Agents you can let run
What they did is visible afterwards, and the irreversible parts are gated.
File 07 · converge
Receipts, not promises.
An agent saying “I followed the rules” proves nothing.
Compliance you can trust comes from structure, not instruction. Separate the maker from the checker, and make every check leave something you can look at.
FIG 02 // TWO ROOMSSCROLL // RUN THE CHECK
01 · The promise
An agent saying “I followed the rules” proves nothing. That's performative compliance.
02 · Structure, not instruction
Compliance you can trust comes from structure: what the agent can see, what it's allowed to do, what it must produce, and which contexts are kept apart.
03 · Two rooms
Separate maker and checker. Only the work crosses the wall. The checker stays blind to the maker's reasoning.
04 · Every check leaves something
Not a claim that it was checked: the check itself, something you can look at, on file.
05 · “Nothing found” is allowed
Always allow “nothing found.” A clean result goes on file the same as a kill.
06 · High stakes
On anything high-stakes, the checker comes from a different model family. Same family, same blind spots: the check passes what it should catch.
Above a stakes threshold
The maker never grades its own work.
Move the stakes:
CHEAP AND REVERSIBLE.A full outside check can cost more than the mistake would.
Before the act
Detection isn't prevention.
A perfect receipt can document a leak after it happened. Irreversible actions get a gate before the act, not just a receipt after it.
Can the act be undone?
CAUGHT AFTER, IT CAN STILL BE WALKED BACK.The receipt after the act does the job.
Honest numbers
No denominator, no number.
A probability needs a reference class, a settle condition and an evidence tier, or it's decoration.
Evidence quality caps how sure you may be.
Evidence tier
NO DENOMINATOR, NO NUMBER.Without its three parts, a probability is decoration.
What it allows
Work you can let run, and others can check.
FILE 07 · RECEIPTS, NOT PROMISES
ANNEX A · LIMITSWHERE IT BREAKS
ANNEX A · LIMITSWHERE IT BREAKS
- Detection isn't prevention. A perfect receipt can document a leak after it happened. Where an act can't be undone, the control has to come first: permissions, a sandbox, an approval gate. The less reversible the act, the more control moves before it.
- Same lineage, same blind spots. When the checker shares the maker's lineage, the blind spots match and the check passes what it should catch.
- Receipts turn into theater: boxes ticked with artifacts nobody reads.
- Over-applied to cheap, reversible work, where checking costs more than the mistake would.
- It audits; it doesn't steer. It keeps an honest operator honest and catches drift. It doesn't stop someone who wants to cheat.
- No reference class. A genuinely novel one-off has none. An honest number says so rather than invent one.
Next file08 · Translate
OTHR · RECEIPTS, NOT PROMISESREV // 73c45b39 · BUILT // 2026.10.11NO CAPTURE · NO CTA