AI writes code faster than you can read it. If you aren't checking every change, regressions stack quietly until something visible breaks and you can't trace it back. This module makes verification a habit you run after every prompt cycle.
Key idea
If you did not prove it, you did not ship it. Typecheck, build, and git proof after every change.
This module includes
Time: about 2 hours of focused work
You finish with: a proof log template, a regression checklist, and a tested governor block config
Start by adding verification steps to one of your existing execution prompts and seeing the difference
Every change goes through the proof loop before it ships.
Outcome
You can prove each change is correct. Not hope. Prove.
Deliverable
A proof log template you use on every commit, a regression checklist, and a tested governor block config.
Lessons
·The non-negotiable sequence: typecheck, lint, build, then commit
·Baking verification steps directly into your AI prompts
·Why regression checks after every single change are worth the time
·TypeScript strict mode and what it actually catches for you
·Build-time errors you can fix now vs. runtime errors you find in production
·Proof artifacts: what to log, what to screenshot, what to git-output
·Governor blocks that stop agents from touching files outside scope
·Using the HANDOFF packet as hard proof of completion
·Smoke-testing critical routes after every deploy
·Automated checks vs. manual review and where each earns its keep
·The discipline of verifying after every prompt, not just at the end
·Recognising when to throw away AI output and rewrite the spec
·Building a regression checklist that fits your project, not a template
·Trust the log. The log doesn’t have feelings.
Exercises
·Take an execution prompt you’ve already used. Add verification requirements. Run it again and compare.
·Write a regression checklist for your project. Use it on three commits in a row. Adjust what doesn’t fit.
·Set a governor block limiting an agent to two files. Give it a task that tempts it to go wider. See what happens.
What good looks like
Verification is a habit, not a final step. Run it after every prompt, not just at the end.
Three consecutive commits with clean proof logs.
Proof Checklist
Proof
☐Proof log template committed and used on 3+ real changes
☐Governor block tested and confirmed it restricted scope as intended
☐npm run build exits clean
☐git show --stat HEAD shows only the files you planned to change
☐git show --name-only HEAD matches your declared targets