done in about 4 minutes · one log line per action ✓
Loop B · the improver
pass 14 · rewording summaries
pass 15 · rewording what pass 14 reworded
pass 16 · reorganizing an index that was fine
cost climbing · scheduled to run again next monday
turn 20 · the cap ends the run ✓
Scorecard · the two runs, side by side
Loop A · filingLoop B · improver
passes316 and climbingstopped at 20
work finished?yes: incoming folder emptyundefined, so never
stopped byits own stop conditionnothing in sightthe turn cap
run timeabout 4 minutes58 minutes
cost this mondaypocket changeroughly ten times loop A, and again next monday
the logone line per action, plus why it endedone line: "updated files"
Loop A's task file · the highlighted lines do the safety work
File any notes sitting in the incoming folder into the research folder, using our date naming. Add one line for each to the summary index.
Stop when the incoming folder is empty. ← the stop condition
Give up after 20 turns. ← the cap
Log every action, one line each. ← the log
Loop B's task file · look for what is missing
Keep the research folder organized and up to date, and improve the summaries where needed.
missing: a stop conditionmissing: a turn capmissing: any log requirement
Module 05 · Walkthrough
A loop with a stop condition
Two automations, same Monday schedule, nobody watching either one. One finishes in four minutes. One would run forever. Three parts:
1 · A finish line2 · No way out3 · The guardrails
A finish line, a cap, and a log
A stop condition a computer can verify. A cap in case the stop condition fails. A log that says what happened and why it ended. All three, every time, and a loop becomes safe to walk away from.