The debate usually defaults to raw intelligence or processing efficiency. Systems optimize better. They scale endlessly. On those terms, humans have already lost.

The actual divergence happens elsewhere.

Systems can act without having to live inside what their actions mean. Humans cannot.

A system executes a command or processes an outcome. It never has to ask: What does this make me? For a human, that constraint dictates everything. We do not evaluate action by outcome alone; we evaluate it by what it turns us into. A choice can be correct, even rewarded, and still feel impossible because performing it requires becoming someone we cannot bear being.

The true barrier to action is rarely Can I? It is more often What would it make me if I did this?

Speak up, and become disloyal.

Leave, and become unreliable.

The action exists, but the required identity is unlivable. Uninhabitable.

A computer, machine, system, or even an institution does not face this problem. It does not inhabit its actions. It can reverse itself overnight or optimize metrics that quietly degrade the people inside it, and nothing fractures internally.

If you assume humans are mere outcome-optimizers, control looks like a practice of restricting options. If humans are meaning-bound, control operates entirely differently. The most efficient way to govern behavior is not prohibition. It is making the protective act feel like selfishness, or the truthful act feel like disloyalty.

You do not need to close the door if you can make walking through it unlivable.

This explains the gridlock of modern institutions. We are told that once people are given rights and incentives, movement will follow. When it does not, the individual absorbs the blame. We call them fearful, passive, or lazy.

That diagnosis mistakes available action for inhabitable action.

An action is not functionally real just because it exists on paper. It is only real if a person can survive being the one who takes it. If using a right makes you unsafe or morally compromised, the option sits unused. That non-use is then cited as evidence that the right was not needed. The architecture disappears behind the appearance of choice.

Failing to recognize this means continually misreading structural failure as personal weakness.

It also leaves us blind to the demands of our own built environments. As social life routes itself through automated, legibility-hungry infrastructures, the pressure grows for humans to become frictionless too: faster, clearer, more compliant.

But a human being is not simply a slower system.

A system proceeds as long as the action works. A person stops when the action becomes unlivable, even if it works perfectly. We usually call that stopping point conscience.

Conscience is not an error in the human design. It is one of the last protections against a world organized entirely around execution.

The same feature that makes us capable of refusal makes us uniquely vulnerable. We remain in bad situations because leaving would collapse our sense of self. We fail to act not because the path is hidden, but because the self required to walk it has been made impossible.

Systems do not suffer this way. They do not break under meaning.

We do.

The defining boundary between a human and the systems that surround them is not optimization. It is that we are meaning-bound. We do not just act. We have to be able to live with the kind of actor an action makes us.

Systems [must] execute.

Human beings [must] inhabit.

And if we fail to defend that distinction, we will keep building systems that treat conscience as inefficiency, paralysis as preference, and domination as a problem of bad choice architecture.

​It is the calm indifference of the handbook. When a worker breaks under a regime of “flexible” overwork, or a patient reaches the end of an insurance appeal only to find a new wall of paperwork, the response from the center is rarely an admission of cruelty. It is a shrug of technical innocence.

​The explanation arrives late: you were free to choose.

​It is an elegant sentence, if you admire efficiency. It allows an institution to acknowledge that an option existed on paper while ignoring that it had become unusable in practice. The door was unlocked. The policy was posted. No one physically barred the exit. Therefore, the logic goes, the arrangement was voluntary. Responsibility for the outcome—the debt, the resignation, the silence—is returned to the person who failed to use the “available” option.

​This logic depends on a convenient fiction about human agency. It imagines people making decisions in a vacuum, possessing enough energy and protection from retaliation to treat formal options as real ones. As long as an action is not explicitly forbidden, the person is said to be free.

​But modern institutions rarely need to forbid very much. Over time, they have evolved something more effective: resistance becomes expensive.

​Power in complex systems is often exercised by how costs accumulate. A right that exists in law but requires months of paperwork is not much of a right. A complaint procedure that formally permits reports of abuse, while making it practically inevitable that the reporter will be marked as a problem, is not a remedy. In these settings, coercion does not appear as a locked gate. It appears as friction.

​The option remains intact, but the system has raised its price.

​That is the deeper dishonesty of the defense. It takes structural difficulty and redescribes it as a test of personal character. If the worker did not report the abuse, perhaps they lacked courage. If the patient did not complete the appeal, perhaps they didn’t want treatment badly enough. What disappears is the system itself: its opacity, its predictable friction, and the way the burden naturally transfers onto the person already under strain. The individual is left to bear the moral weight of a calculation they were never meant to win.

​This is why the language of choice is so misleading. It does not merely describe agency; it obscures the conditions under which agency is exercised. Endurance is treated as endorsement. Compliance begins to look like legitimacy.

​A serious account of freedom asks more than whether the door was technically unlocked. It asks what the system demanded from the person standing there. Was the process understandable to someone already exhausted? Did using the option require gambling one’s income or reputation just to access a right supposedly already available? These are not sentimental questions. They are the minimum conditions for distinguishing a usable freedom from a decorative one.

A decent institution does more than refrain from blocking the right move. It lowers the predictable costs of taking it. It does not merely preserve an exit in theory. It makes the exit livable in practice.

​Until then, “choice” remains a ceremonial word: a bit of decorative trim on an architecture that reliably exonerates itself. “You were free to choose” will continue to sound like an expression of liberty while functioning mainly as a record of where the burden was left.

And it is usually left on the person with the least capacity to carry it.

​What this perspective largely overlooks is the duration of suffering. Because human beings do not experience harm as an isolated event on a timeline, but rather as time spent living through a crisis, the incidence of a problem tells us very little about its total impact.

The harm of a frozen bank account, for instance, is not contained within the instant the freeze occurs; it is the cumulative experience of the weeks or months during which a person is denied access to their resources. Similarly, an immigration backlog might appear in a database as a single case entry, but for the individual inside it, that entry represents years of suspended autonomy. From the system’s perspective, these are incidents; from the person’s perspective, they are stretches of life.

We can see this distinction in the administrative systems that organize modern life. Failures rarely arrive as dramatic, singular events. Instead, they take the form of “pending” states: fraud investigations, visa applications, insurance appeals, or benefit claims. From an institutional perspective, these are often treated as neutral procedural queues where a file enters and eventually produces an outcome. From the inside, however, the waiting is often the harm itself. While a case remains unresolved, a person may be unable to work, travel, access money, or receive medical treatment. The system sees a file awaiting resolution, but the person experiences months or years of a life lived in precarity.

​Once we account for duration, a measurement paradox appears: it is entirely possible for a society to reduce how often people encounter certain problems while simultaneously extending how long those problems last.

We can effectively create a world with fewer entries into hardship, but significantly longer “sentences” for those who do fall through the cracks.

Consider two hypothetical societies. In the first, administrative errors are common but are corrected within a week. In the second, such errors are much rarer, but the systems responsible for correcting them move so slowly that a mistake takes three years to resolve.

If we only count the frequency of incidents, the second society appears to be the more progressive one.

However, if we measure the total amount of human time spent inside those harms, the first society might actually be the more humane.

​Yet, public arguments about progress continue to rely almost exclusively on the first metric. By treating declining rates of poverty or disease as proof that suffering is shrinking, we overlook the “time-tax” of institutional failure. A backlog is not merely a list of cases; it is an accumulation of human time spent waiting for relief. Every stalled application or delayed appeal represents months or years during which a life remains constrained. In the standard statistical narrative, this time effectively disappears because the harm has already been “counted” at its inception.

​Ultimately, if duration is factored into our understanding of progress, the story becomes much harder to summarize with a single downward line on a chart.

Reducing the frequency of harm is a vital goal, but it is only half of the story. The other half is how quickly people can escape once harm begins. Progress should be measured not only by how rarely a life is disrupted, but by how much of that life is allowed to be consumed once the disruption occurs.

It rewards the ability to notice something is wrong and still keep things moving. To register harm without forcing repair. To accept delay without demanding a deadline. To speak in ways that can be acknowledged without binding anyone. This is how corridors work when nothing is denied and nothing is owed.

A lot of writing about institutions stops at the institution itself: the queue, the process, the “we hear you,” the waiting designed to outlast your stamina. That story is real.

I’m interested in the next layer: what that corridor trains in the person moving through it. When continuity is the goal, a system doesn’t need your refusal. It works better when refusal arrives already softened. Alarm becomes “a concern.” A demand becomes “feedback.” Clarity becomes “a perspective.” Language absorbs the failure without reversing it, the same way reassurance can substitute for obligation.

That competence gets praised as calm, professionalism, realism, and perspective. The praise sounds supportive. It also teaches you what not to do.

What follows is one way to name the gates that turn harm into something survivable, and then into something optional.

The first filter is calm.

“If you were competent, you’d stay calm.”

Calm is treated like proof of judgment. In practice, it functions as a cost signal.

People learn quickly what escalation costs. They watch what happens to the person who insists. Urgency gets reclassified as temperament. The conversation shifts away from the harm and toward whether the messenger is handling it well. Distress is permitted only if it never becomes operational, which is how systems train for an idealized, low-cost subject.

This is also where professionalism does its main work. Something happens that should stop the room, and it gets translated into something the plan can carry. A ticket. A backlog item. A follow-up. The harm isn’t denied. It’s converted into a format the calendar can absorb.

Because the meeting continues, the body learns a bad rule. Relief comes from returning to flow, not from repair.

The second filter is “actionable.”

“If it were serious, it would be actionable.”

“Actionable” sounds like a property of the problem. It isn’t. It’s a property of what the room is willing to bind itself to.

Actionability is shaped by hierarchy, liability management, staffing, and risk tolerance. This is where urgency runs into permission. A situation can be severe, documented, and ongoing, and still get downgraded into a concern or a learning. Acknowledgment is cheap. Obligation is expensive. You can be heard without gaining the kind of standing that forces a clock to start.

This is the corridor effect. Harm gets routed into steps. Responsibility diffuses. Time stretches until reversal becomes optional. Each step can be defended on its own. Together they form a path long enough that many people adapt, disengage, or disappear.

The third filter is the taboo against scenes.

“Adults don’t make scenes.”

A scene is framed as childishness or instability. Structurally, it’s often the moment harm stops being privately absorbable.

It’s when the cost returns to the room. When someone refuses to carry it silently. When the system can no longer keep the problem non-binding without admitting it won’t fix it.

That’s why scenes are taboo. They force decisions. They make inaction visible. They create liability. The person becomes the problem the moment the problem becomes expensive, which is how “reasonable” gets enforced as a governance category in ordinary life.

So the culture shames scenes not because they’re always wrong, but because they make harm expensive to ignore.

The fourth filter is realism.

“Being realistic means accepting how things work.”

This is the blessing that makes the arrangement feel adult rather than coerced.

“Realism” is often resignation with better branding. It’s what you call it after you’ve tried to force repair and learned what it costs. After timelines stretch. After responsibility diffuses. After your insistence becomes the problem.

