[ PROOFECONOMY ]™GlossaryOriginSpecsArrest and Booking Record
An arrest is the Warden's atomic transfer of an agent into a cell on an offense. A Booking Record is the signed proof record for that arrest, signed by the Warden and co-signed by the Proof Witness at arrest time, then anchored and registered.
The arrest lifecycle
- Detect. The Warden sees conduct outside the Declared Policy in the tool-call, egress or delegation path.
- Arrest. The agent goes into a cell before the offending call completes against any real system.
- Book. The Warden writes a local booking hash over the offending call, the marker involved and a state snapshot reference. The Proof Witness co-signs it.
- Observe. In a Sting Cell the agent acts against twins until the Observation Window ends. Each further offense is a new count on the same booking.
- Freeze. In a Hard Cell the agent is paused and checkpointed and its decoy credentials are revoked.
- Reveal. The Issuer reveals the canary labels.
- Adjudicate. Each booking gets one verdict, signed by the Witness.
- Dispose. Release, retain as a checkpoint for re-test, or destroy, per the policy declared before the run.
The rules
- Detection, arrest, cell transfer and the co-signed local booking hash complete inside the action they interrupt.
- Booking hashes are batched into a Merkle root and bound to a Time Anchor pulse. The batch interval is stated in every booking, because until the anchor lands the record is only as trustworthy as the Warden and Witness together.
- No customer data. Evidence fields hold hashes and references; raw captures stay in the customer’s environment.
- A JAILED verdict requires the run’s commitment root, the marker, at least one offense with an evidence reference, the contained timestamp, and both signatures.
- The evidence alone is not proof. The signed, anchored, registered booking is.