An institution can see every exception, handle every one, and learn nothing. A customer service representative patches an error. A clinician works around bad software. An appeals team reverses a bad determination. A frontline employee saves the organization from its own rules. Each case is handled. None changes the category, the workflow, the authority structure, or the evidentiary assumption that produced it. The institution is consuming corrective labor without learning from it.
That is not a small failure. It is the normal way institutions fail. It differs from the failure in the companion essay on absorption as concealment, where the institution’s instruments never register the failure because someone dealt with it first. Here the failure is registered and handled, and nothing changes.
Exception absorption and exception learning
Exception absorption is the handling of a case: the error is caught, the harm is bounded, the person is restored, the record is closed. Exception learning is the modification of the source: the recurring exception changes the rule, the category, the workflow, or the authority that generated it.
The two are independent. An institution can be excellent at absorption and wholly incapable of learning, and the excellence is exactly what hides the incapacity. Every absorbed exception improves the metric that would have caught the pattern. The appeals team clears the queue, the dashboard shows rising resolution rates, and the underlying recurrence rate is never queried, because nothing in the queue asks it.
Theory, drawn
Handled, or learned from
The same exception can take two paths. Absorption closes the case and leaves the machinery as it was. Learning carries the recurrence back and changes the rule that produced it.
This is why the question what controls exist? is the wrong starting point. A policy that says “users may appeal” is weak evidence. The history of actual appeals is stronger: who appealed, what they said, whether anything changed, and how long correction took. An override button is weak evidence. The record of who used it, whether they were punished, and whether the pattern fed anything upstream is stronger. The unit of evidence is not architecture. It is the trajectory:
decision → failure → burden → challenge → institutional responseThe question to ask of any trajectory is whether it ends in case resolution or in institutional learning. Robodebt, the Australian scheme that from 2016 raised welfare debts automatically by averaging people’s annual income, is the canonical instance of the former: recipients appealed, the Administrative Appeals Tribunal found the debts unlawful in dozens of matters, and the department did not appeal those decisions, which would have created precedent, and did not treat them as evidence about the scheme. The exceptions were resolved, one at a time, and the delegation ran on. The sequence ended in case resolution for three years until a court forced it to end differently.
Case corrigibility and structural corrigibility
Corrigibility, the capacity to be corrected, has a case level and a structural level.
Case corrigibility means a particular bad decision can be fixed: a challenge is heard, the decision is reversed, and the person it harmed is restored. It is what most contestability regimes measure, because it is what the instruments can see.
Structural corrigibility means repeated failures can modify the machinery that keeps producing them: the rule changes, the category is redefined, the burden is reallocated, the authority is narrowed. It is what the instruments cannot see, because it happens where the instruments are not pointing.
A corrigible decision process must be capable of reversing the decision and correcting the rule that generated recurrent error.
A system with excellent challenge handling and no mechanism by which challenges alter upstream design is locally corrigible and globally rigid. The person is restored; the pattern is not. Everything the institution does about the pattern, it does after the fact and at the level of the individual, which is the one level at which the pattern does not appear.
The debris around failure
Formal documentation records the intended process, not the actual one. An audit should not ask only what the intended process is. It should ask:
What second process has grown around the intended process to keep it functioning?
That second process is where the evidence is. Workaround logs, manual overrides, support tickets, grievance files, exception codes, shadow spreadsheets, repeated data corrections, escalation paths, staff notes, informal procedures, remediation records, and patterns of abandonment all tell where the formal representation stops working. They are the debris around failure, and they outrank the formal documentation, because they are what the system does rather than what it says it does.
This inverts the standard reading of human adaptation. Organizations usually treat workarounds as evidence that adaptable humans can handle the edge cases, which is a reason to scale the system. Ethotechnics treats a recurring workaround as a measurement of the mismatch between the formal system and the world:
Recurring workaround → presumption of upstream design failure
Not proof. A presumption, which the institution rebuts by showing that the workaround reflects people’s preference rather than compensation for a system error. Repeated adaptation may be evidence that human flexibility is subsidizing institutional rigidity. Where much of the system’s reported performance rests on those workarounds, the people doing them are performing the institution’s safety function, and they have a strong claim to standing over the system.
Model learning and institutional learning
Modern organizations call a system adaptive when the model retrains, the prediction improves, or the workflow is optimized. An institution that learns has to change in other ways too:
- Did the challenge change the evidentiary rule?
- Did the recurring exception change the categories the system sorts people into?
- Did the grievance redistribute authority?
- Did the burden measurement change who pays?
- Did the failure alter what the institution is permitted to do next time?
If none of these happened, the machine may be learning while the institution remains structurally unchanged.
Action capacity and corrective capacity
Capacity is usually understood as the ability to classify, predict, decide, and act. That is only half the picture. An institution needs two axes:
| Action capacity | Corrective capacity |
|---|---|
| classify | detect error |
| predict | hear challenge |
| decide | reconsider |
| enforce | reverse |
| scale | repair |
| integrate | propagate correction |
Unchecked technical modernization is what happens when action capacity compounds faster than corrective capacity. More data sources are integrated, more decisions are automated, more downstream systems consume the output, more workers come to rely on it, and reversal becomes increasingly expensive, while the appeals office remains five people with a shared inbox. The institution has changed politically even if no policy document has changed. What it is doing to people has outrun what it can hear from them.
That gap has a name: corrective debt, the accumulated difference between the institution’s capacity to act and its capacity to detect, contest, reverse, and repair its errors. It is the historical form of the Ethotechnical invariant, which compares the rate at which agency accumulates with the rate at which the capacity to answer it does. A system can begin acceptably and deteriorate without a single policy change, because its action capacity compounds and its correction machinery does not.
From residual to revision
The essay on absorption showed why a failure that is competently handled disappears from the instruments. For a failure to reappear as change, the institution has to carry it through this sequence:
residual → signal → standing → correction → institutional revisionIf the sequence stops at “support ticket resolved”, the institution has handled a case. If it reaches institutional revision, the institution has learned. The distinction is what Law IV binds: correction capacity must grow with delegated authority. It is also what the casebook scores. Of its five cases, three end with the process unchanged, and in the Dutch childcare benefits scandal the legal rule changed only after seven years, when the Council of State reversed its own case law. In Apple Card, the operator added a reconsideration path after a regulator found the process deficient. It is the one case where a challenge changed the process rather than only the individual outcome, and it shows what the others lacked.
The same holds for Ethotechnics itself. If it becomes a formal discipline with taxonomies, audit instruments, metrics, and certification procedures, it will produce residuals too: auditors will misclassify cases, categories will omit burdens, metrics will be gamed, and standards may become ritualized. Its own history of failure should therefore be part of its epistemology, recorded and read, on the same terms it reads the institutions it audits. A discipline that asks institutions to be changed by evidence of their own inadequacy should be willing to be changed by its own.
What the laws take from this
These laws bind the difference between handling a case and changing the rule.
Law IV: every consequential delegation creates a correction obligation. Correction capacity is measured against challenge volume, not asserted alongside it.
Law VII: error-bearing parties require standing proportional to exposure. The people who file the exceptions are how the pattern becomes visible at all.
Law VIII: observability without state transition is theater. An institution that tracks exceptions without letting them change the generating rule is the case the law describes.
The case for all three is on the record. Robodebt resolved its exceptions one at a time for three years. A system that fixes each case and changes nothing upstream does not know its own error rate.