Use cases

Each guide takes one way an agent quietly goes wrong — a refactor that regenerates instead of moving, a “done” with no proof, a destructive overwrite — and shows the guardrail that refuses it.

How to read a guide

Every guide is the same shape:

1. The failure — the class of mistake, stated plainly. Not a toy scenario; the actual thing that goes wrong.
2. How it works — the guardrail that catches it, and which of the three natures (file-guard, gate, context) it uses.
3. The actual configuration — the real, working example shipped in this repo, shown in full. What you read is what runs.

A guide is not a spec. For the exhaustive surface — every command, event, and YAML shape — see Reference. For the why behind a mechanism, see Authoring guardrails.

All guides