Vision
Vision
Nothing Is Ever Done
Finance built explicit machinery for the gap between "trade done" and "matter settled": named actors, deadlines, records, a whole clearing process. The cost of leaving that gap unmanaged was obvious enough that nobody argued about it. Agent systems are now creating organizational commitments — sent messages, changed configurations, triggered workflows — faster than most organizations can build rules for when those outcomes get revisited. Which makes production readiness look less like a success rate and more like a question of whether you can govern what happens after an agent succeeds.
Nothing Is Ever Done
Finance built explicit machinery for the gap between "trade done" and "matter settled": named actors, deadlines, records, a whole clearing process. The cost of leaving that gap unmanaged was obvious enough that nobody argued about it. Agent systems are now creating organizational commitments — sent messages, changed configurations, triggered workflows — faster than most organizations can build rules for when those outcomes get revisited. Which makes production readiness look less like a success rate and more like a question of whether you can govern what happens after an agent succeeds.
Domain and Design
The Right to Reopen
Chargebacks, malpractice claims, insurance reopenings: every industry has formal machinery for unwinding a commitment after it's been made. That machinery works. It was also built for a world where reopening is the exception. When automated agents produce thousands of commitments an hour, the exception stops being exceptional — and the structures don't break so much as stop keeping up.
The Hold
Every organization has commitments sitting in a state that doesn't officially exist: not accepted, not rejected, just stuck. At low volume, a person remembers to follow up. At agent volume, that workaround stops working. The fix is formalizing what organizations already do badly — a state where consequences are frozen, the uncertainty is written down, and someone owns the clock.
Hidden Authorship
An agent drafts a purchase order, a client letter, a regulatory filing. The interface presents a summary and a button: Approve. One click, and the system records the reviewer as author: the person who verified the facts, confirmed policy compliance, exercised authority to commit, and accepted liability for the outcome.
Those are four distinct institutional functions. In most organizations they belong to different roles: the person who checks accuracy is not the person with signing authority, and neither necessarily bears the loss. COSO's 2026 guidance on agentic systems identifies this directly. Approving an AI-generated outcome without independently reperforming the underlying work looks like oversight but functions as delegation.
The interface compounds the problem through a basic asymmetry: approval takes one click; refusal demands justification. As agent output scales, reviewers keep clicking, systems keep logging consent, and the institutional work those clicks are supposed to represent quietly goes unperformed.
Further Reading
