Legitimacy test
An institution is legitimate only if people can inhabit its options without being forced to absorb hidden costs for the system’s sake.
This page is not only an orientation page. It is a compact theory of society: a way to judge whether institutions, platforms, clinics, schools, workplaces, and states are preserving order by exporting strain downward while keeping legitimacy language intact.
When a system offers a right, procedure, or choice in formal terms but makes the lived use of it punishing, identity-damaging, or administratively impossible, the legitimacy claim has already failed. The question is not whether permission exists on paper; it is whether the institution can be used without manufacturing a crumple zone.
What is this theory?
It is a theory of society built at the level of institutions and systems. It asks how power keeps appearing normal by shifting cost, delay, risk, and moral injury onto the people with the least leverage, then reading the resulting adaptation as proof that the arrangement works.
Use it to move from isolated events to recurring structure. A policy, product, platform, clinic, school, or workplace can look functional at the center while remaining survivable only because someone downstream is improvising, masking, waiting, translating, proving, or breaking.
Glossary
What are its primitives?
These are the smallest reusable parts of the theory. Pick the primitive that best names the mechanism in front of you, then test it against the linked essays until the pattern becomes portable across domains.
- Crumple zone
- The person or population made to absorb a system’s failures so the institution can keep its surface of competence intact. Use it to ask whose body, time, or stability is making the arrangement look orderly. See Why Systems Lean on Our Backs and Pending: The political economy of waiting.
- Burden transfer
- The movement of risk, ambiguity, admin work, emotional labor, or delay from a system onto people with less leverage. Use it when an institution solves its own problem by turning it into someone else’s homework. See Don’t Let Reassurance Do Engineering's Job and If Every User Is a Potential Threat....
- Coercion as cost-loaded options
- Coercion often appears not as prohibition but as a menu whose usable choices carry punishing financial, administrative, social, or psychological costs. Use it to test whether an option exists only for people who can afford the damage of taking it. See You Were Free to Choose and You Don’t Have the Right.
- Inhabitable action / uninhabitable acts
- An action is only real if someone can survive being the one who takes it; if the protective move requires becoming disloyal, selfish, or unsafe, the act has been made uninhabitable. Use it to see why a formally available move does not become a livable one. See Uninhabitable Acts and Modern Adulthood.
- Livability vs permission
- Systems often grant permission on paper while withholding the conditions that would make using it livable. Use it to distinguish a nominal right from a survivable path through the institution. See You Don’t Have the Right and Pending: The political economy of waiting.
- Non-use as evidentiary distortion
- When people avoid an option because using it is dangerous, exhausting, or identity-shattering, institutions often treat that non-use as evidence that the option was unnecessary. Use it to track how absence gets converted into proof for the system. See You Were Free to Choose and Incidence Is Not Suffering.
- Conscience as stopping point
- Human beings stop where a system would keep executing: at the point where an action becomes morally or existentially unlivable to inhabit. Use it to read refusal, hesitation, or burnout as evidence of a limit the institution is trying to overrun. See Pretending Is Half the Job and Uninhabitable Acts.
- Permission structure
- The background story that tells a system which harms count as normal, necessary, or justified before any individual case is reviewed. Use it to ask what violence, neglect, or abandonment the institution has already decided to tolerate. See “We Condemn the Excesses” and Emergence Is an Excuse.
- Recourse
- A real path for contesting harm, getting an exception, repairing damage, or changing the rule instead of merely enduring it. Use it to separate systems that can be corrected from systems that only reroute people back into procedure. See If Every User Is a Potential Threat... and Legitimacy Machine.
- Proof-based harm
- Injury created when people must repeatedly document what is already true before they can access care, rights, or relief. Use it to notice when verification becomes a way of rationing recognition. See Legitimacy Machine and Incidence Is Not Suffering.
Visual model
Operational loop
Read the loop clockwise: what begins as formal permission can return as institutional self-justification once the cost of use produces non-use that gets misread as consent.
View source
%% title: The operational loop %% caption: Formal permission can preserve legitimacy on paper while the lived cost of using it produces non-use that institutions later treat as consent. flowchart LR A[Formal Permission] --> B[Cost of Use] B --> C[Identity Damage] C --> D[Non-Use] D --> E[Misread as Consent] E --> A
Focused module
Why non-use is not consent
A permission that people cannot safely inhabit becomes evidence against itself unless you track the loop all the way through.
Institutions often point to low uptake as if it settles the question: if people are not using the option, maybe the option was unnecessary. But that reading skips the key step. Many permissions are formally present while remaining costly to inhabit in practice, because using them means retaliation, administrative burden, stigma, lost income, exposure, or relational fallout.
Once that cost is high enough, people adapt by withdrawing. They stay quiet, delay, mask, absorb the loss, or decide it is safer not to ask. The institution then records the silence without recording the pressure that produced it. Non-use gets counted as preference, and the absence of visible demand gets recycled into justification for keeping support thin.
The right diagnostic question is not whether an option exists on paper. It is whether someone can survive being the one who uses it. If they cannot, then low uptake is not proof of legitimacy; it is often the footprint of coercion. For the longer essay version of this argument, start with You Were Free to Choose.
View source
%% title: Permission-to-non-use loop %% caption: Formal permission collapses into non-use when the cost of exercising it remains dangerous, and institutions then misread that retreat as proof the option was unnecessary. flowchart TD A[Formal permission exists] --> B[Person considers using it] B --> C{Would using it stay livable?} C -->|No| D[Risk of punishment,<br/>exhaustion, exposure] D --> E[Withdrawal, delay,<br/>silence, self-suppression] E --> F[Institution records non-use] F --> G["See? Nobody needed it."] G --> H[Support stays missing] H --> C C -->|Yes, with backing| I[Use becomes survivable] I --> J[Demand for recourse,<br/>accommodation, redesign]
Recognition
Where you’ve seen this
Use these as quick sightings: the same transfer shows up across domains even when the language changes.
Workplace
Watch for performance language that turns structural failure into someone’s private burden.
- Metrics become permission.
- Compliance gets renamed judgment.
- The fallback worker absorbs the miss.
Healthcare
Notice when access depends less on need than on surviving proof, delay, and format.
- Access depends on documentation, not need.
- Delay presents itself as neutrality.
- Care is routed through institutional liability.
Tech
Track the moment optimization language outruns accountability, recourse, or refusal.
- Optimization outranks accountability.
- Prediction gets sold as wisdom.
- Users inherit system fragility.
Relationships
Read the small rules around care, disclosure, and exit before treating intimacy as neutral.
- Control gets framed as protection.
- Convenience hides unequal cost.
- One person becomes the shock absorber.
Use
Diagnostic questions
Move from recognition into use by asking what the system demands, hides, and punishes when someone tries to survive inside it.
Who pays for the delay?
If the wait compounds risk for the person asking for help while the institution stays calm, the system is using time as a sorting tool.
What happens if someone uses this right?
If exercising the option threatens income, belonging, safety, or identity, permission exists on paper more than in life.
What hidden sacrifice makes this system look smooth?
If the process only works because someone downstream absorbs admin work, emotional labor, or fallout, count that sacrifice as part of the design.
What identity is required to survive here?
If someone must become obedient, self-erasing, endlessly documentable, or exception-worthy to make it through, the system is selecting for survivability, not justice.
How should a reader use it?
Use this page as a toolkit, not as a creed. Start with the primitive that most cleanly names the mechanism you are seeing, use the loop to test how the institution converts permission into pressure, and then compare that pattern against the essays linked here until the structure becomes legible across domains.
The aim is analytic reuse. Once you can recognize burden transfer, cost-loaded options, non-use as evidentiary distortion, or conscience as a stopping point in one setting, you can carry the same tool into another and ask what kind of redesign, recourse, or refusal would interrupt the loop.
- Start with a primitive from the glossary: pick the smallest term that names what you are seeing most clearly.
- Use that primitive as a diagnosis: ask how it operates here, what it makes visible, and which hidden cost or legitimacy claim it explains.
- Then open one of the linked archive examples and compare the pattern across domains until the recurring structure becomes easier to recognize on sight.
If you are new, move from primitive → loop → archive example. The essays will start to read less like isolated arguments and more like repeated sightings of the same machinery.