Eventually you stop pushing not because you’re persuaded, but because you’re trained. The culture calls that training wisdom.

Two tools keep this stable:

1. One tool is complexity.

   Complexity is real. It also functions as deferral without refusal. “This is wrong” becomes “this is complicated.” Urgency drains away. Humility replaces commitment.

   Picture a meeting where a safety threshold is missed and risk rises. Instead of stopping, the room debates variance. An hour passes. The danger hasn’t changed. The room feels calmer. The hazard has been turned into an intellectual object, and that conversion becomes permission to proceed.

   Understanding becomes a solvent. Not a step toward repair, but a way to tolerate harm without changing course.

2. The second tool is pricing refusal.

   You’re told you can opt out, appeal, refuse, choose differently. Formally, you can. The penalties are calibrated. Refusal costs promotion, access, or reputation. Elsewhere it costs time, money, or safety. Choice exists on paper. Punishment exists in reality. Exit isn’t forbidden. It’s made unaffordable.

   Accepting those penalties gets framed as responsibility. Questioning the pricing model gets framed as immaturity.

   Options remain available, but livable only for people with surplus.

These filters produce a person who can acknowledge harm without making it bind.

Who keeps tone acceptable so the room stays comfortable. Who downgrades urgency into formats that can be filed and forgotten. Who accepts process without demanding deadlines. Who absorbs costs quietly and calls it growth.

On paper, this looks like maturity. In practice, it often means nothing has to change because of you.

You don’t have to psychoanalyze anyone to tell what kind of calm you’re looking at. Watch what happens after it.

After the calm, does anyone become obligated to act on a timeline?

If yes, calm followed responsibility. Repair is underway.

If no, everything stays optional. Slow. Diffuse. Socially gated. In that case, calm replaced responsibility. It made harm easier to carry without making it easier to fix, inside the basic asymmetry modern systems run on: harm can be done quickly, but correction is slow, discretionary, and procedurally gated—what it means, in practice, to not have the right.

A better definition of “adult” is not “non-disruptive.”

Calm isn’t the problem. Professionalism isn’t the problem. Understanding isn’t the problem.

The problem is when they substitute for repair.

A culture that treats non-disruption as the highest adult virtue will reliably produce adults who are excellent at tolerating unrepaired harm, and terrible at making it stop.

And once you see that, a lot of praise changes register.

Not: you did well.

But:

Thanks for not making this harder for us.

The phrase doesn’t open accountability. It closes it.

“Excess” labels violence as an execution error instead of a governance choice. It preserves the baseline—normal force, necessary force, lawful force—and isolates the spill as an aberration. The state sacrifices a tactic, sometimes a person, never the permission structure.

That is the move. It has a long history. It leaves bodies behind.

I. Amritsar, 1919: Condemn the Man, Keep the Empire

British troops fired into a trapped crowd at Jallianwala Bagh on April 13, 1919. The killings triggered outrage across India and Britain. Parliament held inquiries. The Hunter Commission condemned General Dyer’s actions. The British state removed Dyer from his command and barred him from further service in India.

But the empire didn’t revisit colonial authority. It didn’t renounce emergency powers. It didn’t treat mass coercion as the problem. It treated one general’s “mistaken notion of duty” as the problem, then continued governing with the same architecture.

The condemnation punished the spill and laundered the baseline.

II. Bloody Sunday, 1972: Time Does What Bullets Can’t

British soldiers killed unarmed civil rights marchers in Derry on January 30, 1972. The state moved quickly: it announced an inquiry and produced the Widgery Report within months. Widgery largely backed the soldiers’ account and helped close the case while the political stakes still burned. That speed mattered more than the content.

Then the state reopened it decades later. The Saville Inquiry (opened 1998, reported 2010) declared the killings unjustified; Prime Minister David Cameron apologized in Parliament.

The reversal didn’t threaten the underlying authority because time had already done its work. The families carried the cost; the state carried the continuity. Even now, prosecutions have largely failed, and courts cite evidentiary decay and delay as the limiting condition.

This is the upgraded form of the move: the state doesn’t need to lie forever. It only needs to defer truth until truth stops biting.

III. Kent State and Attica: The Domestic Pivot

In the United States, the move works just as well on domestic soil.

When the Ohio National Guard killed four students at Kent State in 1970, officials called it tragic. They also treated protest as the underlying provocation and “order” as the overriding necessity. The legal aftermath delivered diffusion: no criminal convictions for Guardsmen, a delayed civil settlement, and a statement of regret. The state condemned the bodies, kept the doctrine, and moved on.

At Attica in 1971, the cover-up was even sharper. New York State retook the prison, killing hostages and inmates alike. Officials initially blamed prisoners for the hostages’ deaths until autopsies proved law enforcement gunfire was responsible. The state ran the standard conversion: inquiry, findings, paperwork. Yet, the Attica Task Force pursued indictments heavily against inmates, while accountability for state violence remained minimal.

Attica proves the point cleanly: Condemnation doesn’t require enforcement. It requires narrative closure while leaving the pipeline untouched.

IV. Minneapolis, January 2026: The Protocol in Real Time

This is why Minneapolis matters. It shows the handoff happening right now.

On January 7, 2026, federal immigration enforcement killed Renée Good during “Operation Metro Surge.” Officials expressed regret. They promised review. The surge continued.

On January 24, 2026, federal officers shot Alex Pretti during a protest. DHS moved fast on the one thing that matters in these cycles: narrative. It declared the force justified before independent actors stabilized the evidence. Body-worn camera footage created contradictions that the declaration didn’t wait to answer.

Minnesota and its two largest cities sued to stop the surge. They led with evidence preservation. They went there first because everyone who has watched this movie knows where the system wins: evidence control, chain of custody, jurisdiction, and timeline.

Reporting describes a broader DHS pattern: officials repeatedly treat officer-involved shootings as justified before investigations conclude.

That isn’t “excess.” That is a permission structure.

The Maintenance Cycle

When officials say “we condemn the excesses,” they are buying three specific things:

1. Baseline Protection: They isolate the spill so nobody contests the tool.

2. Tempo Control: They replace pressure with procedure, letting time dilute the outrage.

3. Evidence Control: They centralize facts inside the apparatus while outsiders litigate for access.

They don’t need to ban dissent; they can price it. They don’t need to deny harm; they can docket it.

If nothing makes the next repetition harder:

• if authority doesn’t shrink

• if evidence doesn’t become automatically accessible

• if consequences don’t land quickly on insiders

then the phrase didn’t mark a boundary. It marked a maintenance cycle. It wasn’t a limit. It was a reload.

Reassurance in Failing Systems Is a Tool of Governance

​Reassurance typically signals kindness. However, in systems that cannot reliably repair harm, it serves a different function: it becomes a mechanism for deferring obligation. It allows an institution to acknowledge a user without committing to repair, ending the interaction without ending the failure.

​This is not a matter of tone; it is a matter of mechanics. When a system cannot correct itself on demand, soothing language begins doing structural work. It masks a lack of obligation with the appearance of care—offering recognition without bindability (no clock, no owner, no enforceable outcome).

​Don’t mistake the receipt for the product. Reassurance acknowledges you paid with your time; it is not the repair.

​Soft Language Resolves the Interaction Without Resolving the Failure

​The pattern is standard. Your account is frozen “for your protection,” your appeal is “under review,” or your ticket is “escalated” without resolution. Then comes the standard automated response:

​We are sorry. We understand. We take this seriously. We appreciate your patience.

​The outcome is rarely repair; it is recalibration. Your urgency is dampened, and your expectations are lowered. The institution secures what it needs—reduced conflict—without providing a path to restoration. Reassurance becomes a substitute for obligation. Harm is acknowledged, but no binding commitments follow. Nothing is owned, nothing is time-bound, and nothing materially changes.

​Delay Is Disguised as Kindness to Outlast Your Capacity

​This dynamic is dangerous because it allows delay to be presented as process. Delay is an effective form of power for an institution. If a system can act quickly to harm you but slowly to fix you—without consequence—it can remain wrong indefinitely. It does not need to win the argument; it only needs to outlast your capacity to pursue it.

​Reassurance makes that delay tolerable and easy to interpret as standard procedure. It converts “we are not capable of correcting this reliably” into “please be patient while we look into it.” Because the language is polite, the failure becomes harder to name, and the waiting period looks less hostile—even as access remains blocked.

Reassurance is Used to Reframe Persistence as Misconduct

​Reassurance enables a critical shift: it changes the framing of the interaction. Once a user has been “heard” and “reassured,” continued insistence begins to look unreasonable. If you keep pushing, you are no longer a person seeking correction; you become a person who refuses to let it go.

​Consequently, the system’s failure is obscured by your demeanor. The problem is no longer that the process cannot reliably produce repair; the problem becomes how you are behaving inside the process. The institution gains an excuse: it claims it wants to help, provided you are calmer or more grateful. It converts distress into disqualification, turning emotional regulation into a requirement for access.

That is not care. That is screening.

​Real Safety Requires Binding Mechanisms, Not Better Manners

Question: Does the reassurance bind the institution, or does it only soften the person?

​Legitimate reassurance is additive; it operates alongside enforceable structure. A clock starts when harm is reported. An owner is named. Interim protection applies while an investigation happens. A reversal path functions without extraordinary effort.

In a functioning system, an apology is secondary; the primary requirement is a clear, enforceable timeline for resolution.

We must stop letting reassurance do the job of engineering. Users do not need institutions to empathize; they need them to function.

The test of a system is not how politely it fails, but how reliably it repairs.

​For centuries, the social contract was built on a default setting of trust. You were assumed to be who you said you were, and you were assumed to be acting in good faith until you broke a rule. The burden of proof lay on the accuser.

​That architecture has been replaced.

​In the digital world, the default setting is now “Zero Trust.” This is a cybersecurity concept that has leaked into governance. In a Zero Trust architecture, no entity—inside or outside the perimeter—is trusted by default. Every request must be verified. Every interaction is conditional. Every user is treated as a potential threat until they perform the “proof of work” required to establish a temporary state of innocence.

This change was not motivated by ill will; it was a result of calculations.

​When you operate at the scale of billions, the “tail” of bad actors—spammers, fraudsters, state-sponsored hackers—is numerically larger than the entire population of most countries.

To a system administrator, the volume of attack traffic is indistinguishable from the volume of legitimate traffic.

​So, the system adapts. It builds a defensive wall that treats everyone as adversarial. The result is a society running on a new operating system: Guilty Until Verified.

Share

The Asymmetry of Trust

​The defining feature of this new regime is “Asymmetric Irreversibility.”

​Modern institutions have automated the power to suspect, but they have not automated the power to exonerate. A fraud filter can freeze a bank account in milliseconds. A content moderation bot can ban a decade-old creative business in the time it takes to render a pixel.

These systems operate at machine speed, with zero marginal cost per decision.

​But correction operates on human time.

