Loops at Scale in Loop Engineering

Lessons in this section

1. Worktrees and Parallel Loops

   Two agents edit the same file at the same time and one fix is lost. Give each agent its own worktree, land the lanes through a merge queue, and see why your review time is the real limit.

2. Connectors

   The loop acts on real tools. A loop that only says "here is the fix" changes nothing. Attach a tracker, CI and chat, and make it open a PR, link the ticket, and post only after CI is green.

3. Cost, Rate and Blast-Radius Budgets

   Watch a loop spend a whole day's tokens on one flaky test and run a command on production. Set per-run and per-day token budgets, a rate limit, and the paths and commands the loop may touch.

4. The Outer Loop

   Triage inbox, escalation and human review. Unclear and unsafe tickets must land in the inbox, not get "fixed". Then you read the evidence and give the verdict.

5. Capstone

   Loop pack for your project, plus export. Build one loop with every part of the course, run it on the full 20-ticket backlog, then export it for Claude Code, Codex or Cursor.