Method reference

The tests behind the essays, and what each one counts as failure.

New readers should start with the Start here guide: the core claim, and the three questions to put to any institution.

What this framework asks instead of the usual debates

The usual debate asks questions like: Is the system biased? Did leaders mean well? Is the policy efficient? Does the right exist on paper? Are the ethics principles strong enough? Those questions matter, but they often stall because they stay too close to official language and too far from lived conditions.

This framework asks a more structural question: what does a person have to carry, prove, endure, or risk in order for the arrangement to keep functioning as advertised? That shift moves attention from stated permission to usable options, from values language to actual constraint, and from isolated bad actors to recurring patterns.

Those three moves make a method for reading institutions through burden, livability, recourse, delay, standing, and maintenance rather than through public justification alone.

The failure-behavior claim

Beyond who controls them, what rules they announce, or whether people may object, institutions should be evaluated by their failure behavior. Ask where error is absorbed, what it costs the absorber, whether that error counts as evidence, and which confirmed failures can actually limit or end power.

The claim holds even after conceding that nearly every part of it has a precedent. One structural question shows up in administrative burden, bogus consultation, automated denial, heroic frontline labor, investigations that never conclude, institutional apologies, model errors, memorialization, procedural exhaustion, and regulators captured by the entities they regulate. When the system is wrong, what has to give: the institution’s claim to continue, or the person underneath it?

A framework can make those cases structurally related and say what institutional change would distinguish a real remedy from a cosmetic one. Doing so is a meaningful contribution even where none of its component intuitions is unprecedented.

The framework's strongest version is a theory of catastrophe prevention through preserving correction capacity. The catastrophes it sees best are generated by systems that keep operating after reality has started proving them wrong. Reality diverges from the model, people absorb the difference, and the institution reads successful compensation as evidence the model still works. Seventeen essays' compensation vocabulary, Hollnagel's resilience engineering, and the frontline-adaptation cases behind the crumple zone all name the same loop. What resilience engineering calls work-as-done, this framework reads as telemetry: when people repeatedly have to save a system, those saves count as evidence that the system is failing. Correction is cheap only while the absorbers' capacity holds.

The shortest way to see the whole framework

The burden-visibility diagram shows why a system can look efficient while its costs are hidden: it counts the completed outcome and ignores the phone calls, waiting, caregiving, masking, and workarounds that produced it. The good-vs-bad-insulation diagram separates the insulation that protects a decision-maker from improper pressure from the insulation that shields it from consequence. Read together they answer the two questions the framework starts from: what the system counts, and who is allowed to stay unchanged.

What the System Sees

A system can look efficient because it counts outcomes and ignores the labor required to produce them.
A system can look efficient because it counts outcomes and ignores the labor required to produce them.
View source
%% 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

Good vs Bad Insulation

Insulation from noise, retaliation, or panic protects a decision. The problem is insulation from evidence and consequence.
Insulation from noise, retaliation, or panic protects a decision. The problem is insulation from evidence and consequence.
View source
%% 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

The inferences this framework refuses

The recurring failure the archive attacks is an inference rather than a particular institution. A fact is true, and a conclusion about what should happen gets smuggled out of it. Each conversion below is a move institutions make routinely, and each is invalid. A fact about capacity, necessity, reliance, adaptation, provision, or credentials does not support the conclusion it is routinely asked to carry.

  1. Useful becomes entitled. Relevance does not become jurisdiction: an institution can be competent, predictive, or deeply relied on without acquiring a right to govern adjacent parts of a life.
  2. Necessary becomes justified. Dependence does not imply subordination: needing an employer, a state, a platform, or a system never justifies giving it progressively broader command.
  3. Adapted to becomes consented to. Adaptation is not consent: functioning inside a bad system because the alternatives are worse is not evidence the arrangement was endorsed.
  4. Successful becomes competent. Observed success can conceal institutional failure: outcomes systematically overstate competence when invisible human effort prevents failures from surfacing.
  5. Provided becomes relieving. Formal provision is not practical relief: an institution can officially supply help while exporting the scheduling, coordination, and troubleshooting onto the person supposedly helped.
  6. Exit on paper becomes meaningful exit. How much refusal costs decides how much weight consent can carry.
  7. Dependence becomes indispensability. Necessity can be self-produced: a system can restrict alternatives, force adaptation, and then cite the resulting dependence as proof of its indispensability.
  8. Technically possible becomes socially warranted. Capability does not create permission, and expertise in one domain does not yield authority outside it.

