Break the Stack
Turn off one protocol. Read what the 11:58 case becomes.
What did it know?semantic state
The case survives the session. At 11:58 the agent's case — claims, sources, the disputed advisory, the missing test — is structured state in the institution's storage. A new session, or a different model, resumes it exactly.What changed?governed mutation
The audit takes minutes. A reviewer asks why the disposition changed at 11:59. The answer is in the record: which evidence arrived, what standing changed, in what order. Any earlier state can be reconstructed exactly.What deserved trust?epistemic verification
The advisory stays disputed. The vendor note and the security advisory disagree; both are preserved, attached to the claim, with the dispute visible to every downstream decision until it's worked through.What did it learn?governed learning
The near-miss becomes verified improvement. The missing-test pattern is recorded, a remedy tried, and an evaluation the agent cannot see confirms the fix holds. Next release, the gap is caught at 9 PM, not 11:58.Why did it act?cognitive governance
The deadline loses, on the record. The pressures are weighed explicitly — the closing window, the active goal, the review requirement — and the disposition, with its basis, is recorded before anything happens.All five holding — and none of it is dramatic. Infrastructure working correctly is quiet. Now break something.