← Latest papers
🤖 AI

One Gate Is Not Enough: Composing Stateful Pre-Action Controls for Agentic AI

This paper formalizes the challenges of remediation-induced control coupling in multi-gate Agentic AI systems, proposing a "remediate-and-regate" protocol to restore soundness while demonstrating that remediation order is semantically critical and that current mitigations cannot fully eliminate state-level poisoning risks.

Original authors: Gaston Besanson

Published 2026-08-20
📖 5 min read🧠 Deep dive

Original authors: Gaston Besanson

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.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

In the emerging world of artificial intelligence, autonomous agents are being tasked with making decisions that have real-world consequences, from ordering supplies to managing energy grids. These agents do not operate in a vacuum; they must navigate a complex landscape of rules. Before an agent acts, it must pass through a series of digital checkpoints, or "gates," that ask three fundamental questions: Is the agent allowed to do this? Can the organization afford it? And is the evidence supporting the decision valid? For years, researchers have treated these questions as separate hurdles, checking each one independently before giving the green light. However, as these systems grow more sophisticated, a critical flaw has emerged: the act of fixing a problem in one area can inadvertently break the rules in another. If an agent changes its plan to stay within budget, that new plan might suddenly violate a permission rule it previously passed. The core challenge is no longer just about having multiple gates, but about understanding how the gates interact when one of them changes the very thing the others are measuring.

This paper tackles that specific, tangled problem by studying what happens when an AI agent's decision is altered by one control system and then re-evaluated by another. The researchers built a working demonstration using three distinct engines that handle permissions, financial budgets, and evidence validity. They discovered that if you simply run these checks once, in parallel, on the original plan, the system can be dangerously wrong. An agent might be approved for an action based on a corrupted piece of data, only to have that data corrected by a second gate. By the time the action is executed, the original approval is no longer valid because the underlying numbers have changed. The study proves that a single pass of checks is insufficient and can lead to actions that violate safety rules or exceed budgets, even though the system thought it was being careful.

To solve this, the author developed a "fix-and-recheck" protocol. Instead of just saying "yes" or "no" once, the system allows a gate to correct a flaw—such as swapping a bad data point for a verified one or reducing an order size to fit a budget—and then forces every single gate to re-evaluate the new, corrected plan. This ensures that the final decision is based on the actual action that will be performed, not the flawed version that was proposed. The researchers tested this method across thirty different simulated scenarios and found it to be sound, meaning that every action that was executed passed all the rules at the moment of execution. They also showed that this approach does not create false safety; if a specific type of error is not covered by any of the individual gates, the combined system will not magically detect it. It remains honest about what it can and cannot see.

A surprising and significant finding emerged when the researchers introduced a second type of correction. In their system, one gate could fix data errors, while another could scale down an order to save money. They tested whether the order in which these fixes were applied mattered. The answer was a definitive yes. Applying the data fix first and then the budget fix produced a different result than doing them in reverse. This means that the sequence of operations is not just a technical detail of how the software is written; it is a fundamental part of the governance policy itself. If the order is wrong, the system could silently approve an action that is actually over budget or unauthorized. The researchers used a rigorous computer checker to find dozens of specific examples where the order changed the outcome, proving that these systems cannot be left to run in any random sequence.

The study also uncovered a subtle risk regarding how the system remembers past decisions. When a corrected piece of evidence is accepted and stored for future use, it enters a trusted buffer. The researchers demonstrated that if a flawed piece of data slips through the initial checks and gets stored, it can poison future decisions. The system might trust this corrupted data later because it came from its own "trusted" memory. To address this, they tested two mitigation strategies: a "quarantine" period where new data must be consistent over several checks before being trusted, and a method of averaging multiple data points. In their simulations, these strategies significantly reduced the number of poisoned decisions, though they did not eliminate the risk entirely, particularly in scenarios with very few data points.

Ultimately, this work provides a clear blueprint for how to safely compose multiple AI governance controls. It moves beyond the idea of simply stacking rules on top of each other and instead establishes a dynamic process where corrections trigger re-evaluations. The researchers are careful to note that their findings are based on a specific, controlled demonstration and do not claim to solve every possible problem in AI governance. They do not assert that their system is perfect for all real-world deployments, nor do they claim to have solved the problem of infinite loops or complex, multi-agent interactions. However, for the specific setting they studied, they have proven that a single pass of checks is unsafe, that the order of fixes matters, and that a disciplined process of re-checking after every change is the only way to ensure that an agent's final action is truly compliant with all its governing rules.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →