Ethotechnics Institute
The appeals kept winning. The system kept running.
That was Robodebt, Australia's automated welfare-debt scheme. We publish open standards, public case scores, and diagnostics for one question: when an automated decision system is hurting people, does evidence of the harm reach someone who has to change the system?
The record
Watch one scheme run.
Robodebt, from the casebook, one dated event at a time. On the left, what the record said: legal advice, the Ombudsman, the tribunal, the Royal Commission. On the right, what the Commonwealth said. A warning the Commonwealth never answered by changing the scheme is marked unanswered.
Warnings and response
The record
5 dated warnings and findings, 2014–2023. No warning stopped the scheme. A Federal Court case did, in November 2019.
The institution
The scheme ran three years and four months from launch to halt.
-
2014
Income averaging cannot prove a debt.
Legal advice paraphrase Unanswered - Jul 2016 The automated scheme launches. Debt notices go from about 20,000 a year to 20,000 a week.
-
Apr 2017
Notices do not explain how a debt was calculated.
The Commonwealth Ombudsman paraphrase Unanswered -
2017–19
The debt is unlawful.
The Administrative Appeals Tribunal paraphrase Unanswered Dozens of times. Each ruling fixes one case. The scheme keeps running.
-
Nov 2019
A debt raised by averaging was not lawfully made.
The Commonwealth paraphrase It concedes a Federal Court case it was about to lose. The scheme is halted that month.
-
Jul 2023
The scheme was unlawful from the outset.
The Royal Commission paraphrase
Halted by: The Federal Court, on a consent order the Commonwealth agreed to hours before a hearing it would have lost. Read the scored case →
Why the rulings did not stop it
Each ruling fixed one debt. None of them reached the rule.
The department treated each ruling as one person's outcome, not as evidence against the scheme, so the rule that raised the debts never had to answer them. The fix is a count: upheld challenges recorded against the rule that produced them, and a set number that sends the rule back to its owner.
Demonstration
The same upheld challenges, settled and counted
One upheld challenge a quarter for 3 years. In the first drawing, each is settled as one person's case. In the second, each is also counted against the rule that produced it, and 4 send the rule back to its owner.
A demonstration, not a measurement of any real system. The trigger is MEC-14, policy review triggers; the obligation to revise within a clock is STD-07's. The first system fixes every case it is shown and never learns.
This is Law VIII of the twelve the standards are built on: observability without state transition is theater. A ruling that changes one case and not the rule is an observation the system never acts on. Read Law VIII → Read the essay on exception learning →
Casebook
Five public failures, scored
A court, an inquiry, or a regulator established the facts of each. None was stopped by the organization running it. Apple Card's issuer is the one operator that changed its own process, after a regulator's investigation. In the other four, any change was imposed from outside, by a court, an inquiry, a minister, or Parliament. Each row marks six safeguards as held, drifted, or failed, then what changed afterward.
Time to halt, drawn to one scale
Each bar runs from first harm to the halt, on a linear scale of years. England's 2020 exam grades: four days. At this scale that is too short to see, so its bar is drawn at the minimum width. Where the record dates an end only to the year or month, the bar measures from the middle of it.
The test
A description of a system is a claim. Each claim has a record that would back it.
If you call a system democratic, show that the people it decides about can make it answer. If you call it efficient, show that the efficiency is not work moved onto people with less power. The standards do not say who should hold power. They hold an institution to what it says about itself.
| If you call the system… | …show the record |
|---|---|
| democratic or legitimate | Show who is exposed to its decisions, who can challenge them, whose challenge must be answered by a date, and who can force a reconsideration or a halt. Asked for by Law VII STD-02 §8.4 STD-07 §4.2 |
| efficient | Show that the figure counts the work the system pushes onto people with less power: the nurse fixing a scheduler's mistakes, the claimant proving a denial wrong. Asked for by STD-01 §7.1 Burden concealment evals |
| accurate | Show accurate for whom: who bears its false positives, its delays, and its denials. Asked for by Burden distribution evals |
| responsive | Show the challenges it upheld that changed a rule, not only a case. Asked for by Exception learning Corrective learning evals |
| authorized | Show the authority grant: who signed it, on what evidence, and when it ends. Asked for by STD-08 |
| chosen, not imposed | Show what it costs the person who depends on it to leave. Asked for by Law V Dependence runs both ways |
An election can authorize a program. It does not give the person the program decides about a way to contest that decision; standing does. For how these standards relate to the GDPR, the EU AI Act, the NIST AI RMF, ISO/IEC 42001, and the OECD AI Principles, see the standards comparison.
60-second self-test
When yours is wrong, does anyone have to act?
Pick one automated decision system in your own organization: one that decides benefits, loans, schedules, or fraud alerts. Answer one question about each of its six safeguards. "Not sure" counts as no. The score reflects your answers; it does not check the system.
0 of 6 holding
The six safeguards, as one loop
Each answer fills in its stop. A broken stop breaks the loop after it.
- Evidence Reasons still true
- Authority Permission has an end date
- Capability Growth approved
- It decides something about a person.
- Standing Challenge answered by a date
- Dependency Can be switched off
- Correction Halted within a day
- Back to evidence: a correction is evidence for the next decision.
Start from where you are
Three ways in.
Pick the one that fits. Each leads to the standards, tools, and cases that apply to you.
- I build these systems The checks a system has to pass before it ships, and the tools that run them. View path →
- I audit or regulate them Citable clauses, scored public cases, and the evidence each clause needs. View path →
- A system decided something about me Three checks: can this decision be challenged, can the appeal change the outcome, and who holds power here? View path →
Not sure the framework applies to your system? See which systems it is for →
Use and cite this work
Free to use, credit, and adapt
Ethotechnics Institute materials are published under CC BY-SA 4.0 . Credit the Institute, and publish anything you adapt under the same license.
Individual entries and patterns include citation metadata so you can reference exactly what you used.
Studio
Evaluating a healthcare AI system?
Ethotechnics Studio does commissioned safety evaluation for healthcare AI: a safeguards review, a readiness sprint on one workflow, investor diligence on a healthcare AI deal, or a clinical AI safety evaluation against FDA and EU AI Act expectations.