loop-contract
Design a loop before running one - name its trigger, verification, two stop conditions, terminal states, and the weakest mechanism that holds it. Use when designing or reviewing unattended or repeating agent work - a schedule, a cron/routine, "keep going until X", a babysitting loop. Not for a fixed sequence of known steps (write a script instead) or a single task that just runs long - repetition, not duration, is the trigger.
Pinned to revision 882a707e51d5, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.