Verification Loops: Never Trust an Unrun Edit

About this workflow

Wire verification into your agent so every edit is checked by machines - syntax, tests, behavior - before it counts as done.

What happens when you run it

1. 1
   The cheapest catch-point is the moment of the edit.

   Runs flow-verification-loops-never-trust-unrun-edit-1-verify-at-the-write-boundary on Claude Sonnet 4.6
2. 2
   Syntax says it parses; only execution says it works.

   Runs flow-verification-loops-never-trust-unrun-edit-2-add-the-post-change-verify-step on Claude Sonnet 4.6
3. 3
   Done is a property of the evidence, not the prose.

   Runs flow-verification-loops-never-trust-unrun-edit-3-gate-completion-on-evidence on Claude Sonnet 4.6
4. 4
   Verification you have not tried to fool is decoration.

   Runs flow-verification-loops-never-trust-unrun-edit-4-red-team-your-own-verification on Claude Sonnet 4.6

Best for

• •Recurring tasks you currently copy-paste between tools.
• •When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
• •Fork and adapt if your inputs differ materially from the author's use case.

Models used