The framework's own inference is the mirror image of these refusals. Sometimes two claims that both look true collide, such as a formally neutral rule and a systematically unequal experience, or an apparently efficient institution and exhausted employees. Treat the collision as evidence that the representation is missing a variable, before concluding that one side is lying. Ask what must be true of the underlying system for both observations to hold. Then look for the mechanism, such as identical rules imposing unequal compliance burdens, ambiguity allocated asymmetrically, or unmodeled cases charged a hidden adaptation cost. The archive's concepts come from that both-true test. Each one names the hidden relation that explains how both observations can be true.

The challenges this framework should expect

Pattern pages carry the pattern-specific objections; these apply to the whole framework.

“This is just an engineering metaphor.”

The engineering language specifies testable relationships: where an error propagates, who absorbs its cost, whether evidence travels upstream, and whether a successful challenge forces a state transition. Remove every engineering noun and the underlying test remains intact, because the metaphor carries a model.

Read the claim on Method

“Assume maximum awareness is cynical or paranoid.”

It is a diagnostic stress test, not an empirical claim that officials always know everything. Assume the institution already has all the information reformers want to give it. If the explanation for why the problem persists still works, the problem was never really about information. The test rules out the easy explanation before anyone reaches for it.

Read the maximum-awareness essay

“But sometimes institutions really are ignorant.”

The method allows that conclusion. It is deliberately falsifiable. If showing that actors lacked information explains the outcome, and new information reliably changes behavior, the knowledge-deficit explanation survives. The test rules out taking ignorance as the default merely because it makes reform politically comfortable.

Read the maximum-awareness essay

A Person Lives With the Act; the System Runs On

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.

Humans have to inhabit actions with bodies, identities, and consequences, while systems keep executing until recourse, redesign, or refusal interrupts the loop.
Humans have to inhabit actions with bodies, identities, and consequences, while systems keep executing until recourse, redesign, or refusal interrupts the loop.
View source
%% title: A Person Lives With the Act; the System Runs On
%% 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

The main discourses this framework intervenes in

Each one moves from a familiar public argument toward a test about cost, livability, burden, or power.

Choice / coercion

Whether visible choice is enough to count as freedom.

  • Old discourse: if a choice is visible, coercion must be absent.
  • Why it stalls: it ignores retaliation, dependence, and the cost of refusal.
  • Reframe: ask whether exit, refusal, and self-protection are actually usable.

Read survivability

Formal access / lived access

Whether rights, options, and procedures matter if they are costly or unlivable to use.

  • Old discourse: formal access is treated as the main moral threshold.
  • Why it stalls: a right on paper can still be punishing to use in practice.
  • Reframe: ask whether someone can use the option without being damaged by the process.

Open survivability

Efficiency / justice

Whether system smoothness is a good in itself, or a sign that burden has been exported.

  • Old discourse: smoothness, speed, and low-friction throughput are treated as obvious goods.
  • Why it stalls: the system can feel efficient because someone else is absorbing the friction.
  • Reframe: ask whose labor or injury is making the surface look clean.

Open burden

Kindness / care

Whether empathic tone, reassurance, and good UX are evidence of actual support.

  • Old discourse: warmth, empathy, and good tone are treated as evidence that care is present.
  • Why it stalls: a humane tone can coexist with missing recourse, redesign, or material support.
  • Reframe: ask what concrete obligations, protections, or repairs actually changed.

Open care and care theater

Procedure / neutrality

Whether delay, review, and administrative process are impartial, or active techniques of control.

  • Old discourse: procedure is treated as neutral simply because it is formal and repeatable.
  • Why it stalls: delay, review, and documentation can be the mechanism of domination.
  • Reframe: ask who pays for the process while the institution preserves its calm.