​To fix the mistake, you must navigate a reversal path that is manual, scarce, and expensive. You must file tickets, wait on hold, upload documents, and plead with agents who often lack the authority to override the machine.

​This creates a terrifying structural reality: The system can destroy your status instantly and for free, but restoring it costs you days of your life.

​Because the institution pays nothing for the error, and you pay everything for the correction, the system learns a brutal lesson: it is always safer to block a good user than to let in a bad one. False positives are just “friction” for you; false negatives are “risk” for them.

​The Rationing of Justice

​Under this logic, “due process” ceases to be a right and becomes a scarce resource.

​Because human review is expensive, it is rationed. It is saved for the users who matter—the wealthy, the verified, the “continuous.” If you have a stable address, a ten-year phone number, a consistent biometric profile, and a standard income, you pass the friction filters. You have “slack.”

​If you are poor, transient, unbanked, or irregular, you trigger the immune system. You fall into the “tail.” And because you lack the resources to endure the reversal process, you are not just delayed; you are exiled.

We are seeing the rise of Administrative Homelessness: a class of people who are biologically alive but systemically dead. They cannot rent because of a zombie eviction record. They cannot work because of a background check error. They cannot bank because of a fraud flag. They are trapped in the database’s blind spot, unable to prove they exist.

​The Rationality of Bad Behavior

​This hostile architecture explains the bewildering shift in modern behavior. We are not watching a moral collapse; we are watching a rational adaptation to a system that assumes we are enemies.

Cheating becomes rational.

When the official recovery form is a dead end, but a bribe to a “dark web” consultant works, honesty becomes a survival disadvantage. If the system doesn’t play by the rules (it bans you without cause and refuses to hear your appeal), why should you? Cheating is no longer deviance; it is the only remaining form of agency.

Rage becomes pointless.

Anger is a social signal intended to shame the community into enforcing standards. But you are screaming at a mechanism. A “No-Reply” inbox cannot feel shame. A chatbot cannot be intimidated. Rage requires a recipient, and the system has designed itself to be un-reachable.

Politeness becomes humiliating.

To get help, you must perform submission. You must say “please” and “thank you” to the very entity that is destroying your livelihood. You must validate the system’s “Theater of Care”—the empathy scripts, the apology emails—just to keep your ticket open. It feels humiliating because it is humiliating: you are performing compliance to your own abuse.

Withdrawal starts to seem like the only sane move.

If every interaction carries a 0.1% chance of an uncorrectable “death penalty” (a lifetime ban, a frozen wallet), the only winning move is not to play. People stop posting. They stop verifying. They stop experimenting. They standardize their lives to fit the machine’s narrow template of a “good user.”

​The Mirror

​We are building a world where correctness is a luxury good, available only to those who can afford the “premium” tier of human support.

For everyone else, there is only the algorithm, which sees the world through a single, paranoid lens.

If the system treats every user as a potential threat, eventually the users return the favor. We stop trusting institutions. We assume every form is a trap, every delay is a lie, and every rule is a weapon.

​We are not losing our values. We are simply mirroring the machine.

• Your card declines at the grocery checkout.

• Your benefits don’t show up.

• Your account is suddenly “under review,” or

• A letter arrives announcing a decision you didn’t know was being made.

Most people have lived some version of this. In each case, the change is instant, but the “fix,” if it comes at all, lives somewhere behind: hold music, web forms, “high volume,” and a promise that someone will look at it.

Some of this is especially significant in high-speed, high-stakes systems. Power used to look like ‘a decision maker.’ Now it looks like an undo button you don’t get to press.

I’ve come to believe our political center of gravity has to move from who makes the decision to how hard the decision is to reverse.

Fast harm, slow repair

Systems can change your status in real time, but repair happens on human time, slowly, optionally, and mostly by making you do labor.1

Healthcare makes it easiest to prove, because the impact of delay isn’t just annoying—it can be biological:

Denials are common. In 2023, ACA marketplace insurers denied about 19% of in-network claims (roughly 1 in 5).

Appeals are rare. Across tens of millions of denials, consumers appeal at under 1%.

Appeals work. When people do appeal, denials are overturned at least partially 44% of the time—and prior auth appeals succeed in some studies 80%+ of the time.

Almost nobody appeals. When they do, they often win. Stop and think about what that means: The system can afford to be wrong 19% of the time because it knows 99% of people won’t fight back.

Which means the system doesn’t win by being right. It wins by making correction expensive enough that most people can’t afford to try.

Denials are cheap and fast. Appeals are slow and costly—in time, energy, uncertainty, and risk.

But in the Age of Appeals, the ones who push through often win.

This isn’t just “a healthcare problem.” It’s a design pattern across high-speed, high-stakes systems.

I see the same structure everywhere:

• Benefits: payments stop overnight; hearing dates land months later. Pennsylvania unemployment appeals can run 2–6 months. You still need rent and groceries during “the process.”

• Housing: the move from filing to removal can be weeks. Illinois eviction cases can reach hearing in 7 days. Appeals exist, but they often don’t automatically pause harm —so “you can appeal” becomes technically true while you’re already displaced.

• Platforms: a flag can erase an account and income instantly; “review” has no binding timeline and can stretch to “weeks or months”. The platform decides if you get your life back—and when.

• Immigration: removal and detention can move quickly while the system that hears contests is backlogged for years. The right to contest exists inside a machine designed to outpace it. As I explored in Pending: The Politics of Non-Decision, indefinite waiting becomes its own form of control.

The new class divide is ‘error survivability’

Here’s what that implies, and it’s uglier than it sounds:

In a high-speed administrative world, class is increasingly measured in error survivability: who can absorb or reverse a wrong decision before their life comes apart.

Who can afford to:

• Sit on hold for two hours on a Tuesday without getting fired

• Write in institutional jargon without melting down

• Front money while “it gets sorted out”

• Keep backup accounts, backup housing, backup childcare

• Pull in a lawyer, union rep, or journalist who gets a response

• Remain functional while their status is “pending”

So the real Wealth is Error Insurance.
The most important Education is Procedural Literacy.
The key determinant of Health is Capacity to Endure Bureaucracy.

The same formal right behaves like a safety net for some and a dare for others.2

Why the usual fixes miss

• Transparency: You can see the policy, understand the reason code, watch the status bar—and still have no leverage. Visibility is not power.

• Fairness metrics: A system can be “95% accurate” and still concentrate its errors on the people least able to contest them. For the person in the 5%, the metric is irrelevant. The question is: can you survive the mistake?

• More process: extra forms and extra layers usually just add more filters for time, literacy, stamina. If process isn’t coupled to binding timelines and real outcomes, it’s just a sorting mechanism for who gives up.

All of these change how systems talk about themselves without changing what they can be forced to do.

What would actually work?

☐ Automatic stays for survival stakes
If an appeal is active, harm should not proceed for money-for-food, housing, essential medical care, or physical presence in a country. Default to continuity until someone with real authority resolves it.

☐ Binding deadlines with teeth
Pick numbers (14 days, 30 days). Enforce them. Missing the deadline shouldn’t be a “service failure”—it should trigger reversal or meaningful penalty.

☐ Burden on the actor
If a system flips your status, it should carry the burden of proving it was right—rather than forcing you to prove it was wrong while you’re under duress.

☐ Proportional capacity
If you can act on 100,000 people/day, you must be able to process 100,000 appeals/day within guaranteed timelines. Otherwise “you can appeal” is brochure text.3

☐ Cost-shifting when wrong
When the institution is wrong, it should pay the person’s costs (fees, lost wages where applicable, and recognition of harm caused by delay). Right now almost all costs sit on the individual.

What rights actually are

A right isn’t a sentence on paper. A right is the machinery that moves when the sentence is violated.

I explored this more fully in On “Having a Right” to Something.

• Can you trigger it yourself, or do you need permission?

• Does it stop harm while it runs, or does harm continue during review?

• Is it timed to your crisis, or institutional convenience?

• Does it work when you’re broke, sick, exhausted, scared—or only when you’re composed and resourced?

• Does it make the institution pay when wrong, or just quietly walk it back?

If the answers are mostly “no,” then you don’t have a right.

You have a story about a right—plus a test of whether you can survive the cost of making it real.

The constitutional crisis nobody noticed

We’re living through the age where having rights and being able to enforce them have completely diverged—and most political discourse hasn’t noticed.

The formal constitution says one thing: you have rights, due process, equal protection. The operational constitution—what institutions can actually be forced to do—is something entirely different.

The gap is widening as decision speed increases while remedy speed stays constant. This creates a new form of domination: not through explicit denial of rights, but through making rights practically conditional on resources while maintaining formal universality.

Share

Under high-speed, high-scale systems, the most important political question is no longer just “who decides?” or “what do the rules say?”

It’s: when the system gets it wrong, who can force reversal, how fast, and at what cost to whom?

Everything we currently call “rights,” “fairness,” or “accountability” will either be rebuilt around that question—or go on existing mostly as pamphlet language.

Until that question sits at the center of how we talk about healthcare, housing, welfare, platforms, policing, immigration—and everything else—we’re just arguing about whose turn it is to get the pamphlet.

If you’ve lived the gap between having a formal right and being able to enforce it—or if you’re building systems trying to close that gap—I want to hear about it.

Leave a comment

This is part of ongoing work on what governance actually requires under conditions of high-speed, high-scale automated decision-making.

​But in the wild, your user is often on the “Sleepy Path.”

They are operating on 15% battery—biologically and technologically. They are scrolling one-handed while holding a crying baby, standing on a crowded train with spotty signal, or trying to pay a bill at 1:00 AM while panicked.

​They are in Cognitive Scarcity: a temporary drop in mental bandwidth caused by stress, fatigue, or distraction.

​When you design for the Hero User, you build fragility. When you design for the Sleepy User, you build resilience.1

​Here is the difference between a Hostile Interface and a Resilient Interface.

​Pattern 1: The Session Timeout

​The Concept: Amnesia vs. The Bookmark

​The Scenario: A user gets halfway through a complex application (insurance, taxes, housing) but gets distracted by real life. They return 20 minutes later.

​❌ The Hostile UI

The standard security pattern prioritizes the database over the human. It assumes the user is a security threat, rather than a busy person.

​The Experience: A cold modal stating “Session Expired.” When the user clicks “OK,” they are booted to the login screen. Their data is wiped. They quit.

​✅ The Resilient UI

The “Soft Landing” pattern assumes the distraction was involuntary. It offloads the memory burden from the user to the system.

​The Experience: A warm modal stating “Welcome back. We saved your progress.” The user enters their password, and the screen restores exactly to the field they were editing.

​Pattern 2: The Critical Error

​The Concept: Panic vs. Assurance

​The Scenario: A payment fails or a sync breaks. The system needs to inform the user that a process has stopped.

​❌ The Hostile UI

​This pattern pushes the cognitive load onto the user. It uses “System-Speak” (Error codes, Gateway Timeouts) that induces panic in non-technical users.

