Can you design a loop that always stops, never makes a failure worse, and sets bad inputs aside safely?
- Capstone
- 05/05
- To read
- ~6 min
One team had three loop incidents in six months: a retry storm, a repair agent that never stopped, and a validation loop that left thousands of items stuck. What do you think the three had in common?
In the module you make your guess first, then read what happened and why.
The four loop invariants
Loop Specification Document: required sections
Loop testing is adversarial by default
Capstone deliverable: the Loop Spec Document
Your complete loop spec
A spec for your own app, as a text file you download. The module also gives you the prompt for Claude Code, Codex or Antigravity, a checklist to check what it built, and recommended skills.
- Observability