Production Canary

A loop that can undo itself in 60 seconds can afford to move fast. A loop that can't, can't.

If you let an agent merge to production without a human, the question is not "will it ever ship something broken?" — it will. The question is how long broken code stays live, and who finds it. Right now the answer is usually "hours" and "your users."

A canary makes it 60 seconds and the machine.

What it does

After every merge, once the deploy lands:

1. Fetch production.
2. Assert the things a user actually needs are there — not that it returned 200.
3. If any assertion fails: git revert the merge, push, alert, halt.

That's it. scripts/canary.sh is the working version; adapt the assertions.

Assert success — do not try to recognise failure