The problem
Each of these belongs to a different department and arrives as a different emergency. Underneath, they are one missing branch.
The problem is one. The record of what an autonomous system was permitted to do, and of what it did, is made and kept by the system itself, so no one outside it can prove an action stayed within authority. It arrives as six emergencies, in six departments, and each is set out below.
These did not come from a market study. They are our working account of what an authority problem looks like from inside an organization that has one. We put them in front of operators and ask which are close and which are wide of the mark. Some always are. That is why we ask.
Each one closes with a requirement rather than a product. It states what would have to be true for the problem to be answered, whoever answers it.
Someone acted. Nobody can prove the action stayed inside the authority that was granted. The grant lives in one system, the action in another, and the two were never joined at the moment that mattered.
What would have to be trueThe decision to permit the action would have to be taken against the grant itself, recorded as it was taken, and checkable afterward by a party that was not involved in taking it.
What it meansA signed record answers the authority question — verifiable by a party independent of the action, not reconstructed after it.
An AI contributed to an action and there is no record of what it proposed, who accepted the proposal, or on whose authority it went forward. Accountability for the outcome stays with the organization regardless.
What would have to be trueIt would have to be possible to show, afterward and to an outsider, what the AI proposed, who accepted it, and on whose authority.
What it meansAI is fielded faster — accountability is answered by the architecture, not by holding capability back.
The record of the decision is held by the same system that made the decision. Reviewing it requires that party's cooperation, in that party's format, on that party's timetable. The reviewer is asked to take the actor at its word.
What would have to be trueA third party would have to be able to check the decision without the cooperation of the system that produced it.
What it meansAn inspector general, a court, or a coalition need not take the acting system’s word.
Automated systems act at speeds no human review can match. Approval queues degrade under time pressure into approval fatigue, which looks like oversight and is not. Oversight falls further behind every quarter.
What would have to be trueThe evidence would have to be produced at the speed of the decision, not assembled afterward by people.
What it meansOversight scales with the systems it governs instead of falling behind them.
Something goes wrong. Weeks are spent separating error from misuse from adversary action, and the separation is never clean, because the question of who proposed what, and on whose authority, was never recorded at the time.
What would have to be trueEvery action would have to carry a record of what proposed it, on whose authority it was permitted, and what followed.
What it meansThe investigation starts with attribution established, not spent establishing it.
Evidence for the regulator, the auditor, the inspector general or the court is assembled by hand after the fact, against a deadline, by the same people who ran the system. It is expensive, it is slow, and it is an assertion rather than a finding.
What would have to be trueThe evidence would have to be a by-product of the system running, not a project with a due date.
What it meansProduced on request, not reconstructed against a deadline.
One question
One or two is plenty, and a single line is enough. It lets us build a demonstration around your problem instead of around our example.
Start a conversationRead the argument
We are not asking you to trust us. We are asking you to let us prove it.