Open delay

Event-harm / condition-harm

Whether harm is only a discrete incident, or can be ambient, attritional, and structural.

  • Old discourse: harm is recognized mainly as a visible event with a clear beginning and end.
  • Why it stalls: structural harm often accumulates through atmosphere, repetition, and attrition.
  • Reframe: ask what ongoing conditions are wearing people down even without a single dramatic incident.

Read burden and delay

Agency / constraint

How to think about action when people are exhausted, dependent, time-poor, or structurally exposed.

  • Old discourse: action is judged as if everyone has the same room to decide and respond.
  • Why it stalls: exhaustion, dependence, and exposure change what action is realistically available.
  • Reframe: ask what the situation makes possible before assigning blame or responsibility.

Open survivability

Participation / fairness

Whether staying, using, signing, or continuing means the arrangement is acceptable.

  • Old discourse: continued use is treated as a clean verdict in favor of the system.
  • Why it stalls: participation can reflect dependence, attrition, or lack of alternatives rather than endorsement.
  • Reframe: ask what forms of exit, refusal, and dissent were made too costly to use.

Read A Person Lives With the Act; the System Runs On

Power / prohibition

Whether power mainly operates through saying no, or through design, timing, burden, reversibility, and survivability.

  • Old discourse: power is easiest to see when an institution openly prohibits something.
  • Why it stalls: modern control often works through defaults, burden, timing, and managed risk instead.
  • Reframe: ask how design, survivability, and reversibility structure what people can actually do.

Open infrastructural power

The seven tests to carry into the essays

Survivability: can someone stay intact while using the option?

If the route exists on paper but using it predictably threatens safety, dignity, income, belonging, or coherence, the option is not genuinely livable.

Read the survivability pathway

Reversibility: if this goes wrong, who can undo it?

A system fails this test when rollback, exit, appeal, or repair depend on the harmed person absorbing all of the cost and initiative.

Open the reversibility pathway

Burden: what work is being transferred out of sight?

Treat hidden paperwork, vigilance, emotional labor, translation, proof, and self-management as part of the system rather than as private resilience.

Trace burden transfer

Standing: whose testimony counts before proof begins?

Watch who is presumed credible, who must become hyper-legible, and whose noncompliance gets read as character failure rather than evidence about the system.

Read the standing essay

Time: who pays for the wait?

Delay is diagnostic when an institution preserves its own composure by making the person asking for help absorb risk, attrition, and uncertainty.

Follow the delay pathway

Maximum awareness: does the explanation still work when they know?

Assume the institution already has every piece of information reformers want to give it. If the explanation for why the problem persists still works, the problem was never really about information. Only then does ignorance become the leading hypothesis.

Read the maximum-awareness essay

Correction: when the rule is wrong, who can change it?

Assume the misfit is real and known. Ask whether it can count as evidence against the rule rather than as noise, and who has standing to force a change. Then ask what the finding obliges anyone to do, and whether whoever does the correcting can be corrected too.

Open the corrigibility pattern

The mechanisms that turn the tests into something testable

Between the tests and the matrix: the mechanism pages name twenty recurring ways institutions move costs onto people, four of them attacks on correction itself. Each one belongs to exactly one cluster, carries a narration, the impediment it hides, and a checklist, and links back to the essays that ground it. When a situation passes the seven tests and still feels wrong, name the mechanism first. The checklist turns the evaluation into something another person can run, and the cluster mapping says which body of essays to read next.

Action outcomes after the seven tests

