Coercion synthesis
The archive’s coercion model: domination often works by making the costs of refusal, exit, or self-protection too high to bear.
The essays on coercion argue that force does not need to appear as an explicit command. It can settle into infrastructure, defaults, dependency, paperwork, timing, and the social penalties attached to saying no. Permission is not freedom.
Across domains, the question is not only “what is forbidden?” but also “what remains technically available while becoming socially, economically, or administratively uninhabitable?” Systems are defined by the selves they require.
Recurring mechanisms
The recurring mechanisms in the archive’s model of coercion
These mechanisms let you compare coercion across healthcare, labor, platforms, bureaucracy, and intimate arrangements without collapsing the differences between them.
Ban → cost-loaded option
A person may be “free” in the narrow formal sense while every usable path out carries costs they cannot safely absorb.
- What choice remains technically available but predictably punishing?
- Who can afford to exercise the option, and who cannot?
- Which penalties make the option unusable without openly banning it?
Autonomy story → engineered dependence
Institutions gain coercive power when they control the conditions of care, income, status, or access that people need in order to remain intact.
- What dependence is being converted into compliance pressure?
- What would exit actually cost here?
- How does the system make self-protection feel like self-destruction?
Command → infrastructure
Platforms, forms, categories, and procedures can quietly set the field of action long before anyone gives an order.
- Where did power harden into background architecture?
- Which defaults are steering people without overt confrontation?
- How does the interface hide the governing structure?
Withdrawal → misread consent
When using a route becomes too costly, silence and withdrawal are often footprints of coercion rather than proof that the option was unnecessary.
- What retreat is being misread as preference?
- How is attrition feeding the institution’s self-justification?
- What would uptake look like if the option were genuinely livable?
Choice story → required self
Coercion becomes visible when survival demands cheerfulness, obedience, endless proof, strategic silence, or self-erasure.
- Who must become smaller, calmer, or more legible to stay safe?
- What adaptation is being mistaken for consent or maturity?
- When does refusal become uninhabitable to perform?
This model makes coercion comparative: it becomes possible to see family resemblances between medical systems, labor systems, software defaults, and bureaucratic procedures without pretending they are identical.
Representative essays
Representative coercion anchors
These essays make the coercion model portable across different domains of life and institutional design.
The clearest argument for why formally voluntary choices can still be coercive.
Shows how rights discourse can obscure the dependency structures that make self-protection unusable.
Tracks how mid-level systems shape the field of action before explicit commands enter the scene.
Pushes the archive from diagnosis toward institutional form by asking what design would interrupt coercive dependence.
What changes when these essays are read together
The essays stop treating coercion as an edge case reserved for obvious violence. Read together, they show coercion as a patterned way of organizing options: make exit expensive, make refusal isolating, make proof endless, make default participation easy, then point to the remaining formal permission as proof of freedom.
That synthesis matters because it gives the archive a portable account of domination. The same lens can be carried into healthcare, work, platforms, public administration, or personal life: not to flatten them into one thing, but to compare how costs, dependencies, and required selves are being arranged in each domain.