Questions this pattern makes askable
- Where did power become architecture, default procedure, or background expectation instead of an explicit command?
- Which systems shape the field of possibility before anyone argues about choice?
- What is being presented as neutral even though it quietly arranges dependence, exposure, or compliance?
Read in this order
Infrastructural power
For when the question is not just who decided, but what architecture made that decision feel inevitable.
For readers who want the systems layer: how force becomes routine, default, category, platform, or ambient constraint before any explicit command appears.
- Technologies are Crystallized Politics
- Mesopower and the Shaping of Possibility
- Universality Disincentivizes Surveillance
- Against Technocracy Resisting rule by expertise is not anti-science or anti-technology; it is a defense of democracy
- Designing Systems Where Coercion Is Structurally Impossible
- The Worldview with a Gun No single ontology—vendor or otherwise—should monopolize state violence.
After the path, open the coercion synthesis or the reversibility path if you want to connect ambient power to design constraints and possible points of repair.
Mechanisms
How this pattern runs
Named mechanisms in this pattern. Each one has a checklist for telling whether you are inside it.
Seemingly Neutral Systems
Narrates itself as objectivity, data, procedure, the algorithm, due process.
Is the outcome attributed to a process, algorithm, or system rather than a person?
Administrative Homelessness
Narrates itself as security, verification, fraud prevention.
Can you prove you exist to the system that says you don't?
Vocabulary
- Mesopower
- Seemingly neutral systems
- Post-user web
- Infrastructural power
More in this pattern
Other essays that name it
-
Why neutrality isn’t fairness—and what it hides when institutions say it is.
-
The interface is dying because the “User” is obsolete. On the post-user web, AI agents, friction economics, and the rise of adversarial infrastructure.