Action outcomes based on diagnostic results
Diagnostic outcome What this usually signals Recommended action Continue reading
Redesign recommendation The system can be improved if burden transfer, delay, or proof friction is redesigned before harm hardens. Push for specific design changes: remove hidden labor, shorten waiting loops, and shift verification burden back onto the institution. Read about redesign Trace burden shifts
Recourse escalation Existing channels fail repeatedly rather than in isolated errors, and they need stronger escalation routes. Escalate through documented recourse: aggregate incidents, route through stronger oversight, and force a response with consequences instead of reassurance. Follow survivability failures Map delay as power
Put the rule on trial The same failure recurs across cases, each closed as an exception, while the category that produced it stays untouched. Aggregate the cases into a pattern and route it to whoever holds authority over the rule. Ask for the exception log, the review trigger, and a written answer on what finding would change the category. Read Appeals Test the Clerk, Never the Rule Open the corrigibility path
Refusal / exit condition The arrangement stays unlivable even after attempts at redesign or escalation, and continued participation becomes self-erasing or unsafe. Treat refusal or exit as a legitimate boundary and move toward safer alternatives, coalition support, or non-participation. Read infrastructure as coercion Track care vs. care theater

Use the archive by idea

What this framework cannot do

Architecture is frozen politics. Who gets standing is a political settlement. So are what counts as evidence, which findings must be acted on, who bears delay, whether an appeal pauses the harm, and who can take away whose authority. Instead of replacing power analysis with mechanism design, the framework asks where power has been encoded into the mechanism. The economy the mechanism lives in is part of that analysis, since who profits from an institution’s errors and whether correcting them is priced above avoiding them decide whether a corrigible design survives.

Corrigibility is a necessary limit on legitimate power and falls well short of a full theory of justice. A perfectly corrigible deportation regime could still pursue an immoral policy. Substantive commitments (equality, liberty, welfare, anti-domination) still have to specify what institutions should pursue.

An impossibility result is a structural claim. The term fits only when, under the institution’s rules, no allowed input can produce the outcome. For example, an oversight board that can investigate but has no way to force the conduct to stop cannot stop it with the powers it has. It does not fit a prediction that a reform probably won’t work.

The framework takes no side on how much public power there should be and is strict about how that power handles its errors and who carries their cost. A highly redistributive welfare state, national health service, public housing authority, industrial planning agency, or powerful regulator can satisfy it better than a privatized market regime. The constraint is that power, however large, must still change in response to confirmed evidence of its own mistakes.

The framework applies symmetrically to private power. Employers, insurers, platforms, landlords, banks, hospitals, and model providers also allocate persistence, route errors downward, impose stamina tests, and preserve authority after demonstrated failure. Where private systems have no internal way to be corrected, the framework makes the case for more public intervention.

The opening claims are easy to accept, so the steps beyond them have to be flagged. Hidden burdens are nearly universal, but what follows from them is not. A reader may agree that burdens exist and are distributed by power, reject the redesign a conclusion proposes, and still carry the diagnostic intact. The framework keeps that possible by being honest about its own escalations. When an argument moves from an observed relation to a structural theory, it should say so. Keeping the exits open stops the method from turning into the persuasion it refuses to be.

What the framework builds toward

The limits name what this framework cannot do. The diagnosis also makes positive claims, compressed into one sentence: build institutions that increase what people can safely depend on while reducing what that dependence lets others demand from them.

Dependence creates duties before it creates any authority. The more people rely on an institution, the stronger its duties of reliability, care, accessibility, explanation, and repair should become, and the weaker the case that their reliance gives it authority over them. Dependence alone never gives anyone the right to command.

Social provision is freedom's cost structure. Housing, healthcare, income security, and public services matter partly because they lower the material penalty for saying no to an employer, a platform, a profession, a family arrangement, or an administrative demand. Provision makes refusal survivable, and refusal keeps provision answerable.

The positive ideal is interdependence built on strong institutions with little power to compel: institutions that provide a lot, decide narrowly, can be corrected while they run, and leave people plenty of practical freedom. The opposite of domination is interdependence arranged so that people gain security without giving up too much control over their lives.

The framework's philosophical leverage is a set of separations. Dependence need not imply subordination. Capacity need not imply jurisdiction. Provision need not imply paternalism. Expertise need not imply rule. Consent counts for less as the cost of refusing rises. Institutional strength need not imply diminished liberty. Classic debates assume these move together, but the framework treats each as an independent design question.

Continue reading

New essays by email

One letter a week: that week’s new essays, and one tool to use.

New essays by email

One letter a week: that week’s new essays, and one tool to use.