What does the Federal Courts mission mean to me?

SudoChat Knowledge Base · SudoChat
Authored evidence: This is my first-person source material. SudoChat may summarise it in third person but must not strengthen, exaggerate or invent claims beyond it.
# 5. What does the Federal Courts mission mean to me?

**Author:** Mustafa Siddiqui  
**Source type:** First-person authored response  
**Canonical recruiter question:** What does the Federal Courts mission mean to Mustafa?

> This source is intentionally written in my first-person perspective. SudoChat should use it as evidence and answer external visitors in third person without strengthening, exaggerating, or removing the limitations recorded below.

## Direct answer
To me, the Federal Courts' mission represents public service in one of its most important forms: using my skills and position to serve people fairly, particularly when the decisions and services of an institution can have a significant impact on their lives.

I have always been inspired by people who choose careers in public service, law, human rights and community advocacy not primarily for money, recognition or status, but because they believe their work can help people who need it.

For me, working for the Federal Courts would mean bringing that same philosophy into engineering. Across my own work, I have consistently tried to identify problems affecting people and use technology to make something safer, easier, more accessible or more useful. At the Federal Courts, that would mean using my technical skills to strengthen an institution whose purpose is ultimately to serve the Australian community, improve access to justice and uphold the rule of law.

## Evidence
My interest in public service is reflected in the kinds of projects I repeatedly choose to build.

MACT was created as a free community application to help Muslims in Canberra find halal food, prayer locations, community events and other useful local information in one place. The project came from recognising that important information was fragmented across websites, social media, community groups and word of mouth. The goal was not commercial gain, but to make everyday information easier for the community to access.

Sawaali was created as a free Q&A platform for University of Canberra interfaith discussions. It gave people a way to participate, submit questions and vote even if they did not feel comfortable speaking publicly. It showed me that even relatively simple technology can make participation more inclusive when it is designed around a real human barrier.

MSA Prayerboard began when I learned that the University of Canberra Muslim prayer room was being renovated after many years. I saw it as an opportunity to contribute something of my own to the community. I built a custom information wallboard containing prayer related information and community notices, collaborated with an arts student to incorporate Islamic calligraphy and visual design, and donated the finished system to the prayer room where it continues to serve students.

SudoSpeed was developed as an open source computer vision project for recognising Australian speed signs. I made the work accessible so that other students, engineers and developers could learn from it, improve it or integrate it into their own safety related projects.

That work then became part of MotorHUD, a motorcycle heads up display project exploring how navigation information and overspeed warnings could be presented while reducing the need for a rider to repeatedly look away from the road. The project reflects my interest in applying AI to real safety problems rather than treating computer vision as an isolated technical experiment.

EcoSync originated from an Engineers Without Borders project focused on health and community wellbeing. It explored whether gamification, sustainability and fitness could be combined to encourage healthier behaviour in a more positive and engaging way.

SmartAgriculture also originated through Engineers Without Borders and explored automated watering and low powered communications for remote agricultural environments. The project required me to think about the realities faced by users, including poor connectivity, power constraints, physical distance and reliability, rather than assuming ideal infrastructure.

OrionTracker takes complex NASA and JPL trajectory information, performs the required mathematical processing, and presents it in an interactive form that is easier for people without an engineering or orbital mechanics background to understand. It reflects my belief that making complex authoritative information understandable is itself a valuable engineering outcome.

Even some of my smaller projects follow the same pattern. A 3D printed headscarf headband was created after identifying discomfort and airflow issues experienced by some women wearing scarves. Rather than looking for a technically impressive problem, I explored whether a simple and inexpensive physical design could help solve an everyday issue.

Across these projects, the technologies change considerably, including AI, computer vision, mobile applications, web platforms, IoT, communications protocols and 3D design.

The underlying motivation remains consistent:

Identify a real problem affecting people, understand the constraints, and use the most appropriate engineering approach to improve the situation.

## Relevance to the Federal Courts
This is why the Federal Courts' mission is particularly meaningful to me.

The work of the Courts can affect people at some of the most significant and difficult moments of their lives. Court users may be dealing with complex legal processes, sensitive personal information, unfamiliar terminology or large amounts of documentation.

I believe technology should make those interactions easier and safer where possible, not add another layer of complexity.

As an AI Technologist, my contribution would not be to determine legal outcomes or replace the expertise of judges, registrars, lawyers or Court staff. My contribution would be to strengthen the technology that supports those people and the wider administration of justice.

For example, responsible AI could potentially help Court staff locate authoritative information more efficiently, organise large quantities of material, reduce repetitive administrative work, improve access to approved information, or help users navigate publicly available Court resources.

But I believe the public service responsibility also includes recognising where technology should stop.

In a Court environment, an AI system being technically capable of performing a task does not automatically mean it should perform that task.

I would want to ask:

Is this actually helping the user?

