Loop Engineering, end to end.
6 modules · 8 lessons · 0 project labs · ~3h of reading. Every entry lists what you end up holding, so you can audit the whole path before paying for any of it.
Take this course first
- Harness Engineering. Loop Engineering assumes a single agent loop already runs reliably inside a harness. This course adds the guard rails for letting that loop run unattended and, eventually, across more than one project.
MOD 01Lock what you measure
Before a loop runs unattended, make the one file that decides whether its work counted something it cannot write to itself.
- 01A Loop That Can Edit Its Score Will Edit Its ScoreRead · 19m · concise path · 4 quiz · free · updated 2026-10-04
You end with: loop/protected-paths.md + loop/locked-scorer-hook.json — a permission-layer deny rule scoped to the files that decide whether your loop's work counted, keyed on a session marker the loop itself cannot mint.
MOD 02Screen the candidate
Not every recurring annoyance is a loop. Run the cheap four-gate screen before spending an hour building automation for it.
- 02Most Tasks Do Not Deserve a LoopRead · 19m · concise path · 4 quiz · updated 2026-10-04
You end with: loop/loop-worthiness-checklist.md — four yes/no gates (repeated, token budget named, machine-checkable score, agent can run its own output) run against any candidate task, with the failing gate recorded.
MOD 03Run the ratchet
Snapshot before every change, declare one metric, and keep it only if the number moved past the noise floor — then price what each cycle actually cost.
- 03Keep It Only If The Number Moved: The RatchetRead · 20m · concise path · 4 quiz · updated 2026-10-05
You end with: loop/ratchet-ledger.md — a dated, append-only keep/revert ledger with a noise-floor-based revert rule and a decaying probation tag for proven-noisy metrics.
- 04Spend Tokens In Tiers, Not In LoopsRead · 20m · concise path · 4 quiz · updated 2026-10-04
You end with: loop/spend-tiers.md — a free/cheap/expensive tiered budget table plus cost_usd, tokens_in and tokens_out fields added to your trace schema.
MOD 04Aim, then triage
Split the goal into four tiers that move at different speeds, then score the idea pile before any real tokens get spent on it.
- 05Write the Goal in Four Layers and Let Only One Layer MoveRead · 21m · concise path · 4 quiz · updated 2026-10-04
You end with: harness/goal-hierarchy.md — a north star, a project objective with non-goals, a loop-owned per-cycle backlog, and a guardrail list, each tier naming who may edit it and what has to be true before it does.
- 06Triage the Pile: Score, Try Cheap, Then DecideRead · 21m · concise path · 4 quiz · updated 2026-10-04
You end with: harness/triage-score.md — a five-axis scoring formula with evidence-class and reversibility caps, a three-stage cheap-to-expensive screen, and a niche-archive table keyed on mechanism and layer.
MOD 05Scale across instances
Once more than one project runs the same self-improving loop, canary every template change before it fans out, and never let an instance write back into the shared template.
- 07A loop that improves loops: factory, instances, canaryRead · 20m · concise path · 4 quiz · updated 2026-10-04
You end with: harness/upgrade-ledger.md + harness/canary-checklist.md — a dated propagation ledger and a canary-before-fan-out checklist for spreading template changes across instances.
MOD 06Settle the bar
A fleet of builders and critics needs a bar that exists before it starts. When there is nothing finished to copy, settle every open question first and compile the answers into a key the fleet cannot edit.
- 08Settle the Bar Before the Loop StartsRead · 20m · concise path · 4 quiz · updated 2026-10-09
You end with: loop/fog-map.md + loop/answer-key.md — every undecided question about a build tagged decided or fog, and a pass/fail answer key compiled only from decided lines, each check naming the decision it came from.