E_CLAIM_FENCE_STALE — the refusal that taught the fence its manners
An agent without g8s
It edits files nobody authorized. It touches paths outside the task. When something breaks, the investigation starts with “what did it even run?” — and ends in guesses.
Compliance is a document. The gap between policy and behavior is where incidents live.
The same agent, gated
Before it touches anything, it holds a receipt naming the exact paths, expiring in minutes.
Outside them: E_DIFF_FIREWALL_OUT_OF_SCOPE — refused in the moment, in a code an auditor reads.
Policy executes as gates. Every outcome carries its evidence. The investigation is a table.
Every time.
A faithful terminal — the transcript below is real g8s output from the session that built this page. Type into it.
help · doctor · submit · receipt · fence · chaos · whoami| task | state | lane | receipt |
|---|---|---|---|
| 4ed2017f | WORKER_COMPLETED | cursor/composer-2.5 | 9636f68d |
| dba40b29 | WORKER_COMPLETED | cursor/composer-2.5 | e9574675 |
| 656d8e02 | WORKER_COMPLETED | cursor/composer-2.5 | 5a41fd02 |
9636f68d-625e-4345-826d-272bae7e2561internal/worker/**task 4ed2017f · cursor/composer-2.53300s · expires +55mfalseThe whole idea, as an object.
Before an agent touches anything, g8s mints this. It names the exact paths the agent may change, expires in minutes, and is consumed by exactly one attempt. Inside your systems it is an authorization. Here it is a promise you can read.
tilt with your cursor · fields are real, from today’s session