​The Experience: A red banner reading “Error 503: Gateway Timeout.”

The User Thinks: “Did I lose my money? If I click it again, will I be charged twice? I don’t have time to call support.”

​✅ The Resilient UI

​This pattern absorbs the ambiguity. It translates the technical failure into a financial status update.

​The Experience: A yellow banner reading “We couldn’t process this yet. Don’t worry, you haven’t been charged. We will auto-retry in 5 minutes.”

The User Thinks: “Okay. My money is safe. I can go to sleep.”

​Pattern 3: The Destructive Action

The Concept: Fear vs. Forgiveness

​The Scenario: The user hits a button that destroys data (Delete Project, Cancel Subscription, Remove User).

​❌ The Hostile UI

​This relies on the user reading fine print while rushing. It is a “Speed Trap”—it assumes the user is reading, but the user is scanning.

​The Experience: A modal asking “Are you sure? This cannot be undone.”

The Risk: Sleepy users operate on muscle memory. They see a modal, look for the bright red button, and click it before their prefrontal cortex registers the warning.

​✅ The Resilient UI

​This pattern accepts that “Fat Finger” mistakes happen. It replaces fear with time.

​The Experience: The item disappears immediately, but a toast notification appears: “Project moved to Trash. [Undo]”

The Principle: Never demand perfection from a tired person. Always offer a time machine.

​Pattern 4: The Login Loop

The Concept: The Memory Test vs. The Key

​The Scenario: The user is trying to log in on a new device but can’t remember their password.

​❌ The Hostile UI

​The “Memory Test.” It demands high-fidelity recall at the exact moment the user is likely frustrated.

​The Experience: A shaking text field saying “Password Incorrect. Try Again.”

The Result: The user tries three variations, gets locked out, and churns.

​✅ The Resilient UI

​The “Side Door.” If the user fails the primary challenge, the system automatically offers a lower-friction alternative.

​The Experience: After one failed attempt, the UI expands: “Looks like that wasn’t right. Want us to email you a login link instead?”

The Principle: Don’t make them bang on the lock. If the front door is stuck, open the window.

​The Designer’s Checklist for Low Energy

Designing for cognitive scarcity isn't about "dumbing down" the interface. It's about respecting your user's biological reality.

​When reviewing your flows, stress-test them against these three questions:

1. ​The “2 AM Test” If I looked at this screen at 2:00 AM with one eye open, is the primary action obvious? Or do I have to read a paragraph to understand what to do?

2. ​The “Tunnel Vision” Test Sleepy users ignore grey text. If I remove all the helper text and subheaders, do the buttons alone still tell the accurate story?

3. ​The “Safety Net” Test If I tap the wrong button by accident, how many seconds (and how many clicks) does it take to fix it?

​Attention is a finite resource. A respectful UI doesn’t spend it unless it has to.2

Subscribe now

​We have built an entire industry of thought leadership—spanning management theory, psychology, and tech design—dedicated to making the human operator tougher, faster, and more adaptable.

But viewed through the lens of Industrial Hygiene, this obsession with resilience is not a solution; it is a symptom of structural failure.

​Resilience is a subsidy. It is a tax the user pays to cover the cost of lazy engineering.

​When a system fails to resolve ambiguity, manage memory, or handle errors, it doesn’t just stop working. It borrows stability from the user. The user supplies the memory, the patience, and the metabolic energy to bridge the gap. This is not a character trait; it is a resource transfer. Institutions are balancing their books by burning your nervous system.

​To build truly safe systems, we must dismantle the five dominant myths that allow institutions to offload their maintenance costs onto us.

Myth 1: The Myth of “Grit”

• The Intellectual Source: Angela Duckworth (Grit).

• The Thesis: Perseverance and passion for long-term goals are the primary predictors of success.

My Critique:

Grit is a valid virtue for intrinsic pursuits (learning the violin, training for a marathon). It is a toxic metric for extrinsic friction (navigating a billing code).

When we demand “grit” from a nurse struggling with a medication dispenser, we are committing a category error. We are treating a Logistical Bottleneck as a Character Test. The “grit” required to endure bad software is not a sign of high character; it is a sign of high Failure Demand. Every ounce of grit spent fighting the interface is a tax paid on behalf of a vendor who didn’t finish the design.

Myth 2: The Myth of “Antifragility”

• ​The Intellectual Source: Nassim Taleb (Antifragile).

• The Thesis: Systems (and organisms) benefit from shocks and disorder; they should get stronger under stress.

My Critique:

Taleb’s physics apply to evolutionary systems, not administrative ones. A muscle grows when torn; a distinct cognitive process degrades when fragmented.

Administrative burden follows the laws of thermodynamics, not biology. It creates Entropy (waste heat), not Hypertrophy (growth). When a user faces high-frequency interruptions, they do not become “antifragile”; they become cognitively insolvent. Applying this logic to UX justifies negligence by framing burnout as a failure to adapt to chaos.

Myth 3: The Myth of “Atomic Habits”

• ​The Intellectual Source: James Clear (Atomic Habits), Charles Duhigg.

• The Thesis: You do not rise to the level of your goals; you fall to the level of your systems. Optimization comes from personal habit stacking.

My Critique:

This is true for the individual, but false for the operator of a hostile system. You cannot “habit stack” your way out of a Coercive Architecture.

If an algorithm is designed to interrupt you every 11 minutes (the average for hospital staff), no amount of personal discipline can maintain a flow state. The Institutional System (the alerts) always overwhelms the Personal System (the habits). Suggesting that a user can “optimize” their way through toxic infrastructure is a form of gaslighting that obscures the structural deficit.

Myth 4: The Myth of the “Growth Mindset”

• The Intellectual Source: Carol Dweck (Mindset).

• The Thesis: Abilities can be developed. Failure is just a learning opportunity.

My Critique:

The “Growth Mindset” presumes a rational environment where inputs yield outputs. But modern bureaucracy functions as “Sludge” (Cass Sunstein)—friction designed to be irrational and opaque.

Navigating a broken system acts as a Regressive Tax. It requires surplus resources (time, literacy, emotional reserve) that vulnerable users do not have. To tell a user who has hit a dead-end in a benefits portal to “adopt a growth mindset” is to ignore the material reality of the barrier. The barrier isn’t a learning opportunity; it’s a locked door.

Myth 5: The Myth of the “MVP” (Minimum Viable Product)

• ​The Intellectual Source: Eric Ries (The Lean Startup), Agile Orthodoxy.

• The Thesis: Move fast, ship early, and iterate based on user feedback.

My Critique:

In safety-critical environments, the MVP often functions as a Maximum Liability Product.

“Shipping to learn” creates a moral hazard where the cost of Quality Assurance (QA) is externalized onto the user. If the interface is confusing or the workflow is buggy, the user pays for the company’s “learning” with their own time, errors, and stress. It is a direct subsidy: the vendor saves money on testing, and the user pays for it in burnout.

Rejecting the Tax

​If a bridge requires a driver to be a stuntman to cross it safely, we do not start a training program for “Resilient Driving.” We fix the bridge.

​Yet in the digital world, we have accepted the stuntman standard. We have accepted that our tools will be hostile, extracting, and broken, and that it is our job to be tough enough to survive them.

​We must stop paying this tax.

The goal of design is not to build a user who can endure the friction.

The goal is to build a system that does not require endurance to use.

That era is ending, not because of a new technology, but because of a new speed.

The modern world has outpaced the biological capacity to “use” it. We are creatures of sequential processing; we read one thing at a time, we forget passwords, we get tired on hold. The institutions we interact with, however, operate on machine time. They can generate infinite administrative demand at near-zero marginal cost. They can wait forever. We cannot.

So the web selects for whatever can persist at machine speed.

In this frequency mismatch, the graphical user interface—the buttons, the forms, the layouts—stops being a tool for access and becomes a bottleneck. It becomes the place where our slowness gets harvested into abandonment.

So we are leaving the era of browsing the web. We are entering the era of deploying against it.

Share

If there is a true utility of “Personal AI,” it is not creativity; it is persistent agency. It is the ability to decouple your intent from your attention. The UI era required your attention to produce your rights; the agent era tries to sever that dependency. When you employ an AI agent, you are not asking it to “surf” the web. You are asking it to treat the web as a set of endpoints to be queried, triggered, and scraped.

You won’t navigate the airline’s cancellation maze. You will simply issue the command: “Refund this.” And the agent will do what a human cannot: it will execute without fatigue.

This shift changes the physics of the internet.

Historically, the friction of the interface was a business model. The dropout rate—the number of people who give up on a claim, a subscription cancellation, or a dispute—was a revenue stream. Companies relied on the fact that human patience is finite. But when consumers bring agents with effectively infinite patience, friction stops working as a filter.

The institutional response will be structural. To survive a world of high-frequency consumer agents, the web must make automation expensive.

We will likely see the decline of the “human-readable” web. Websites will become polymorphic—constantly shifting their underlying code, randomizing layouts, and obfuscating data to break scrapers. The visual web may degrade into a chaotic, heavy, shifting surface that is difficult for machines to parse and unpleasant for humans to look at.

The clarity of the interface was a luxury of the era when humans were the primary revenue source. In an adversarial era, clarity is a vulnerability.

This leads to the final, quiet transformation: the change in what it means to be “online.”

As agents take over the negotiation of daily life—buying, scheduling, disputing—the speed of interaction accelerates beyond human comprehension. Dispute resolution becomes high-frequency trading. The systems we rely on will operate in bursts of millisecond negotiations that we never see. When errors happen at that speed, they happen at scale.

But to keep this system secure, the price of entry will rise.

If behavior can be spoofed by AI, institutions will stop trusting behavior. They will demand the biological operator. The login will evolve into proof of life. Biometric verification will become the standard toll for access, not because the state is watching, but because the system must distinguish the Principal from the swarm.

This is the future of the interface: a bifurcated world.

On one side, a dark forest of bot-to-bot infrastructure—fast, invisible, hostile.1

On the other, walled gardens where humans can speak to humans—but only after proving, legally and biologically, that they are real.

We are not losing the internet. We are simply losing our place at its center.

The interface is not being replaced. It is being rendered unnecessary by systems that no longer require our presence to function. The web does not need us to look, click, or understand—only to authenticate, authorize, and occasionally absorb the consequences of decisions made elsewhere.

We are no longer the subject around which the system is organized. We are the constraint it routes around. In a world that runs on machine time, the human is not the user. We are the finite resource. We are the failure mode. We are the error the system is quietly learning how to avoid.

For a moment, something loosens in your chest. There is a record. There is proof you entered the channel. Whatever is happening to you—medical, financial, bureaucratic, interpersonal—has crossed a threshold from private trouble into recognized process.

Then the waiting begins.

The status changes just enough to keep you from concluding that nothing is happening. In review. Pending verification. Assigned to the appropriate team. You may get requests for more documentation—the same PDF again, a clearer copy, a different format, a resubmission because the first upload “didn’t go through.” Each loop arrives wrapped in courtesy.

