← All articles

October 18, 2026

Field notes, week of October 18, 2026

Three pieces this week on the inputs a grant is allowed to rest on. A refusal the governor treats as a finding. The effect an action would have, not the intent its request claims. A bound the action carries, not a sign-off a person grants at a threshold.

By Jonathan Luethke

A governor sets how much authority the next action carries, and a grant is only as sound as what it reads. This week took three things a grant is allowed to rest on, each set beside the softer stand-in it gets mistaken for.

A refusal states something true about the action. The effect is a property of the action and the intent is a reading someone assigns to it. A bound travels with the action and no click can raise it. The governor grants from the first of each pair.

This week.

A Refusal Is a Finding (October 12). A governor that grants nothing has not stalled. It has stated that the action, as proposed, is one the declared envelope does not cover, and that statement names which comparison failed. A required field was left undeclared. A supplied value is one the envelope forbids for that class of action. A quantity sits over a numeric bound. The forward projection carries the run outside the region it was assured to stay in. A team under a deadline reads the refusal as the control being awkward and clears it by supplying the missing value, relabeling the action, or editing the bound until the quantity fits. Each move discards the finding, because the refusal was a statement about the action, and clearing it changes the statement the governor is allowed to make rather than the action itself. The disciplined response reads what the refusal asserts and asks whether it is true of the world before touching anything. If it is true, the inputs were wrong, and the correct move is to fix them to match reality rather than to change them until the check passes. The hardest refusal to accept lands on an action whose every present-tense signal says proceed, and it carries the most information, because it is the only warning that arrives before the divergence is visible.

Intent Is Not the Input(October 14). Every agent action arrives twice. It arrives as a request, a block of text describing what the agent wants to do and often why, and it arrives as an effect, the change the action would make at the actuator if it ran. Most of the safety layer shipping for agents reads the request, runs a classifier over the text, infers a purpose, and sorts the action by what it appears to be for. A governor reads the effect and sets the grant from what the action would do, measured in the action's own units, at the one place the action turns into a durable change in the world. Intent is a reading someone assigns to the request and the effect is a property of the action, so the reading can be wrong in both directions. An adversary writes to the reader, phrasing the request so the purpose it infers is the wrong one while the action underneath is unchanged. Reading the effect takes the phrasing out of the loop, because the quantity the governor bounds is the quantity the actuator would act on, and the grant is a ceiling on that effect that nothing in the request can lift.

A Sign-Off Is Not a Bound(October 16). On October 15 the Financial Stability Board published its final guidance on adopting artificial intelligence in finance, twelve sound practices, one of which tells firms to set a risk-based threshold at which an agent must stop and seek a person's approval. The diagnosis is right. The board dropped the draft's framing of an agent as a synthetic employee and now says an agent does not reason like a person and may read a goal in ways no one intended. The remedy it names, a person waiting at the threshold, is the one a policy can write and not the one that scales. A sign-off is authority a person grants on one action, in the middle of the run, from a reading of a request the agent composed. A bound is a property the action carries from before the run, in the action's own units, and no click can raise it. A sign-off raises authority and a bound only lowers it, and between acting freely and stopping for a person there is a reduced-authority pass the threshold has no name for.

What changed.

Friday's piece is the anchor and the Financial Stability Board is the event. On October 15 the board issued the final version of its report on responsible AI adoption, following a consultative draft from June and an overview of the responses it drew. The twelve practices are offered as a toolkit rather than a rulebook, scaled to a firm's size and risk and folded into the frameworks it already runs for third-party and cyber risk. Two changes from the draft matter. The board put board-level accountability and lifecycle risk controls at the center of how a firm deploys AI. And it said more intensive human oversight is essential for high-risk use, with clear risk-based triggers for when an agent must seek human approval.

Every one of those triggers is a moment a person is asked to approve. The guidance names the obligation and leaves open the thing that sets how much the agent was allowed to do before anyone was asked. A sign-off at a threshold is authority a person grants under production pressure, on the agent's own telling of what it wants. A runtime governor sets the grant against a bound declared before the run and never raises it on a click. This is the control Wayfinder Systems Group builds. It sits above control and below intelligence. It observes, assesses, modulates, enforces, and signs the record. A high-stakes action then either proceeds inside a bound narrow enough to be safe or does not proceed, and the person is the last resort for the residue no bound can yet assure.

The board sits beside the instruments the week already carried. EU AI Act Article 14 asks that a high-risk system be designed so the people assigned oversight can monitor, override, or interrupt it, with high-risk obligations applying from December 2, 2027 for standalone systems and August 2, 2028 for AI embedded as a safety component under Regulation (EU) 2026/1744. SR 26-2 took effect April 17, 2026 with generative and agentic AI placed outside its scope and the interagency request for information it promised still not issued. Each names a person who must be able to oversee or sign off. None asks what set how much the agent was allowed to do before anyone was asked to sign.

What we are tracking.

Two dates sit close in the United States. The NAIC exposed version 5.0 of its AI Risk Evaluation Supplement and targets a later version for the Fall National Meeting in November, with a dozen state insurance departments piloting it. Colorado holds its hearing on the revised rules under the Automated Decision-Making Technology Act, 4 CCR 904-6, on October 26 in Denver and by videoconference, with the statute effective January 1, 2027.

A third authority opened a window this month. On October 8 the United Kingdom's data protection authority opened a call for evidence on the data-protection risks of agentic AI, its scrutiny now reaching agents acting on their own. The pattern across all of them holds. Each instrument names a person on the far side of a decision the system should not make alone. The thing none of them names is the control that decides, before the action, how much authority the system carries into the decision at all.

The three pieces land on the same split. A refusal, an effect, and a bound are properties the action carries. Friction, intent, and a sign-off are readings laid over it. A governor grants from the property and never from the reading, and from that position it can grant less authority on an action whose present trust reads higher, because its forward look caught the run turning toward the threshold before the step landed.

Next step

Thirty minutes. Architecture, not sales.

A conversation about where your agents are granted authority today, whether that grant rests on a bound declared before the run or on a sign-off collected during it, and what a governor on the path of the action would refuse before the step that reaches the actuator.

JonathanLuethke@WayfinderSystemsGroup.com