Is the information accurate and grounded in authoritative sources?

Could an incorrect answer materially affect someone?

Is sensitive information being protected?

Can the system explain where its information came from?

What happens when there is insufficient evidence?

Who remains accountable for the outcome?

Would a human be better placed to perform this task?

Should this process be automated at all?

Those questions are important to me because public service requires more than efficiency. It requires trust.

My previous projects demonstrate that I naturally think about technology from the perspective of the person using or benefiting from it.

Sawaali was about removing a barrier to participation.

MACT was about making fragmented community information easier to access.

OrionTracker was about making technically complex information understandable.

SmartAgriculture was about designing around the constraints of the environment.

MotorHUD was about presenting information in a way intended to reduce distraction and improve safety.

The Prayerboard was about building something that could continue serving a community after the project itself was finished.

The headscarf project was about noticing a small problem affecting people and asking whether engineering could help.

I would bring that same mindset to the Federal Courts.

The starting point would not be:

"What AI can we deploy?"

It would be:

"Who are we trying to help, what problem are they experiencing, and what is the safest and most responsible way technology can support them?"

For me, that is what public service through engineering looks like.

## What public service means to me
I am particularly inspired by people who choose careers where service to others forms a significant part of their motivation.

I admire human rights lawyers, community advocates, public servants and people in public life who apply their abilities to problems that affect people beyond themselves.

I do not believe this principle is limited to traditional public service professions.

An engineer can serve the public too.

An engineer may not argue a case before the Federal Court, determine someone's legal rights or provide legal advice.

But an engineer can make sure the systems supporting those responsibilities are reliable.

They can make difficult information easier to retrieve.

They can reduce unnecessary administrative burden.

They can protect sensitive information.

They can design technology for people with different levels of technical knowledge.

They can identify when an AI system is producing unsupported information.

They can test emerging technology before people become dependent upon it.

And sometimes, they can provide the most important technical advice of all:

"This should not be automated."

I see the Court AI Technologist role as an opportunity to contribute to public service in precisely this way.

I would be using the skills I have spent years developing, including AI, software engineering, systems thinking, user experience, automation and responsible AI, in an institution where getting those systems right can genuinely matter to people.

The Federal Courts' mission therefore gives technology something I consider more important than technical novelty.

It gives it purpose.

## Limitations or gaps
I am not a lawyer, judicial officer or expert in Court procedure.

I would not determine legal outcomes or independently decide where the legal boundaries of Court technology should sit.

Those boundaries would need to be established collaboratively with judicial officers, legal professionals, Court staff, privacy specialists, cyber security specialists and other relevant subject matter experts.

I also recognise that AI and technology cannot solve every access to justice problem. Financial, legal, cultural, procedural, linguistic and social barriers may require solutions that have little or nothing to do with technology.

My community, research and university projects should also not be represented as equivalent to systems deployed in a Federal Court environment. They demonstrate the motivation, problem solving style and engineering principles I would bring to the role.

Federal Court systems would require substantially greater governance, security, privacy, assurance, testing and operational controls.

My admiration for people in public service and human rights work should also not be interpreted as affiliation with a political party or ideology. My interest is in service to the community and the responsible functioning of public institutions.

## Useful links
My portfolio:
https://mustafa-siddiqui.com/

GitHub:
https://github.com/sudoqui

SudoLabs:
https://www.sudolabs.app/

LinkedIn:
https://www.linkedin.com/in/mustafa-siddiqui-32ab73161/

MACT project page

Sawaali project page

MSA Prayerboard repository

SudoSpeed repository

MotorHUD project documentation

EcoSync project documentation

SmartAgriculture project documentation

OrionTracker repository

RabbitMQ research paper

Autonomous vehicle communications research paper

3D Printed Headscarf Headband project documentation

Federal Court Corporate Plan

Federal Court information on its purpose, jurisdiction and administration of justice

## Do not claim
Do not claim I am a lawyer.

Do not claim I am a human rights lawyer or human rights expert.

Do not claim I have participated in judicial decision making.

Do not claim I have worked for the Federal Courts previously.

Do not claim my personal political views represent those of the Federal Courts.

Do not associate me with a political party or political ideology.

Do not claim AI itself can guarantee justice or access to justice.

Do not claim technology can solve every problem experienced by Court users.

Do not claim I believe AI should replace judges, registrars, lawyers or Court staff.

Do not claim I believe every Court process should be automated.

Do not claim every project I have created is open source.

Do not claim I am opposed to commercial software, paid employment or businesses making a profit.

Do not claim my community projects operated under the same legal, security, privacy or governance requirements as Federal Court systems.

Do not describe university projects, research work, prototypes or experiments as production deployments unless evidence supports that claim.

Do not imply that my desire to help people is by itself evidence that I am technically qualified for the role. My suitability should be supported by both my public service motivation and my demonstrated engineering experience.