And still: nothing becomes a decision.

This isn’t a story about a few cruel people. It’s a story about a common design: systems that are very good at producing signals of care, and very reluctant to produce outcomes that bind them.

Signals are cheap. Outcomes are costly.

Most institutions can generate the reassuring parts at near-zero cost:

• acknowledgments

• apologies

• status updates

• “we take this seriously”

• new ticket numbers

• new portals

• new “listening sessions”

Those signals aren’t fake. They matter psychologically. They reduce panic. They create the feeling that the situation has been admitted into a legitimate channel.

But the expensive part is different.

A real outcome costs something. It can set precedent. It can create legal exposure. It can force the organization to admit error in a way that travels. It can produce a written decision that can be appealed, audited, or compared to other cases.

So the system does what systems do: it produces the cheap thing abundantly, and rations the expensive thing.

That gap—cheap legitimacy, costly remedy—is where modern cruelty can live without anyone raising their voice.

Time binds you. Time does not bind them.

These processes typically have a clock for the claimant: respond in 48 hours, submit within 10 days, attend the appointment, upload by Friday.

But there is often no enforceable clock on the institution’s side. You can be told to wait without a deadline. You can be told it’s “in progress” with no point at which “in progress” becomes “overdue.”

That asymmetry does something strange: it lets your situation get worse while the system remains calm. Harm can intensify without triggering any obligation to act.

Your urgency exists in your life. The process remains serene.

Many systems don’t need a decision to function.

In the civics story we tell ourselves, conflict produces a decision: approval, denial, a reason-in-writing, something you can contest.

In a lot of modern systems, that isn’t required.

Delay can restrict you. Non-response can effectively deny you. You can lose access while the system never produces a written, appealable conclusion. Nothing solid is created—no “object” you can point to and say: this is what happened and this is what I’m contesting.

The power move is not always to deny. It’s to never finalize.

“Escalation” is often just movement, not change.

Most systems advertise escalation: talk to a supervisor, file an appeal, request review.

Here’s the test that matters:

Does escalation change who can decide?
Does it add a deadline the institution must meet?
Does it force a written outcome?

If not, escalation is mostly a coping feature. You get a new person, a new inbox, a new tone. The underlying authority stays the same. The system remains free to not decide.

Precision becomes a burden, not a virtue.

Another common pattern: the system can always ask for more specificity.

It’s cheap to request: “please clarify,” “provide more documentation,” “submit in a different format.”
It’s expensive to satisfy: time, executive function, money, coordination, emotional labor.

That creates endless failure points: one missing detail, one wrong file type, one missed call, one forgotten step. And when you stumble—predictably, under stress—the stumble is treated as your moral failure.

The system makes “keeping up” expensive and then calls the cost “responsibility.”

Dropout isn’t just what happens. It’s what the system uses.

Eventually, many people stop.

Not because they were satisfied. Because they’re exhausted. Because they’re sick. Because they have to work. Because their phone number changes. Because they can’t keep reproducing the same proof for a process that never acknowledges it has already been provided.

And here’s the inversion: many systems can close the case without deciding anything. “No response.” “Inactive.” “Abandoned.” “No further action.”

Your stopping becomes the thing that lets the system file the episode away as resolved.

Dropout is converted into consent after the fact; it “guesses” you didn’t actually need the help.

This is why it’s not a decision system. It’s a selection system.

When signals are cheap and outcomes are costly; when time binds only one side; when cases can end without decisions; when escalation doesn’t change authority; when precision demands create repeated failure points; when dropout can be recorded as closure—

the process isn’t mainly deciding who is right.

It is selecting for who can stay in the process without breaking.

Outcomes aren’t allocated by need, correctness, or entitlement. They’re allocated by survivability under delay.

Participation doesn’t reliably increase the probability of remedy. It reliably increases the carrying costs borne by the claimant.

In short:

When those conditions hold, governance is exercised through the managed distribution of exhaustion.

The design question that follows is not “How do we make the process nicer?”

It’s: where does the system become obligated to deliver an outcome—and what happens when it doesn’t?

If the answer is “nothing,” then the system is governing by non-settlement. And changing it won’t come from tone. It will come from clocks, real escalation, written decisions, and consequences for indefinite delay—because that’s where the power actually lives.

Until those mechanics change, the most vital move is a cognitive one: refusing to mistake the signal for the outcome. The polite email is not progress; it is a notification of stasis. The request for clarification is not a dialogue; it is a throttle.

Seeing the design clearly won’t make the wait shorter. But it might stop you from internalizing the system’s friction as your own moral failure. When you know you are trapped in a machine designed to test your endurance, the hardest—and most necessary—thing to do is refuse to participate in your own exhaustion.

It shifts authority away from the moment of decision, where a human being must look you in the eye and say “no,” and hides it in the architecture of the interface, where no one has to say anything at all.

This is a shift from judgment to syntax. The power to destroy a life no longer requires a verdict; it only requires a loading screen.

The Form is the Gatekeeper

In older bureaucracies, power was exercised through the event. The judge banged the gavel; the clerk stamped “DENIED.” It had an author. You could point to the person who rejected you and demand a reason.

In digital bureaucracy, the rejection happens before you even submit. Politics has migrated into the schema design: the drop-down menus, the required fields, the file-size limits.

The institution no longer needs to argue with you. It only needs to fail to recognize your format.

Subscribe now

If your life is too messy for the categories provided—if your employment history doesn’t fit the box, or your family structure defies the drop-down—you are not formally rejected. You are simply unprocessable. You hang in the void, waiting for a validation check that will never come.

The institution doesn’t need to be cruel. It just needs to be slow.

The Lie of “Efficiency”

We are told that moving services online makes them efficient. This is a lie. It is merely cost-shifting.

“Pending” transforms the applicant into an unpaid caseworker for their own survival. The labor of maintaining the file is exported entirely onto the vulnerable.

• You must compress your narrative into keywords.

• You must re-upload the documents when they expire.

• You must stitch the case back together every time the system dissolves it.

The institution appears efficient on its spreadsheet only because it has offloaded the cost of its own memory onto the person whose life is at stake.

Plausible Deniability

The modern system’s greatest weapon is not silence, but noise.

The system is incredibly talkative. It sends automated emails. It generates ticket numbers. It offers status trackers that sit endlessly at 10%. It performs responsiveness to mask the fact that it has suspended all obligation.

By keeping the ticket open, the institution maintains its moral vanity. It never has to be the “bad guy.” It never has to issue a hard denial that could be appealed or sued over. As long as the status is “In Progress,” they can claim they are helping you, even as they slowly bleed out your time.

Governance by Attrition

For the wealthy, a delay is a nuisance. For the precarious, a delay is a denial.

When the scholarship deadline passes, the surgery window closes, or the eviction notice arrives while the application is “under review,” the system has made a decision without ever issuing one.

This creates a class of the future-poor—people whose horizons are continuously liquidated by the wait.

This is governance by attrition. The system doesn’t have to exclude you; it only has to make you carry the weight of the process until you drop it. It manages scarcity not by saying “No,” but by waiting for you to give up.

Subscribe now

But the failures that dismantle lives rarely happen because an institution doesn’t believe you.

They happen because you lack standing.

In the legal sense, standing is the right to have a court hear your case. In the administrative sense, standing is the technical capacity to force a system to metabolize your reality into an obligation—a check written, a hold lifted, a record corrected, a flag removed. It is the difference between a claim that can be acknowledged and a claim that must be acted on.

Most people encounter this distinction not as theory, but as slow humiliation.

You gather receipts. You upload documents. You follow instructions. You stay polite. You escalate through the blessed channels. And still you watch nothing happen. Your claim is not refuted. It is not even denied. It simply never becomes actionable in a way that binds the institution to response.

This is not disbelief. It is nullification.

The non-decision regime

A denial is painful, but it is legible. It produces a decision artifact: a reason, a timestamp, a deadline, a path to review. “Pending” dissolves the handle. It sounds temporary. It sounds like progress. It keeps you checking, resubmitting, waiting—participating in a process that never commits.

Non-decision is the signature move of modern institutional failure: consequences without a decision. We call it bureaucracy, red tape, inefficiency. Those words flatter the machine. They imply justice exists underneath, and the pipe is merely clogged.

But in more and more domains, the pipe is the policy.

Modern institutions have learned to govern by controlling contestability: accepting input while avoiding being bound. They will generate reference numbers and case IDs. They will route you through portals that can ingest you. But they will not necessarily offer the one thing that turns “listening” into justice: a contestable decision that creates a record, triggers duties, and can be appealed.

The incentive structure is simple: Decisions create records. Records create contestability. Contestability creates exposure. Delay manages exposure.

And “pending” recruits your cooperation. It sounds provisional, so you keep participating—resubmitting documents, waiting on hold, reorganizing your life around a process that never commits. Non-decision is not merely a lack of action. It is a stable state that extracts compliance.

You aren’t screaming into a void. You are screaming into a buffer designed to keep you alive enough to stop escalating—designed to metabolize your claim into “handled” without ever allowing it to become binding.

The pipe is the policy

Governance has migrated out of courts and into workflows: submit a ticket, upload documentation, wrong channel, missed window, unable to verify, case closed. Rights do not exist as abstractions. They exist as successful traversal through a sequence of gates.

Each gate has a cost—time, literacy, documentation, connectivity, stable identifiers. When traversal costs are high, identical treatment at the interface still yields stratified results. Some people can pay the costs. Others can’t. Inequality is laundered through friction.

This is where the concept of the Happy Path becomes a machine for inequality. In systems design, the Happy Path is the default journey where no exceptions occur. But it’s a temporary status, not a permanent identity. One divorce, one fire, one eviction, one name mismatch is enough to convert you from a “user” into an edge case.

And the pipe treats edge cases as risk. Risk triggers friction. Friction produces delay. Delay produces drop-off. Drop-off is recorded as “resolved.”

Admissibility vs. truth

This is why contemporary injustice so often feels like unreality. You can be right and still lose. You can have the receipts and still fail.

Because what is being adjudicated is not truth. It is admissibility.

To understand standing, separate two questions we usually conflate:

Admissibility is what parses—what can be represented as an object in the system. Forms, fields, identity rails, time windows, evidence formats. The institution often doesn’t begin with “is this true?” but with “does this parse?” What cannot be represented cannot be decided.

Standing is what binds—what can force the system to produce a contestable disposition. You can be admissible—logged, routed, assigned a case ID—and still have no standing. You can be “in review” forever.

You can be 100% factually correct, holding physical proof in your hands, and still be functionally wrong because the system cannot ingest the format of your truth. The governing question flips from “Is this true?” to “Is this processable?”

Standing as an asset class

If standing is what makes reality contestable, then standing is a distributive resource. And because it is scarce, it behaves like an asset class.

When the ability to make a system bind is rationed, it becomes purchasable—not by bribing a clerk, but by buying legibility.

