Reference page
Start with /start-here first; use this page when you want the longer reference version of the framework.
The canonical onboarding guide lives at /start-here. That page now carries the core claim, primitives, main loop, and a practical module for how to use the archive without an extra guide hop.
This reference page exists for readers who want the canonical diagrams, the framing contrasts, and the full five-test index after that first pass.
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.
The result is a method for reading institutions through burden, livability, recourse, delay, standing, and maintenance rather than through public justification alone.
Canonical diagram
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 LR 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
Main interventions
The main discourses this framework intervenes in
These are the recurring debates the site is trying to shift. Each one moves from a familiar public argument toward a test about cost, livability, burden, or power.
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.
Whether participation, agreement, or continued compliance proves fairness.
- Old discourse: continued participation is treated as proof the arrangement is acceptable.
- Why it stalls: people stay inside systems they cannot safely leave all the time.
- Reframe: ask what conditions produced the apparent consent and what costs silence is hiding.
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.
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.
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.
Whether delay, review, and administrative process are impartial, or active techniques of control.
- Old discourse: procedure is framed 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.
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.
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.
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.
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.
Key tests
The five tests to carry into the essays
These are the longer reference versions of the tests that /start-here introduces in a quicker, easier-to-scan form.
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.
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.
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.
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.
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.
Diagnose → act
Action outcomes after the five tests
Use this matrix to convert diagnostic findings into practical next steps without leaving the framework at the level of description.
Pathways
Use the archive by idea
Once the framework feels clear, choose the topic that best matches the pattern you want to follow next.
Follow hidden upkeep, maintenance, and transferred strain across the archive.
Track the gap between formal permission and actions people can actually inhabit.
See how waiting, paperwork, and procedural calm become governance tools.
Read essays about rollback, recourse, stopping points, and repair.
Study the gap between sounding humane and building humane conditions.
Follow how power settles into defaults, categories, and ambient systems.
Synthesis guides
Use the archive by structure, not only by path
These synthesis pages compare essays across domains so readers leave with a structural overview, not just a single argumentative thread.
Maps the archive’s main claim, recurring mechanisms, and anchor essays into one comparative overview.
Shows how healthcare essays converge through proof-based harm, delay, burden transfer, care theater, and livability.
Compares the archive’s account of coercion across healthcare, work, infrastructure, and other domains.
How to use this reference page
Use this page after /start-here, not instead of it. Come here when you want the longer framing language, the discourse contrasts, or a reference sheet for the five tests.
The goal is legibility. Once you can recognize burden transfer, unusable options, care theater, or infrastructural power in one setting, you can carry the same test into another.
- Begin on /start-here if you need the compact first-stop version of the framework.
- Name the mechanism: burden, survivability, delay, reversibility, standing, or time.
- Ask what the arrangement demands from the people who must live inside it.
- Use the pathways and essays to compare that pattern across domains until the structure becomes portable.