Nobody argued, nobody filed The policy stands, unread, unbent They simply stopped requiring it And nobody told the department
The arc has been at altitude. States, laboratories, silicon, registers. Today it comes down to a desk, because the same mechanism is running in every organization this newsletter has readers inside, and there it has a name that makes it sound like a discipline problem.
Shadow AI. The unapproved account, the pasted context, the model consulted at home and the answer walked back in as one's own judgment. Security calls it a risk, compliance calls it a violation, and both are right about what it is while being wrong about what it means.
The thing it actually is
An employee who routes around a permission policy may well have failed to comply. Compliance failure is also the least informative description available, since it names the rule that was broken and explains nothing about why. They have exercised exit from a system that never offered them voice.
Ask the obvious question and the framing collapses. When the approved tool could not see the document that mattered, could not remember last week, could not reach the system where the work lives, what was the procedure for saying so? There is usually a channel. There is almost never a decision at the end of it, and the people who have tried once do not try twice. The policy was written by parties with a specific risk to reduce, and revising it requires an owner willing to defend a judgment about acceptable reach, which is the scarcest thing in any institution.
So nobody argues. They stop needing the policy, which is cheaper, faster, and produces no meeting.
This is the enterprise edition of the whole week. Voice was theoretically available and practically inert. Exit required only that an alternative existed, and by 2026 the alternative is a browser tab. The permission architecture lost an argument that was never held.
What the institution stops being able to see
Two things are true here and the arc needs both. Work leaving the building through an unsanctioned tab is a real breach, of data protection duties, of client confidentiality, sometimes of law, and it does not stop being one because it is also informative. The compliance officer is not the villain of this episode.
The reflex response is still enforcement alone, and enforcement alone converts a diagnostic into a secret.
Every unofficial bridge is evidence. It marks the precise coordinates where the permission surface stopped matching the work, generated by the person best placed to know. An organization that could read that map would learn more about its own operating design in a fortnight than a governance review produces in a year. An organization that punishes it learns nothing and keeps the same gap, now invisible.
The measurement problem from What Voice Costs returns here in its enterprise form. Adoption metrics count seats issued and prompts run inside the sanctioned tool. The work that left never appears. So the dashboard can improve steadily throughout the period in which the organization's actual thinking migrates to systems it cannot see, and the improvement will be reported as progress, because the only thing being measured is the part that stayed.
Somewhere in that gap sits a compliance officer who is genuinely correct that data is leaving the building, and who has been handed a problem created three floors up by people who never had to defend a decision about reach.
Who gets to leave
Now the part that makes this a distributional question rather than a productivity one, because the exit inventory applies inside a company exactly as it does between countries.
Look at who can actually route around a policy. It requires knowing that alternatives exist, which is a technical-confidence question. It requires a personal budget, or the willingness to spend one. It requires enough standing to survive being caught, which is a seniority question and a permanent-contract question. And it requires the risk appetite of somebody who believes an awkward conversation is the worst plausible outcome.
Run those filters over any organization and the same population emerges. Senior, technical, secure, and already influential. The workaround reproduces the hierarchy it evades. The people whose judgment the institution most needs to improve, and who have the least room to advocate for themselves, are precisely the ones who keep using the crippled tool and absorbing its gaps by hand.
That is the thirteenth floor again, at the scale of a floor plan, and nobody drew it on purpose.
The invisible labor
Which brings the week back to the person the canon keeps returning to.
Whatever the system was not permitted to do, somebody does. The context it cannot retain is carried in by hand, every time, by the same person. The claims it cannot investigate get verified by someone with a browser and no allocated hours. The information it cannot reach between two systems is moved across by a human being performing an integration the institution declined to build.
Then the productivity assessment arrives and books the human repair work as model output, the verification time as zero, and the errors caught by expertise as evidence that the control worked.
This is the liability sponge with an extra job. Absorbing the blame was the original description. Absorbing the missing capability is the newer one, and calling it initiative does not pay for it.
The handoff
So the frontier question and the desk question turn out to be one question asked at two altitudes. Who is allowed to act, who decides, what happens to the people the decision was not designed around, and where they go when the answer is nothing.
Next week the arc that follows this one takes the enterprise seriously on its own terms, and asks whether an institution can build accountable control without disabling the capacity it exists to govern. It has a harder job than it looked like having earlier in the arc, because it now has to explain why an organization that can only prohibit has already made its decision. The decision is simply being executed elsewhere, by whoever was senior enough to take the chance, and without a record.
Tomorrow the arc has to decide what it is actually recommending.
They did not contest the policy. They stopped needing it.
Companions
- The person in the loop without the levers: The Liability Sponge and The Liability Sponge at the Switch.
- The measurement blindness: Dashboard Goodhart.
- The distributional question inside one firm: The Thirteenth Floor.
These notes come out of Sociable Systems, a practice that reads AI-shaped documents the way a hostile reviewer will, before a lender or a court finds the gap. The argument has an operational form: the Interim Protocol sets out four rules for AI use in environmental and social deliverables, covering disclosure at touch-point grain, evidence custody, the phrases no automated screening may settle, and a hostile read before anything ships. Free, and written to be cited or retired once institutional guidance arrives.