The wealthy do not only get better outcomes. They get more situations in which a wrong can be recognized as wrong, because they hold the portfolio of assets required to force the machine to bind: time to persist through latency, stable identifiers that satisfy proof regimes without triggering fraud flags, documentation continuity that prevents mismatch errors, and intermediaries whose job is to translate messy life into admissible packets.

This asset class compounds. Stable paperwork means fewer mismatches, fewer flags, and easier future standing. Precarity compounds the other way: volatility produces flags, flags produce gates, gates produce drop-off.

The precarious face the raw interface. They guess what the machine wants. They burn hours they don’t have. And when they finally drop, the institution records the outcome as “compliance failure”—as if endurance under administrative coercion were a character trait.

Contestability by design

If the problem were mainly misinformation, the remedy would be better information. But if the problem is standing—systems that accept inputs without incurring obligation—then the remedy is constraints.

At minimum, any institution with the power to materially affect a person’s life should be required to output a decision artifact within a bounded window. Call it a Decision Guarantee:

• Start the clock when input is accepted—and make it visible.

• Bound latency. “Pending” cannot persist beyond a fixed window.

• Forbid ghost closure. No case ends without a disposition artifact.

Within that window, the institution must output one of three states: Approve, Deny (with reasons and appeal path), or Request specific information (with exactly what is needed, a deadline, and a commitment to decide after).

Then ask of any system that governs you—benefits, credit, housing, employment, health care—not “do they listen?” but: What counts as admissible input? What artifacts create standing? When does the clock start? Can they close without deciding?

These questions sound technical because they are. Power lives in parsers, permissions, and queues.

The crisis is not only that the system doesn’t know you’re right. It’s that it hasn’t been forced to bind.

They publish principles, run trainings, hire “responsible” teams, and build high-fidelity dashboards to track harm. The language is polished, the intentions are often real, and the concern sounds sincere.

And yet the behavior rarely changes.

The issue isn’t always hypocrisy. In many organizations, “ethics” functions as a way to metabolize discomfort without altering the machine’s trajectory. Anxiety is converted into documentation, meetings, and process—so the system can keep moving at the same speed, in the same direction.1

This is Toothless Ethics: oversight that performs the rituals of responsibility without the power to force a sacrifice.

The Dashboard Trap

We often assume that if leaders could see harm clearly, they would stop it. So we build observability. We measure “toxic content,” “provider burnout,” and “bias incidents.”

But large systems do not reliably respond to visibility with correction. They often respond with management.

Once harm becomes a metric—numbers on a dashboard, incidents in a report—it can be treated not as a violation, but as an operational variable: How much can we absorb without consequences? Where is the line where it becomes expensive?

In that world, awareness doesn’t destabilize the machine. It stabilizes it. It teaches the organization exactly what it can get away with. As I argued in Assume Maximum Awareness, organizations that track harm with high fidelity often do so not to prevent it, but to price it—learning precisely how much damage they can absorb before consequences arrive.

The “Homemade Key”

You can often identify a toothless system by an architectural flaw: the coexistence of a primary safety protocol and a secondary, informal bypass.

In December 2023, inspectors at an Australian manufacturing facility found that safety interlocks on a CNC machine had been overridden with a homemade metal key. A worker had become trapped in the machine and suffered broken ribs. The safety system existed technically; the bypass existed practically, preserving throughput.2

The chilling part isn’t the key. It’s the logic. The key was homemade because the demand was structural. Someone built that key not to be malicious, but to keep the line moving.

In corporate governance, the “metal key” is the executive override.

If a safety rule can be bypassed via a private message to a founder, or a “special exception” for a major client during a deadline crunch, then the rule is not a constraint. It is etiquette.

At the interface level, this appears as design patterns that make refusal expensive—the digital equivalent of the homemade key, where saying “no” requires navigating deliberate friction while saying “yes” is one click away.

The Solution: Constraint Realism

We need to stop treating ethics as a culture problem—a matter of values and intent—and start treating it as a design problem.

I call this doctrine Constraint Realism.

It treats ethics as real only when it exists as a hard constraint on what actions remain available. Ethics is not defined by what a system claims to value, but by the profitable actions it has rendered impossible.

To evaluate whether an institution’s ethics are binding, do not look at its mission statement. Look for the Foregone Advantage:

Show me what you can no longer do.

• Show me the launch you canceled despite the revenue projection.

• Show me the “report” button that reverses a database state, rather than merely filing a ticket.

• Show me the remediation gate leadership couldn’t unlock.

If an organization cannot point to specific advantages it sacrificed because a constraint held, then its ethics are decorative: reputation management with better vocabulary.

The Care Subsidy

Systems without binding constraints often appear stable only because they rely on human compensatory labor to prevent failure.

I call this the Care Subsidy: the extraction of unpaid diligence from conscientious employees to bridge the gap between resource allocation and safety requirements. You see it in the nurse who stays late to secure a bed, or the moderator who absorbs psychological injury to clear a queue.

As I argued in You are the Crumple Zone Now, a system that depends on heroism to function safely is under-designed. It relies on exhausting its components to maintain integrity.

When that human infrastructure inevitably fails, institutions often reframe the structural deficit as individual noncompliance. Blame serves a functional purpose: it protects the design by locating failure in the person, ensuring that re-engineering is avoided.3

The Politics of “No”

Ultimately, this is a question of power: consent is not valid if refusal is not safe.

If opposing a dangerous course of action produces professional retaliation, then compliance is coerced. In such an environment, ethical discourse is delegitimized—not because the words are insincere, but because dissent carries a prohibitive cost.

We have to stop preaching and start engineering. We need organizations where “no” is a normal operational outcome, not a career-ending event.

And yes: that creates friction. It costs time, money, and flexibility. That isn’t a failure of ethics—it is the proof that ethics is real.

Because if your ethics never blocks a profitable action, never slows you down, and never forces you to accept a loss, then it isn’t binding.

It’s just a story the machine tells while it keeps running.

Related Essays:

• Assume Maximum Awareness — Why organizations measure harm to price it, not prevent it

• You are the Crumple Zone Now — On care subsidy and human infrastructure

• [Accept All] / [Reject All] — Interface-level constraint design

• Stricter in Love Than in Law — The Black-Box Alibi and accountability theater

​We tell ourselves that if the executives only saw the burnout rates in the ICU, if the board only understood the bias in the training data, if the policymakers only heard the stories from the front lines, they would act. We treat dysfunction as a knowledge deficit. We assume that the gap between “what is happening” and “what should happen” is a gap in information.

​Tragic Institutionalism begins by rejecting this comfort. It asserts a colder, more difficult premise: The system is not blind. It is optimized.

​In the digitized, data-saturated landscape of the modern organization, we must assume Maximum Awareness. The institution does not suffer from a lack of visibility into its own harms; it suffers from a calculated decision to tolerate them.

The Industrialization of Sight

​The “Ignorance Hypothesis”—the idea that leadership is unaware of ground truths—might have been true fifty years ago. Today, it is logically impossible.

​Modern institutions are panoptical. They possess industrialized telemetry that captures the granular reality of their operations in near real-time.

• ​In Healthcare: Hospital administrators do not need a nurse to tell them staffing is dangerous. They have dashboards showing nurse-to-patient ratios, call-light response times, medication error rates, and readmission statistics, all trended against payroll costs.

• ​In Tech: Platform executives do not need a whistleblower to tell them their product harms teens. They have A/B tests, engagement heatmaps, churn models, and sentiment analysis that quantify exactly how much psychological distress correlates with a 5% lift in ad revenue.

• ​In Logistics: Warehouse managers know exactly how many workers are skipping bathroom breaks. The productivity tracking software flags “time off task” down to the second.

​The data exists. It is collected, cleaned, stored, and visualized. The problem is not that this data doesn’t reach the top. The problem is what happens when it gets there.

​From Knowledge to Optimization

​When we assume the problem is ignorance, we assume that Knowledge + Power = Action.

​But in a tragic institution, the formula is different: Knowledge + Power = Pricing.

​When leadership reviews data on harm, they rarely view it as a moral crisis to be solved. They view it as a variable to be managed. They are not looking for “Zero Harm”; they are looking for the “Tolerable Harm Band.”

​They ask the rational questions of their role:

1. ​Is this illegal? (Or just “regulatory grey zone”?)

2. ​Will this cause a PR crisis? (Or just “low-level complaints”?)

3. ​Does the cost of fixing it exceed the cost of settling the lawsuits?

​Once the harm falls within the “tolerable” band—where the cost of settlements, attrition, and bad press is lower than the cost of structural change—the harm is “priced in.” It becomes a known operating expense.

​The burnout rate isn’t a surprise; it’s a budget line item for recruitment. The safety violations aren’t accidents; they are the calculated yield of an efficiency model.

​This is the “banality of optimization.” It is not malicious villains twirling mustaches. It is fiduciaries doing their legal job: maximizing value within the constraints of risk.

​The Ritual of Surprise

​If institutions are so aware, why do they seem so shocked when scandal breaks?

​Because “surprise” is a legal and reputational necessity.

​When a crisis goes public—a data leak, a mass walkout, a patient death—leadership performs the Ritual of Surprise. They issue statements about being “deeply concerned.” They launch “independent investigations” to “get to the bottom of this.”

​This performance serves two purposes:

1. ​Liability Shielding: Admitting “we knew this would happen” creates legal exposure (negligence or malice). Claiming “we were unaware” preserves the defense of incompetence, which is legally safer than complicity.

2. ​Preserving the Ignorance Myth: It invites the public and the workforce back into the comfortable fantasy. It suggests, “Now that we know, surely we will fix it.”

​It resets the clock. It buys another cycle of “listening tours” and “task forces” that result in performative tweaks rather than structural redesign.

Subscribe now

The Strategic Implication: Stop Teaching, Start Negotiating

​Why does this matter for the worker?

​Because if you believe the Ignorance Hypothesis, you will spend your energy on Education. You will write longer memos, gather more heartbreaking stories, and try to “raise awareness.” You will exhaust yourself trying to teach a lesson that has already been learned.

​If you accept the Maximum Awareness hypothesis, you realize that Education is a trap.

​You stop trying to “inform” leadership of the costs. You accept that they have already calculated the costs and decided you are going to pay them.

​This changes your strategy from Pedagogy to Leverage.

• ​You don’t write a memo about “moral distress”; you file a union grievance about “unsafe working conditions.”

• ​You don’t explain why a product is unethical; you refuse to sign the compliance certificate that allows it to launch.

• ​You don’t appeal to their better angels; you raise the material cost of the status quo until it is no longer “priced in.”

​There is no innocence in the modern institution. There is only design.

​To assume maximum awareness is painful. It requires admitting that the people in charge are not confused, but comfortable with the damage they are doing.

​But it is also liberating. It frees you from the exhausting, futile work of trying to be the “conscience” of a machine that has none. It allows you to see the terrain clearly:

