The Two Boundaries: Why Behavioral AI Governance Fails Structurally
This paper argues that behavioral AI governance structurally fails because it is undecidable to verify arbitrary program effects against policies (per Rice's theorem), and proposes "coterminous governance"—an architectural separation of computation from effects where governance is embedded in the execution pipeline—as the only solution to eliminate the inevitable risks and inefficiencies caused by misaligned capability and policy boundaries.
Original paper dedicated to the public domain under CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Core Problem: The "Two Boundaries" Mismatch
Imagine you have a very powerful robot that can do almost anything: send emails, move money, or change database records. To keep it safe, you put up a fence (governance) to tell it what it is allowed to do.
The paper argues that in almost every AI system built today, there are two different fences that don't match up:
- The Capability Fence (What the robot can do): This is determined by the robot's tools and code. If the robot has a tool to send emails, it can send emails.
- The Rule Fence (What the robot is allowed to do): This is determined by the safety rules and filters you wrote.
The Problem: These two fences are almost never the same size or shape.
- The "Risk Zone" (Ungoverned Capability): Sometimes the robot has a tool it can use, but your rules didn't cover that specific tool. It's like the robot has a secret back door that your security guard doesn't know about. The robot slips through, and bad things happen.
- The "Theater Zone" (Governance Theater): Sometimes your rules are very strict about things the robot cannot do. It's like having a security guard checking for "flying" when the robot has no wings. You are wasting energy policing things that aren't possible, while the real dangers (the back doors) remain open.
The paper says that trying to fix this by adding more guards or more rules just makes the "Theater" bigger and the "Risk" slightly smaller, but it never fixes the gap.
Why You Can't Just "Watch" the Robot (The Math Problem)
You might think, "Why don't we just build a super-smart monitor that watches the robot and stops it if it does something bad?"
The paper uses a famous math rule called Rice's Theorem to explain why this is impossible for smart, flexible AI.
- The Analogy: Imagine you are trying to predict the ending of a movie just by looking at the script. If the movie is short and simple, you can guess the ending. But if the movie is an infinite, complex story that changes based on the audience, no algorithm can predict the ending with 100% certainty before the movie plays.
- The Result: Because AI is so flexible (it can write its own code and combine tools in new ways), you cannot mathematically prove in advance that a specific action will be safe. You can only guess. And because you can only guess, there will always be a chance the robot does something bad that your monitor didn't see.
The Solution: The "Order Taker" vs. The "Chef"
The paper proposes a structural fix. Instead of trying to watch the robot and stop it from doing bad things, you change how the robot is built.
The Old Way (Behavioral Governance):
The robot is a Chef who has direct access to the stove, the knives, and the gas. You stand next to them with a clipboard, yelling "Stop!" if they reach for the wrong ingredient.
- Flaw: The Chef might grab the gas before you can yell, or they might find a new way to cook that you didn't write down on your clipboard.
The New Way (Structural Governance / Coterminous Governance):
You separate the Chef from the Kitchen.
- The Chef (Computation): The AI is only allowed to think and write down a recipe (a "directive"). It cannot touch the stove, the knives, or the gas. It has no physical hands.
- The Order Taker (Governance Boundary): A separate, strict system receives the recipe. It checks: "Does this recipe have the right ingredients? Is it safe?"
- If yes, the Order Taker goes into the kitchen and cooks the meal.
- If no, the Order Taker throws the recipe away.
Why this works:
- The AI cannot do anything bad because it literally doesn't have the tools to touch the world.
- Every single action must go through the Order Taker.
- There is no "Risk Zone" because the AI has no secret back doors.
- There is no "Theater Zone" because the Order Taker only checks recipes that can actually be cooked.
Why "Monitoring" Isn't Enough
The paper also explains why simply "logging" or "recording" what the AI does doesn't count as governance.
- The Analogy: Imagine a security camera in a bank. If the camera sees a robber, it records the crime. But the camera didn't stop the robbery.
- The Math: If a camera catches 99% of robberies, that sounds great. But if the bank has 1,000 transactions a day, the chance that at least one robbery slips through the 1% gap is nearly 100%.
- The Point: You need to stop the action before it happens, not just record it after.
The Bottom Line
The paper concludes that to truly govern AI, you cannot just add more filters or rules on top of existing systems. You have to rebuild the system so that the AI can only ask for things, and a separate, strict gatekeeper decides if those things happen.
- If the boundaries match: The AI is safe by design (Structural Governance).
- If the boundaries don't match: You will always have some risk and some wasted effort, no matter how many rules you add (Behavioral Governance).
The authors have proven this mathematically using computer code (Coq) to show that this "Order Taker" approach is the only way to guarantee that every action is governed.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.