The Right To Stop: Why AI Governance Needs Intervention Rights

Walk onto any factory floor, and you'll spot it within a minute. A big red button, usually at hip height, usually a little scuffed. Nobody calls a meeting before pressing it. The operator who sees a hand too close to a press slams it, the line halts, and everyone sorts out the rest afterward.

Yet many AI systems lack this crucial safety mechanism. Plenty of firms now run AI that approves loans, flags fraud and triages claims. More and more of it acts on its own. Ask who oversees it, and hands go up. There's a committee, a risk owner and a dashboard. Then ask who can stop it this afternoon. The room goes quiet in a way that reveals more than any committee charter.

Four Rights, Ranked By Force

Intervention starts with observation. You can't stop what you can't see. But a dashboard has no hands. It tells you the model drifted at 2 a.m. It says nothing about who acts on it, or how fast. This creates what the author calls 'governance by spectating'—an excellent view of the crash.

Four rights follow, each heavier than the last. The right to question lets someone challenge the output, evidence or threshold. The right to escalate moves a concern to someone with more authority. The right to pause halts the action while people work out what's going on. The right to override replaces or reverses the decision.

These rights don't form a queue. A guardrail may pause a system before any human raises a hand. The order changes. The force doesn't. And every pause needs an exit. Someone must hold the authority to resume, with a deadline. Leave that out, and a pause either rots into paralysis or gets lifted by whoever owns the revenue line.

Implementation Challenges

Not everyone needs all four rights. An operator might pause one decision. The executive owner might override a whole process. The board might withdraw the system entirely. The stakes should determine the allocation. Two awkward questions follow: what happens when rights collide, and who answers for not stopping?

People make this harder. Whoever pauses a money-making system pays a visible personal price. But letting it run costs everyone, a little at a time. Policy writers love one sentence: 'A human may intervene at any time.' It reads beautifully. Then you ask the engineers how. Which permission? Which button? Does the agent stop cleanly, or halfway through sending 4,000 payments?

Regulatory Requirements

The rights must live in the system itself: identity controls, kill switches, thresholds, rollback and logs. The EU AI Act already expects this for high-risk systems. Article 14 says people can disregard, override or reverse an output, and interrupt the system so it halts in a safe state. Then there's the vendor. Much of AI runs on someone else's model. Unless your contract grants these rights, you may hold none of them.

How do you know any of this works? You test it. Pick one consequential AI process. Raise a challenge, escalate it, pause the system and override a decision. Time each step. Then compare the total with how fast the AI acts. If your intervention takes three days and the decision takes three seconds, you have oversight in the museum sense—everything is labelled, but nothing can be touched.

The article concludes that AI governance belongs to infinite games—played to keep the play going, not to win. The right to stop is what lets you keep playing. Factories run faster because the red button exists. People lean in because they know they can halt the line. We've spent years deciding who may approve AI. The harder question sits on the factory floor, scuffed and at hip height: who gets to press the button?