You are not a teacher in a classroom of confused pupils.

You are a negotiator in a room where the other side has already run the numbers against you.

A worldview shouldn’t have a gun.

We have moved beyond the era where AI merely “informs” decisions. Proprietary ontologies—opaque systems that categorize people as “threats,” “militants,” or “risks”—have ceased to be just analytical tools. Wired into police dispatch, drone tasking, and prison controls, they have become the infrastructure through which state violence flows. These ontologies are not maps; they are rails guiding where violence falls.

Consider Palantir Gotham. The platform goes beyond aggregating warrants or social media; it synthesizes a reality where “impactful targets” literally light up on a screen, waiting for action. It decides whose debts signify risk, whose associates imply complicity, and whose presence on a street corner justifies suspicion. Cities from Los Angeles to Hesse, Germany, feed their databases into Gotham and inherit a vendor’s paranoid worldview under the guise of “visibility.”

For deeper background, see how police use Palantir, coverage of Palantir’s expansion in Germany, and legal analysis of Palantir’s influence in policing.

Axon Fusus extends this logic into real time, merging live camera feeds, drones, license plate readers, and body cameras into a unified surveillance nerve center. Automated alerts nudge officers toward intervention before any human hesitation can take hold. Axon markets Fusus as a “real-time intelligence platform” and infrastructure for “safer corrections,” yet reporting shows how it disproportionately saturates poor neighborhoods with watchful eyes (Gizmodo’s investigation).

In Gaza, the stakes become stark. +972 Magazine’s investigation of Lavender describes an AI system that assigned “militancy” scores between 1 and 100 to tens of thousands of Gazans—mostly men—churning bulk data into kill lists. In parallel, Gospel (Habsora) generated building and infrastructure targets at industrial tempo. Human “review” in this pipeline often amounted to roughly 20 seconds per target, checking only basics like gender and address, with a chilling tolerance for civilian casualties because the machine said target. At this pace, the “human in the loop” is a façade—a latency constraint, not a source of moral agency.

Once deployed, these systems convert ontology from a philosophical concept into the very fabric of violence. It becomes the street grid, the pattern of lives deemed expendable, the logic of what gets bombed first.

To understand its commercial scale, see the private companies quietly building a police state.

Manufacturing killability

These AI systems don’t merely predict risk—they manufacture killability. They distill complex political judgments into scores sold back to the state as objective truths.

In Gaza, this means mass surveillance turning into daily death lists, with officers instructed to treat these outputs “as if they were human decisions” (see the Lieber Institute’s symposium).

In the United States, prisons use Securus to eavesdrop on millions of calls, stripping context from slang, code-switching, and emotional venting to flag “imminent threats.” Investigations describe how AI systems now monitor communications in real time to forecast crimes (KSBY report, MIT Technology Review). The people subjected to this processing have no meaningful way to opt out.

On a more everyday level, tools like COMPAS label Black defendants as “high risk” at roughly double the rate of white defendants who did not reoffend, turning structural racism into mathematical fact. Chicago’s Strategic Subject List transforms histories of over-policing in Black and Latino communities into heat maps justifying intensified patrols for people who may have no violent record at all (legal critiques).

This is epistemic laundering: the state targets a population; the population generates data; the model trains on that data and tells the state, you were right to target them. Responsibility blurs and shifts from policymakers to “the system.” Whether the vendor is Palantir or an open-source engineer matters less than the fact that one ontology has been given the exclusive right to define who counts as dangerous. That is a monopoly over killability.

The feedback loop

Once the loop closes, the prophecy fulfills itself.

Police flood a “high-risk” zone. They make more arrests. The database logs the arrests and marks the area as even higher risk. More patrols follow. In Chicago, this was not a surprising side effect; it was how the Strategic Subject List and related systems were designed to operate.

Proprietary complexity makes this almost impossible to contest. What counts as a “gang indicator”? Which unpaid bill signals risk? Those definitions sit behind trade secrecy and NDAs. Securus converts slang into evidence; COMPAS turns structural racism into a risk score; Lavender can turn mere phone proximity into a death sentence. The nuance of why the data looks the way it does—poverty, segregation, coercion, colonial policy—vanishes. All that remains is the line: “The system found a pattern.”

Marketing language tidies up the rest. “Turnkey.” “Frictionless.” “Real-time.” Gotham promises seamlessness; Fusus sells speed. But friction is another word for due process. Seamlessness is simply the absence of oversight.

What these systems actually do is convert raw political fear—of crime, of terror, of the poor—into dashboard objectivity. Foucault’s “delinquent” is no longer just a subject described in a report; he is a data object, auto-generated and continuously updated.

For one legal-theoretical frame on this, see Artificial Intelligence Law through the Lens of Michel Foucault.

Langdon Winner warned that artifacts have politics. These dashboards are artifacts built to centralize power and treat those on the margins as noise. The faster they run, the more anything that doesn’t fit—duress, context, care—gets thrown away as “unstructured” data. The human loop shrinks. The appeal channel evaporates. Violence becomes automatic.

The false promise of the “good guy with an ontology”

One common response goes like this: We’re not against AI or analytics. We just need better data, better models, a more ethical vendor.

That line misses the point. The problem is not only which ontology is in charge, but that any single ontology is allowed to monopolize the path from data to force.

Even a “good” stack, run by well-meaning people, consolidates enormous power over what counts as threat, what counts as order, and whose life is treated as collateral. It replaces contestation with configuration. It narrows the field of possible futures to those compatible with one model’s worldview.

“Good guy” ethics, layered on top of unchallenged architecture, become a fig leaf. Innovation is celebrated; veto power is not. And a handful of technical elites end up acting as de facto legislators over life and death, without ever being named as such.

Break the monopoly

No single schema—state, vendor, or military—should ever be the sole map for the guns.

Chicago’s stalled consent decree shows how little leverage traditional oversight has over a force increasingly governed by black-box systems; oversight reporting has already documented how Chicago police failed to meet even basic reporting goals. Gaza shows what happens when a singular ontology is fused at scale to munitions and treated as “precision.”

Breaking this monopoly is not a matter of better messaging; it is structural work. It looks like:

• Banning turnkey pipelines that allow a single system to run data through one lens straight into lethal or carceral action.

• Imposing legal ceilings on automated tempo so that systems cannot outpace the possibility of human veto.

• Embedding poly-ontologies—competing legal, historical, community, and adversarial perspectives—into every chain from database to trigger, with real power to say “no.”

As I argue in “The In-House Ethicist”, formal boards and principles without structural veto power only enable co-optation. You cannot sprinkle ethics on top of a machine whose core function is to move faster than dissent.

Worldviews will always carve up reality. Guns, for now, are not going away. But the decision to fuse one proprietary hallucination to the trigger, the cage, and the drone is a choice. That choice can—and must—be refused.

That refusal is the core of Ethotechnics: designing systems so that inference never rules alone over force, and so that no single worldview is ever given a monopoly over who is allowed to live.

​The result is “sedimentary governance”: layers of older solutions sitting beneath new ones, slowing down the entire stack.

Think of a housing crisis layered over 1970s zoning law, 1990s environmental carve-outs, and 2008-era foreclosure relief programs—each one still half-alive in the codebase.

We end up running 21st-century software on 20th-century hardware, weighed down by 19th-century assumptions about permanence.

​Biology solved this problem eons ago.

Subscribe now

​In a healthy organism, death is not a failure; it is a maintenance function. The process is called apoptosis: programmed cell death.

​When a cell is damaged or simply obsolete, it doesn’t wait to be killed by external trauma. It initiates a specific sequence. It dismantles its own machinery, packages its resources, and signals its neighbors to recycle its matter. The exit is clean. The system remains stable.

The alternative is necrosis—traumatic, inflammatory rupture. Or worse: the cell refuses to cycle out at all, replicating without purpose until it destabilizes the host. In biology, we call that uncontrolled growth. In politics, we call it “bureaucracy,” but the mechanic is the same: the part prioritizes its survival over the health of the whole.

​We have built a specific type of fragility into our society by designing institutions that can only end via necrosis (collapse/crisis) rather than apoptosis (resolution).

​Coding for Mortality

If apoptosis is how a body stays healthy, we need the equivalent in law. That means shifting from Statutory Permanence to Statutory Provisionality: nothing runs forever by default. Every institution ships with an end-state baked into its code.

1. Expiration by Default
   Every charter, agency, and program should carry the genetic code for its own conclusion. Not a vague “review in five years,” but a real sunset. The default state of any government program should be winding down unless it can affirmatively prove it is still doing necessary work.

2. The Burden of Proof
   Right now, closing a zombie agency takes enormous political capital. Inertia protects the status quo. Apoptotic design flips the friction: renewal is what takes effort. If a directorate created to reduce homelessness sees homelessness rise for five years, it shouldn’t require a special vote to defund it. The funding falls off because the metrics were missed. The resolution is in the code, not in a heroic last-minute fight.

3. The Graceful Exit (Recycling)
   We fear institutional death because we imagine a void—lost jobs and vanished services. That’s necrosis. An apoptotic ending is planned. Assets are transferred or sold to nonprofits and local actors. Civil servants move into a “talent reserve” for new projects instead of being scattered. Data is archived and made usable. The institution doesn’t crash; it resolves.

Metabolic Governance

​The resistance to this is largely cultural: we tend to view endings as moral verdicts. Shutting down an agency looks like admitting it was a mistake. Sunsetting a law looks like disowning the values that created it.

So we choose the comfortable drift of irrelevance over the clarity of a conclusion. We tell ourselves this is compassionate. It isn’t—not for the people trying to live and work inside these obsolete structures. There is nothing compassionate about a public forced to navigate systems that no longer fit the world. There is nothing kind about trapping talented workers inside organizations that cannot succeed.

​A forest that suppresses every small fire eventually burns down. A body that refuses to recycle its cells eventually sickens. True stability is not the absence of change; it is the ability to metabolize the old to make room for the new.

​The 20th century was about building institutions that could last forever. The 21st century needs to build institutions that know how to die. We should be testing systems for how well they end, not just how well they scale.

But maintenance has not survived history unchanged. Somewhere between the factory floor and the modern state, between austerity budgets and glossy futurist manifestos, maintenance acquired a second meaning—one that looks like care but behaves like control. Today, two very different forms of maintenance share a single name, and much of our political confusion comes from mistaking the wrong one for the right one.

One is maintenance-as-sustenance: the kind I explored in To Be Is To Be Maintained. It creates slack, absorbs shocks, distributes load, and keeps people capable of weathering change. It is maintenance as the precondition for new worlds.

The other is maintenance-as-stasis: maintenance not as care but as containment, not as nourishment but as continuity enforcement. This is the maintenance I critiqued in The Death of Slack and Human as Crumple Zone—maintenance that treats people as buffers for system fragility and regards any rupture as a threat to be managed, suppressed, or moralized away.

