Recognition first
If the pattern already feels familiar, start here.
This page is for the moment when you do not need more theory first; you need a cleaner name for something you already keep running into and a way to convert that experience into a contestable claim.
Recognition is not just noticing. It is the practical epistemology that determines whether lived costs become legible as coercion or get dismissed as personal failure.
Symptom switchboard
What are you seeing?
Start with the live symptom if the domain is less clear than the feeling. Each card routes into the closest path, concept map, and anchor reading so users can move from recognition into comparison without guessing where to begin.
Use this when the route stays technically open but the real process becomes reminders, resubmissions, escalation, and waiting.
- Treat delay as governance, not just bad service.
- Look for pending states, private follow-up labor, and one-more-document loops.
- Start with the delay path if the live feeling is procedural limbo.
Open this when the system looks organized only because you, your family, or a frontline worker became the maintenance layer.
- Hidden cleanup is part of the system, not private resilience.
- Trace paperwork, translation, coordination, and emotional regulation as transferred work.
- Start with burden when smoothness depends on somebody else absorbing the mess.
Open the Burden path · Open the Burden map · Read The Capture of Maintenance
Start here when a choice looks available on paper while using it would cost safety, belonging, income, coherence, or basic stability.
- Formal permission is not the same thing as a survivable route.
- Silence, delay, masking, or withdrawal may record pressure rather than preference.
- Use survivability when the official answer is “you were allowed to choose.”
Open the Survivability path · Open the Survivability map · Read You Were Free to Choose
Use this when recognition itself becomes labor and relief stays one more proof cycle away no matter what you submit.
- Repeated verification is a cost, not a neutral step.
- Ask whether proof is functioning as rationing, delay, or a tax on truth.
- This often sits between the delay and survivability clusters.
Open the questions guide · Open the Delay map · Read Proof-Based Harm
Open this when empathy, values language, or ethics branding seems designed to soften conflict without altering the structure causing harm.
- Reassurance is not repair.
- Look for concern that manages public feeling while obligation stays unchanged.
- Use care theater when the response changes tone but not terms.
Open the Care path · Open the Care map · Read Don’t Let Reassurance Do Engineering’s Job
Start here when the system can act quickly, but reversal, rollback, or repair is slow, manual, and effectively unreachable.
- Fast harm and slow repair usually indicate a structural asymmetry, not a one-off failure.
- Look for missing stopping points, weak appeals, and no proportional rollback capacity.
- Use reversibility when the live question is whether the system can still stop itself.
Open the Reversibility path · Open the Reversibility map · Read You Can Design Harm Out
Use this when power is hard to point at because it has settled into a category, workflow, ranking, or default that now feels like the background.
- Ambient coercion often arrives as convenience, legibility, or sensible defaults.
- Ask what the system pre-decides before anyone reaches the formal choice point.
- Use infrastructural power when the rule is hiding inside the setup.
Open the Infrastructural Power path · Open the Infrastructural Power map · Open the AI systems guide
Recognition
Where you’ve seen this
Start with the one that feels obvious on sight. Then ask: what evidence would this arrangement currently refuse to count as coercion?
You can feel the pattern when the team misses become your private flexibility problem.
- The deadline slips, but the fix is your unpaid cleanup.
- “Be proactive” means absorb the staffing gap without naming it.
- The calm dashboard depends on a fallback worker eating the mess.
You can see it when getting help depends less on need than on surviving paperwork, proof, and waiting.
- Being sick is not enough; you have to become documentable first.
- The wait is framed as neutral while your condition absorbs the cost.
- Care gets routed through liability, billing, and gatekeeping before relief.
You are inside the pattern when process stays immaculate by making you carry confusion, repetition, and delay.
- Every form says almost yes while sending you somewhere else.
- Missing one document becomes your failure, not the system’s design.
- The institution keeps its procedural calm while you absorb the uncertainty.
You recognize it when care comes with invisible rules about soothing, proving, staying quiet, or making things easy.
- “I’m just worried about you” starts doing the work of control.
- Convenience for one person becomes constant adaptation for the other.
- One person turns into the emotional shock absorber for the whole arrangement.
Next moves
Go one step deeper from recognition
Once a pattern clicks, choose whether you want the full theory, the onboarding version, or a portable tool.
Open the standalone theory page when you want the legitimacy test, livability argument, burden transfer account, non-use claim, required selves, and usable recourse in one uninterrupted statement.
Open Start here when you want the glossary, recognition examples, and archive entry points in one guided page.
Use the standalone field guide when you want the shortest test for options that are visible, praised, and still unusable.
Use the portable diagnostic guide when you want reusable questions for any clinic, workplace, app, bureaucracy, or policy.
Use the archive to trace the same pattern across work, medicine, bureaucracy, care, and technology.