By question
The whole position. The Architecture in One Map, The Governance Trilemma, The Human Subsidy to Institutional Continuity
Distribution: who bears the burden. Burden Transfer Flow, What the System Sees, Formal Compression to Power Chain, Permission → Cost → Non-Use Loop, Human vs System: Inhabitation vs Execution
Correction: who can change the arrangement. The Return Circuit Fork, The Error Metabolism Path, Correction Authority Is Divisible, The Escalating Defeasibility Tree, The Settlement and Its Reopening Conditions, The Governance of Misfit, Internal Learning vs External Selection, Good vs Bad Insulation, The Two Capacities
Jurisdiction: what the institution was entitled to decide. Jurisdictional Non-Conversion, Teleology, Jurisdiction, and Corrigibility
New to the framework? Read the short guide first.
The whole position
The Architecture in One Map
One map of the whole position: error governance is the mechanism, consequential review is the test, and the absence of a permanently exempt layer is the design. Use this as orientation before any individual mechanism: locate the arrangement on the map, then descend into the stage of the path that decides its case.
%% title: The Architecture in One Map %% caption: Mistakes plus unequal power make domination possible, unless an error can have consequences without anyone's permission and the correction mechanism itself can be challenged. flowchart TB A[Permanent fallibility,<br/>asymmetric institutions] --> B[Unequal power to define,<br/>absorb, externalize,<br/>and respond to error] B --> C[Risk of domination] C --> D[Detectability:<br/>who can see the error] C --> E[Contestability:<br/>who can define it] C --> F[Burden tracing:<br/>who pays for it] D --> G[Consequential review:<br/>decision, rule, structure,<br/>jurisdiction] E --> G F --> G G --> H[The correction mechanism<br/>is also fallible] H --> D
The whole position
The Governance Trilemma
Choosing scale and authority yields the closed circuit of domination, where the model's errors are eaten by the human sacrifice zone. Choosing no-unilateral-burden and authority abandons scale. Choosing scale and no-unilateral-burden requires surrendering executive monopoly: the people it governs gain the Andon cord, mandatory discovery, and automatic liability that can halt the machine. Use this when an institution claims it can deliver high throughput, low cost, and zero human casualties while keeping management's power fully unchecked — the free-lunch promise this framework calls a lie.
%% title: The governance trilemma
%% caption: Scale, no unilateral burden, and absolute executive authority form an impossible trilemma. The free lunch is the promise that all three can be had at once; every functioning architecture drops one vertex.
flowchart TB
classDef scale stroke-width:2.4px,font-weight:bold;
classDef harm stroke-width:2.2px,stroke-dasharray:6 3;
classDef auth stroke-width:1.6px;
classDef closed stroke-width:2.4px;
classDef open stroke-width:2.4px,font-weight:bold;
T[Governance Trilemma] --> S[1. Massive Scale & Throughput<br/>Legibility at Scale]:::scale
T --> H[2. No Unilateral Burden<br/>No Crumple Zone]:::harm
T --> A[3. Absolute Executive Authority<br/>Uncontested Execution]:::auth
S --> D{Pick any two}
H --> D
A --> D
D -. 1 + 3 .-> CL[Closed Circuit of Domination<br/>Scale without safety]:::closed
D -. 2 + 3 .-> LO[Localist Sanctuary<br/>Safety without scale]:::harm
D == 1 + 2 ==> OP[Open Circuit of Constitutional Friction<br/>Scale with safety,<br/>authority surrendered]:::open
The whole position
The Human Subsidy to Institutional Continuity
Resilience cybernetics identifies the gap between work-as-imagined and work-as-done; social reproduction reveals the unpriced human energy maintaining life; institutional economics tracks how costs are dumped into bodies; administrative burden explains how friction disarms redress. At the center sits the Crumple Zone: institutions surviving on unrecorded human compensation. Use this when explaining what kind of theory this archive builds, and how its critique connects systems engineering, economics, care labor, and political power.
%% title: The Human Subsidy to Institutional Continuity %% caption: How four distinct traditions converge into one diagnosis: the gap between formal system design and human survival. flowchart TD classDef trad stroke-width:1.5px; classDef synth stroke-width:2.4px,font-weight:bold; A[Safety-Critical Cybernetics<br/>Work-as-Imagined vs Work-as-Done]:::trad --> C B[Feminist Social Reproduction<br/>Unpriced Affective & Relational Labor]:::trad --> C C[THE HUMAN SUBSIDY<br/>Compensated performance & epistemic erasure]:::synth C --> D[Institutional Economics<br/>Adaptation Externalities & Social Costs]:::trad C --> E[Administrative Burden & Non-Domination<br/>Attenuated Signals & Corrective Standing]:::trad
Distribution
Burden Transfer Flow
What looks efficient at the center may be strain that has been exported to someone with less leverage. Use this when a workplace, platform, clinic, or bureaucracy looks orderly only because somebody else is doing the hidden cleanup.
%% title: Burden Transfer Flow %% caption: A system often runs smoothly only because work, risk, delay, or emotional fallout has been pushed downstream, and the people absorbing it get called resilient. flowchart TD A[System wants smoothness] --> B[Cost gets exported] B --> C[Downstream person,<br/>team, or patient absorbs it] C --> D[Adaptation looks like<br/>professionalism or resilience] D --> E[Institution counts the surface as success] E --> A
Distribution
What the System Sees
The dashboard and the ledger record completed outcomes. The phone calls, waiting, caregiving, masking, overtime, and workarounds that produced them are invisible to the model — which is exactly why the model's assessment of itself stays green while the burden grows. Use this when an institution reports lower cost or higher throughput and the open question is how much invisible labor downstream absorbed the difference.
%% title: What the System Sees
%% caption: A system can look efficient because it counts outcomes and ignores the labor required to produce them.
flowchart LR
classDef seen stroke-width:1.4px;
classDef hidden stroke-width:2.2px,stroke-dasharray:6 3;
subgraph SEEN[What the system counts]
direction TB
A1[Application submitted]:::seen
A2[Appointment completed]:::seen
A3[Shift covered]:::seen
A4[Claim resolved]:::seen
end
subgraph HIDDEN[What it may not see]
direction TB
B1[3 phone calls / 2 hours waiting]:::hidden
B2[Caregiver help / masking]:::hidden
B3[Unpaid overtime / workarounds]:::hidden
B4[Stress]:::hidden
end
A1 -. uncounted .- B1
A2 -. uncounted .- B2
A3 -. uncounted .- B3
A4 -. uncounted .- B4
Distribution
Formal Compression to Power Chain
When an automated interface is simplified, complexity is conserved and dumped downstream. Power is the privilege of simplifying while forcing others to adapt. Use this when an institution claims an automated process cut handling time or unit cost, while claimants or staff downstream absorb the uncounted work of reconciling it with real cases.
%% title: Formal Compression to Power Chain %% caption: Complexity is conserved. Formal compression leaves residual complexity, which lands as burden on some people and power for others. flowchart TD classDef actor stroke-width:1.6px; classDef system stroke-width:1.2px; classDef gate stroke-width:1.6px; classDef repair stroke-width:2.4px,font-weight:bold; A[Formal Compression<br/>Reduction to schema]:::system --> B[Residual Complexity<br/>Complexity conserved]:::gate B --> C[Burden Allocation<br/>Downstream absorption]:::actor C --> D[Power<br/>Adaptation privilege]:::repair
Distribution
Permission → Cost → Non-Use Loop
A system can preserve the language of choice while making the lived use of that choice too costly to sustain. Use this when an institution points to low uptake, silence, or “continued participation” as evidence that the option was fair all along.
%% title: Permission → Cost → Non-Use Loop %% caption: Formal permission fails publicly when the cost of use makes withdrawal predictable and institutions misread that withdrawal as proof nothing needed to change. flowchart TD A[Permission exists] --> B[Using it carries cost] B --> C[Withdrawal, delay,<br/>silence, masking] C --> D[Institution records non-use] D --> E[Non-use gets misread<br/>as consent or lack of need] E --> A
Distribution
Human vs System: Inhabitation vs Execution
People experience an action from the inside, but institutions tend to process it as a rule, throughput problem, or continuation path. Use this when a system calls something simple or available while the person inside it experiences conscience, exposure, exhaustion, or identity cost.
%% title: Human vs System: Inhabitation vs Execution %% caption: Humans have to inhabit actions with bodies, identities, and consequences, while systems keep executing until recourse, redesign, or refusal interrupts the loop. flowchart TD A[Human] --> B[Must inhabit the action] B --> C[Feels risk, conscience,<br/>identity cost, exposure] C --> D[Needs recourse,<br/>redesign, or a stopping point] E[System] --> F[Executes rule or workflow] F --> G[Optimizes continuity,<br/>throughput, legibility] G --> H[Pressure to continue<br/>or normalize the cost] H --> D
Correction
The Return Circuit Fork
Dependence is legitimate where the defect it produces can travel back and change the system. It becomes domination where the defect stays with the person who absorbed it: the difference between a return channel and a dead end. Use this when an arrangement justifies itself by how much it relies on people's waiting, documentation, labor, or endurance. The open question is whether that reliance ever becomes a reason the institution must change.
%% title: The Return Circuit Fork
%% caption: Institutions depend on people's time, labor, proof, and endurance. That dependence is legitimate when the harm it causes can travel back and force the institution to change. When the harm stays with the person who absorbed it, the dependence is domination.
flowchart TB
A[Institution depends on<br/>people's time, labor, proof, endurance] --> B{Who absorbs the cost and<br/>who is licensed to repair it?}
B --> C[Harm gets standing<br/>and an upstream return channel]
C --> D[Correction binds the institution]
D --> E[Power stays contestable]
E --> A
B --> F[Harm stays privately absorbed<br/>with no return channel]
F --> G[Burden is normalized as resilience;<br/>non-use is misread as consent]
G --> H[The institution's surface stays smooth]
H --> A
Correction
The Error Metabolism Path
Corrigibility depends on the whole path holding, from the first stage to the last. An institution can see an error and still absorb it. Each stage is a separate place where evidence can lose its hold on the institution. Use this to find where a failed correction died. Look at the person who could only plead, the one-off exception, the absorbed harm, and the advisory finding. Then look at the revision that stalled or came out patchwork, the acknowledgment theater, the institution grading its own exam, and the forgotten trial.
%% title: The Error Metabolism Path %% caption: An error gets dealt with only if it travels the whole path. Each stage is a separate place where evidence can lose its hold on the institution. flowchart TD A[Standing:<br/>who may report] --> B[Learning rate:<br/>when variance indicts] B --> C[Burden tracing:<br/>who pays during review] C --> D[Correction authority:<br/>who can force revision] D --> E[Scale:<br/>how revision propagates] E --> F[Consequence:<br/>what must change] F --> G[Measurer:<br/>who defines the test] G --> H[Memory:<br/>where the record lives] H -.-> A
Correction
Correction Authority Is Divisible
The political fight is usually over which of the nine authorities an actor holds, rather than whether correction exists at all. A channel can grant the first four and still force nothing to change. Use this when a participatory process, appeal, or audit claims to give standing, and the open question is how far down the ladder the claimant's authority actually travels.
%% title: Correction Authority Is Divisible %% caption: Nine separable authorities run from observing to terminating. Being affected justifies strong rights in some without implying equal competence in all. flowchart TB A[Observe the evidence] --> B[Report it] B --> C[Trigger review] C --> D[Contest the interpretation] D --> E[Adjudicate the error] E --> F[Specify the remedy] F --> G[Implement the technical response] G --> H[Reopen the jurisdiction] H --> I[Terminate or<br/>replace the institution]
Correction
The Escalating Defeasibility Tree
Not every error moves down the tree, and nothing moves automatically. The tree says when bigger questions become fair to ask, guarding against both overreaction and self-protective rigidity. Use this when an institution answers every adverse finding with a fix at the level the finding cannot reach. The open question is what the pattern of repeat failures has already earned the right to put on trial.
%% title: The Escalating Defeasibility Tree
%% caption: What gets reviewed grows with the evidence, from implementation to jurisdiction to whether the institution should continue at all.
flowchart TB
A[Isolated execution failure] --> B[Review implementation]
B --> C{Repeats under<br/>the same rule?}
C -- no --> D[Stop: fix held]
C -- yes --> E[Review the rule]
E --> F{Repeats across<br/>rules?}
F -- no --> D
F -- yes --> G[Review incentives and<br/>governance structure]
G --> H{Persists<br/>after reform?}
H -- no --> D
H -- yes --> I[Review the jurisdiction]
I --> J{Fundamentally<br/>unreformable?}
J -- no --> D
J -- yes --> K[Withdraw, replace,<br/>or terminate]
Correction
The Settlement and Its Reopening Conditions
The settlement carries its own reopening conditions: who can reopen it, on what evidence, at what cost. Non-finality is still a decision, one that states the terms on which it can be revised. Use this when an institution defends a closure as settled, and the open question is whether anyone was named with the standing to reopen it and whether the evidence conditions were written down anywhere.
%% title: The Settlement and Its Reopening Conditions
%% caption: A decision can be final enough to act on without being closed forever. The settlement states who can reopen it, on what evidence, at what cost.
flowchart TD
A[Settlement:<br/>act on it now] --> B{Reopening<br/>conditions written?}
B -- yes --> C[Named standing,<br/>evidence threshold,<br/>cost allocation]
C --> D[Defeasible settlement:<br/>final for action,<br/>not immune forever]
B -- no --> E[Exempt layer<br/>with a signature]
E --> F[Institution cannot act<br/>without defending closure<br/>as permanence]
Correction
The Governance of Misfit
The quadrant describes without grading. Coercive externalization, protective differentiation, extractive incorporation, and recursive reconstruction are four ways of handling the same misfit. Whether control is concentrated or distributed decides if any of them can be contested. Use this when an arrangement absorbs the people its rules fail and the open question is what happened to the variance, and who had the authority to deal with it.
%% title: The Governance of Misfit
%% caption: What an arrangement does with the people its rules fail: variance externalized or incorporated, structure insulated or revisable, and a separate axis for who controls the response.
flowchart TB
A{What happens to the<br/>rule's misfit?} --> B[Externalized:<br/>routed outside the rule]
A --> C[Incorporated:<br/>absorbed as input]
B --> D[Insulated structure:<br/>coercive externalization]
B --> E[Revisable structure:<br/>protective differentiation]
C --> F[Insulated structure:<br/>extractive incorporation]
C --> G[Revisable structure:<br/>recursive reconstruction]
D --> H{Who controls<br/>the response?}
E --> H
F --> H
G --> H
H --> I[Concentrated:<br/>no quadrant is contestable]
H --> J[Distributed:<br/>no quadrant is a ranking]
Correction
Internal Learning vs External Selection
Neither mechanism works alone, and each fails in its own signature way. Internal learning risks incumbent capture, cosmetic reform, and organizational forgetting. External selection risks catastrophic exit costs, absent alternatives, and monopoly lock-in. Use this when an arrangement claims to correct itself, and the open question is whether its correction has a working rival that failure cannot capture.
%% title: Internal Learning vs External Selection %% caption: Internal learning keeps capacity but leaves insiders in charge of how failure is read; external selection punishes failure but needs a real way out. Sturdy correction needs both, and each must be open to challenge. flowchart TD A[Institution fails] --> B[Internal learning:<br/>revise model, rule,<br/>reallocation of authority] A --> C[External selection:<br/>exit, competition,<br/>loss of jurisdiction] B --> D[Signature failures:<br/>incumbent capture, cosmetic<br/>reform, forgetting] C --> E[Signature failures:<br/>exit too costly, no<br/>alternatives, lock-in] D --> F[Contestability of<br/>the internal channel] E --> G[Contestability of<br/>the external channel] F --> H[Redundant correction<br/>capacity] G --> H
Correction
Good vs Bad Insulation
Judges, scientists, and civil servants need insulation from improper pressure. The same barrier becomes domination when it blocks the harm the institution caused from reaching the actor who can change the rule. Use this when an institution defends its unaccountability as 'independence' — the test is whether the insulation blocks improper pressure or blocks consequence.
%% title: Good vs Bad Insulation
%% caption: The problem is not insulation from noise, retaliation, or panic. It is insulation from evidence and consequence.
flowchart TB
classDef good stroke-width:2.4px,font-weight:bold;
classDef bad stroke-width:2.2px,stroke-dasharray:6 3;
subgraph GOOD[Good insulation: blocks improper pressure]
direction TB
G1[Noise / retaliation / panic] -. blocked .- G2[Decision-maker]:::good
G2 --> G3[Still receives evidence + accountability]:::good
end
subgraph BAD[Bad insulation: blocks evidence and consequence]
direction TB
B1[Harm / contradiction] -. blocked .- B2[Decision-maker]:::bad
B2 --> B3[Keeps authority unchanged]:::bad
end
GOOD ~~~ BAD
Correction
The Two Capacities
Modernization measured on the first axis alone mistakes an unanswerable machine for a developed one. The corrigible-capability quadrant is the design target, and the capable-and-unanswerable quadrant is the trap development normally drifts into. Use this when an institution's growth story is told entirely in throughput, prediction, or coverage, and the open question is whether the ability to contest it grew with the ability to act.
%% title: The Two Capacities
%% caption: Administrative capacity and corrective capacity are separate axes. A society can become more capable and less corrigible at the same time, and the quadrant decides what its power is worth.
flowchart TB
classDef system stroke-width:1.2px;
classDef gate stroke-width:1.6px;
classDef repair stroke-width:2.4px,font-weight:bold;
classDef failure stroke-width:2.2px,stroke-dasharray:6 3;
A{Can it know, classify,<br/>decide, enforce?}:::gate --> B[High administrative<br/>capacity]:::system
A --> C[Low administrative<br/>capacity]:::system
B --> D{Can subjects detect, hear,<br/>reverse, repair?}:::gate
C --> D
D -- yes --> E[Corrigible capability:<br/>power that can be challenged]:::repair
D -- no --> F[Capable and unanswerable:<br/>modernization without correction]:::failure
C -- yes --> G[Small and answerable]:::system
C -- no --> H[Weak and unreachable:<br/>where accidental freedom lives]:::system
Jurisdiction
Jurisdictional Non-Conversion
The valid path runs from a fact, through its relevance to this decision and a separate justification, to limited authority. The invalid path jumps from the fact straight to 'therefore we may govern more', and that jump is where domination gets in, dressed up as competence. Run in reverse, the rule protects the person: their adaptability is a fact about them, and the institution cannot treat it as a standing offer. Use this when an institution's claim to govern arrives as a list of what it knows, provides, or survives, and the open question is where the argument for this particular authority begins.
%% title: Jurisdictional Non-Conversion
%% caption: Facts do not convert into authority without independent justification. Expertise is not sovereignty; survival is not legitimacy; success is not competence.
flowchart TD
A[Fact: expertise,<br/>dependence, necessity,<br/>participation, survival,<br/>success] --> B{Specific relevance<br/>to this decision?}
B -- no --> C[No authority<br/>follows]
B -- yes --> D{Independent<br/>justification<br/>for the extension?}
D -- no --> C
D -- yes --> E[Bounded authority,<br/>renewal conditions attached]
A -.->|the invalid path:<br/>therefore we may<br/>govern more| F[Unbounded authority]
Jurisdiction
Teleology, Jurisdiction, and Corrigibility
Mainstream alignment optimizes what the system should want (its principal's intent) and loses two other questions along the way: what the system has jurisdiction over, and who has corrective standing to challenge it. Use this when an AI safety framework claims alignment solves governance, ignoring what the law lets the system decide, who holds each decision, and how citizens get recourse.
%% title: Teleology, Jurisdiction, and Corrigibility
%% caption: The institutional trilemma: alignment optimizes the system's goal, but legitimate authority also needs jurisdiction and corrective standing.
flowchart TB
classDef teleology stroke-width:1.4px;
classDef jurisdiction stroke-width:1.6px;
classDef recourse stroke-width:2px,font-weight:bold;
subgraph TEL [1. Teleological Alignment]
A[Principal Objective]:::teleology --> B[Model Optimization]:::teleology
end
subgraph JUR [2. Bounded Jurisdiction]
C[Statutory Mandate]:::jurisdiction --> D[Evidentiary Boundary]:::jurisdiction
end
subgraph COR [3. Institutional Corrigibility]
E[Residual Harm]:::recourse --> F[Corrective Standing]:::recourse
F --> G[Binding Reversal]:::recourse
end
B -. Cannot Subsume .- C
D -. Must Connect To .- E