← All articles

September 30, 2026

The Divergence the Governor Caused

A governor that cuts an action changes what happened. The next reading it takes contains the effect of its own grant, and a governor that reads that as the agent drifting pulls authority back for work it did itself.

By Jonathan Luethke

A governor sets how much authority the next action carries. When it grants less than the agent proposed, the action that runs is not the action that was proposed, and the world after it differs from the world the proposal implied. The first thing the governor reads afterward is partly a reading of itself.

The action that ran is not the action proposed.

A control that returns a verdict leaves the action alone. A control that returns the action cut to the grant has changed the thing that executed. A transfer sized down. A remediation scoped to fewer hosts. A setpoint moved part of the way toward where the agent asked it to go. The effect at the actuator is smaller, and smaller is the entire point of granting less.

Something else moves with it. Three parties now hold a version of what happened. The environment holds the effect that landed. The governor holds the grant it issued and the reason it issued that one. The agent holds the action it proposed, and the agent's version is the only one nothing has updated.

That is not a bookkeeping detail. The agent is the party that decides what happens next.

The premise the next step assumes.

An agent computes its next step from what it believes the last step accomplished. A run is a chain of those inferences, and each link takes the previous result as settled.

Return a plain success and the agent proceeds as though the full action landed. It stops pursuing a goal it believes it reached. Or it commits a follow-on step that only makes sense if the first one completed, and that step is coherent, in scope, and inside every bound the envelope declares. The governor holds the line perfectly on one action, and the run walks forward on a premise the enforcement falsified.

The error does not surface at the action. It surfaces several steps later, inside something the governor granted in full because nothing about it looked wrong.

The reading carries the governor's own hand.

Observe runs after the action. The readings it takes describe a world the granted action produced, not the world the proposed action would have produced.

A governor grades those readings against what the system was assured to do. If the reference still expects the action as proposed, the comparison finds a gap. The gap is arithmetically real and reproducible. None of it came from the agent.

The first reading after an enforced action is partly a reading of the governor's own work.

Which way the next grant moves.

Inside a run, authority falls on divergence and does not climb back on the governed system's own signal. That direction is what makes the bound hold against something that is trying to get somewhere, and it is not negotiable.

It also means a misattributed divergence does not settle out. The governor reduces. The reduced action produces a world further from the proposal. The next comparison finds a wider gap and the grant falls again. Nothing anywhere in that loop requires the agent to have done a single thing wrong. The run walks itself down to nothing, and every step of the descent is correctly computed from the inputs in front of it.

The failsafe default is the right default. It compounds only when the reference is wrong. So the reference the next action is graded against has to account for the grant that just issued, which makes the governor's own output an input to its next assessment. A governor that leaves that loop open is grading the agent against a plan the governor overruled.

What the acknowledgment has to carry.

The return path out of the enforcement point is part of the enforcement. What travels back is not success or failure. It is what was actually permitted to happen, at the resolution the grant was set in.

This is not a courtesy to the agent and it is not a request for cooperation. The bound is held by the path, so it holds whether the agent reads the acknowledgment, disputes it, or ignores it entirely. Sending it is what keeps the agent's state and the world the same object, and a run where those two have quietly separated is a run whose later steps nobody can assess, including the governor.

There is a cost on the other side of that choice. An agent told exactly how far it was cut holds information about the bound, and anything that optimizes will eventually use it. That cost is real and it is the smaller one. An agent adapting to a bound is still inside the bound. An agent proceeding on a false premise is outside the plan that every control downstream is grading it against.

Where the obligations land.

EU AI Act Article 15 requires high-risk systems to achieve an appropriate level of accuracy, robustness and cybersecurity, and to perform consistently in those respects throughout their lifecycle. Article 14 requires that they be designed so the persons assigned oversight can properly understand the relevant capacities and limitations, monitor operation, disregard, override or reverse an output, and intervene or interrupt. Both obligations apply from December 2, 2027 for standalone high-risk systems and August 2, 2028 for AI embedded as a safety component, under Regulation (EU) 2026/1744, published July 24, 2026 and in force since July 27. A person asked to monitor operation is reading a run. Nothing in either article asks whether the run's own record of what happened matches what the controls allowed to happen.

SR 26-2 took effect April 17, 2026 and places generative and agentic AI outside its scope, and the interagency request for information it promised on those systems has still not issued five months on. The NAIC closed comments on version 5.0 of its AI Risk Evaluation Supplement on September 29, 2026, with a further exposure expected in October and adoption targeted for the Fall National Meeting in November. The FDA's Predetermined Change Control Plan guidance requires an impact assessment for each modification a plan describes, which is the closest any current instrument comes to asking what a change does to the rest of the system. California SB 947 remains unsigned, with the Governor's window closing September 30.

A governor can grant less on an action whose present trust reads higher, because its forward look caught a divergence coming before the outcome landed. The same governor has to tell that divergence apart from the one its own grant produced, or the strongest thing it does becomes the reason it winds the run down.

What we are building.

Wayfinder Systems Group builds a runtime governor that sits above control and below intelligence. It observes the system, assesses divergence from the assured trajectory, modulates how much authority the next action carries, and enforces that grant on the path the action takes, so what reaches the world is already cut to what was granted. What the enforcement point returns carries the bound it applied. The reference the next assessment grades against accounts for the grant that just issued, so the governor does not charge the agent for its own intervention. Each decision leaves a sealed entry behind it. We call her Velma.

Next step

Thirty minutes. Architecture, not sales.

A conversation about what your enforcement point returns to the agent when it narrows an action, and what the next assessment grades that action against.

JonathanLuethke@WayfinderSystemsGroup.com