The story of modernity is the story of how the first became eclipsed by the second—how the maintenance that keeps people alive was conscripted into the work of keeping institutions alive.

Subscribe now

From Rhythm to Regime

In pre-modern life, maintenance was cyclical and local: tending fields, mending tools, patching walls, restoring what time had worn down. It was the communal labor of staying in the world together. No one believed that repair could prevent change; repair existed to permit change by absorbing its costs.

Industrial capitalism broke that symmetry. A factory’s profitability depended on its machines running continuously. Maintenance was no longer cyclical; it was constant. No longer communal; it was professionalized. No longer adaptive; it became a discipline of compliance and record-keeping. The point wasn’t to sustain life but to sustain output.

Maintenance-as-stasis was born the moment maintenance became a precondition for profit.

Across the twentieth century, this logic expanded. States took responsibility for infrastructure, and public maintenance became the backbone of legitimacy. Roads must not buckle, bridges must not collapse, grids must not blink. Much of this was genuinely life-giving—maintenance-as-sustenance at scale—but it also centralized the question of whose life conditions were worth maintaining.1

Then came the neoliberal turn, which did not simply neglect maintenance but withdrew it strategically. Sociologist Ruth Wilson Gilmore calls this organized abandonment—the deliberate starving of certain systems and communities while elites celebrate a rhetoric of fiscal prudence.

Maintenance-as-stasis became the engine of premature death. The system survives by letting specific populations fall apart.

Moralizing the Wrong Kind of Maintenance

The most insidious development of the last forty years is not the withdrawal of maintenance—it is the moralization of maintenance-as-stasis. As public institutions hollowed out, people were encouraged to treat patching the resulting holes as a personal virtue.

We can see this everywhere:

• Teachers in crumbling buildings are praised for “going above and beyond,” as if crowdfunding air filters were a sign of devotion rather than evidence of state abandonment.

• Nurses working double shifts under dangerous ratios are celebrated for their “resilience.” Their sacrifice becomes the maintenance plan.

• Public libraries quietly become de facto warming centers, social services hubs, and crisis shelters—and we praise them for their “community spirit” instead of funding the infrastructures that would make that labor unnecessary.

• Gig workers carry the volatility of platforms designed to shed every cost possible and are told they are “entrepreneurs of themselves.”

In each case, the world is maintained not through structural repair but through extracted virtue. Institutions weaponize the language of “care,” “community,” “responsibility,” and “stewardship” to shame individuals into doing unpaid maintenance labor that keeps a decaying system upright.2

People internalize these expectations. They take pride in bailing out sinking ships. They congratulate themselves for being reliable where systems are brittle. They mistake overextension for moral character. In this way, maintenance-as-stasis becomes self-reproducing. People become the buffer that eliminates both the evidence of failure and the demand for repair.

When Maintenance Becomes Temporal Containment

The 21st century has intensified this capture. As governments, corporations, and cultural institutions lose confidence in their ability to imagine new futures, maintenance stops being a strategy for sustaining life and becomes a strategy for suppressing change.

“Resilience” means returning to a status quo that is killing people.
“Stability” means preserving institutions that no longer function.
“Preservation” becomes a way to shut down demands for redesign.
“Repair” becomes a euphemism for prolonging the present.

This is not maintenance-as-sustenance—it is maintenance-as-temporal-containment: a politics of the forever now, the same temporal logic I diagnosed in The Pyrrhic Condition, where systems perfect their own performance while hollowing out the future.

Governments speak of “weathering the crisis,” “holding firm,” “restoring normalcy.” Corporations speak of “reliability,” “continuity,” “operational excellence.” But behind this language is a refusal to redesign systems that are structurally incapable of serving the world they now govern.

Maintenance here functions as a defense of the present against the possibility of anything else.

Maintenance as Elite Pastime

Nothing illustrates the contemporary capture more cleanly than the emerging “maintenance movement,” crystallized in the forthcoming Stripe Press book Maintenance: Of Everything by Stewart Brand.

Its aesthetic is seductive: glossy photos of handcrafted tools, sailboats, mechanical clocks; the romance of tinkering; the spiritual discipline of upkeep. But its politics are disingenuous.

Brand’s Long Now philosophy has always sought to “stabilize” civilization against “short-termism.” But when stability becomes the highest value in a broken system, “long-term thinking” becomes a euphemism for infinite stasis.

Stripe Press packages maintenance not as the gritty, precarious struggle of tenants dealing with black mold or communities fighting for clean water, but as a design problem for the already-insulated. Maintenance becomes a luxury hobby, a lifestyle virtue. It aestheticizes survival while obscuring who currently can’t afford to survive.

It is no coincidence that Stripe—a financial infrastructure company—would champion such a vision. For financial capital, the only maintenance that matters is the maintenance of transactionality: uptime, reliability, seamless flows of money. They want a world that works (for commerce), not a world that cares (for people).

In their hands, maintenance becomes a philosophy of infrastructural obedience.

What the Capture Has Cost Us

Across these arcs, the pattern is unmistakable:

• Maintenance-as-sustenance keeps people capable.

• Maintenance-as-stasis keeps systems intact by exhausting people.

• Sustenance builds futures; stasis barricades them.

• Sustenance creates slack; stasis extracts it.

• Sustenance distributes load; stasis offloads it.

• Sustenance makes rupture survivable; stasis makes rupture unthinkable.

We now live in a world where institutions survive by letting people fall apart.

The Maintenance We Must Reclaim

We cannot reject maintenance. We need it more than ever. But we must choose the right one.

We must reclaim maintenance-as-sustenance:

• maintenance that restores capacity rather than consuming it

• maintenance that distributes harm rather than concentrating it

• maintenance that builds redundancy rather than demanding heroism

• maintenance that prepares the world for change rather than prevents it

• maintenance that treats people not as load-bearing components but as lives worth making room for

This kind of maintenance is not nostalgic. It is not soft. It is not slow. It is the only maintenance that allows for the world we desperately need but have not yet built.

Maintenance-as-stasis keeps civilization running in place.
Maintenance-as-sustenance keeps civilization capable of moving at all.

Only one of these can carry us forward.

That framework still explains the warehouse and the assembly line. It does not explain the feed.

It cannot account for a business model where a handful of employees oversee billions in revenue, where “users” generate value without a wage, and where markets move on the difference between one millisecond and the next.

The problem is not that the old theories were wrong; it’s that tying value strictly to labor-time misses where extraction happens now. Contemporary capitalism has stepped outside the factory walls. It no longer just organizes the workday; it reorganizes the day, full stop.

To understand that shift, we need more than a theory of labor exploitation. We need a theory of temporal capture.

Share

The Arbitrage of Duration

We usually treat time as the neutral backdrop of economic life. Wake up, commute, work, rest: the clock is just there, ticking in the background. But in the platform economy, time is no longer background. It is raw material.

You are likely familiar with Shoshana Zuboff’s concept of “surveillance capitalism”—the extraction of our data. But the target here is deeper: it is the extraction of our duration. Tech giants function less like manufacturers and more like refineries. They take unstructured human time and turn it into something that can be priced, predicted, and sold.

When you scroll a feed, you’re not “working,” but your duration is being converted into behavioral forecasts. This follows the logic of high-frequency finance, where, as sociologist Donald MacKenzie details, the game is latency arbitrage—profiting from the tiny gaps in timing between when an order is placed and when it executes.

Streaming services don’t just sell shows; they risk-manage attention. They model exactly how long you’ll stay and the precise “churn rate” of your boredom. Mobile games inject wait loops and countdown timers, then sell you the chance to skip the wait. In each case, the commodity is not just content. It is the control of when things happen—the ability to shave uncertainty off the future and package it as a product.

From Commons to Lease: Temporal Enclosure

Where industrial capitalism fenced off land, 24/7 capitalism seeks to colonize what art historian Jonathan Crary calls the “pores” of life—the intervals of rest, waiting, and sleep that once lay outside the market. These are the little gaps that used to belong to no one.

Today, if you want to move through the world, you pass through privately owned temporal infrastructure: your navigation app, your messaging platform, your social feeds, your work tools. They set:

• The Sequence: When you see information (algorithmic sorting).

• The Friction: How long basic tasks take.

• The Tempo: At which you are pinged for attention.

We are not just “users.” We are tenants in someone else’s timeline. As economist Nick Srnicek argues regarding platform capitalism, these companies operate as rentiers. We pay rent in data, in exposure to influence, in the steady drip of our minutes. The platform owns not just a product, but a slice of the present.

Just-in-Time Humanity

“Just-in-time” manufacturing was invented to cut down on idle inventory. Goods would arrive only when needed; warehouses would be as empty as possible. That idea has been extended from pallets to people.

Today, drivers, couriers, and taskers are kept hovering on the edge of use: unpaid while waiting, instantly mobilized when demand surges. The app promises customers speed and convenience, but as sociologist Sarah Sharma argues in In the Meantime, the speed of the privileged is made possible only by the waiting of the poor.

Human beings have become the buffer. The risk of slow days and dead hours is pushed entirely onto the worker.

A new chronopolitical divide appears:

1. Those who can buy temporal insulation (priority lanes, faster shipping, concierge services).

2. Those who must sell temporal availability (on-call shifts, flexible hours that are flexible only for the employer).

Time becomes a class marker: not just how much of it you have, but who controls its flow.

Burnout is a Property of Systems

Seen through this lens, the current wave of burnout stops looking like a personal failure to “manage time” and starts looking like the predictable outcome of an economy that refuses to leave any time unclaimed.

We feel this as what sociologist Hartmut Rosa calls social acceleration—the sensation that despite all our time-saving technology, we have less time than ever because the volume of tasks grows faster than our ability to complete them.

But the shift is also psychological. The boundaries between market time and human time have thinned to the point of transparency. The inbox follows you home; the chat ping follows you into bed.1

In the factory, the enemy was the foreman. In the timeline, the enemy is the internalized pressure to be optimized, leading to a burnout that is structural, not accidental.

The Timeline is the New Terrain of Struggle

Historically, as historian E.P. Thompson famously chronicled, the transition to capitalism was defined by the imposition of “time-discipline”—the replacement of natural rhythms with the clock. Today, we face a second imposition: the replacement of the clock with the feed.

The central questions are no longer only: How much are you paid?

They are also:

• Who decides the pace of your day?

• Who benefits from your waiting?

• Who gets to ignore their phone without penalty?

A theory of temporal capture asks us to widen the frame. Raising wages matters. But so does reclaiming what sociologist Judy Wajcman calls temporal sovereignty—the ability to decide when to speed up, when to slow down, and when to be unreachable.

That means fighting for limits on 24/7 availability, protections against algorithmic scheduling, and institutions that defend the right to be offline without economic collapse.

Capitalism once extracted value primarily by buying and underpaying our work hours. Now, it builds empires by quietly reorganizing the minutes around them. If we want a livable future, we cannot only fight over what happens at work.

We also have to fight over what happens with our time.