If you're not the model, you're the loop.
Loop engineering is the discipline of designing the cycle that decides what to prompt, when, and whether the result passes. Prompts are one turn. Loops are a system — and you're not playing every note anymore. You're conducting.
Nine chapters, in playing order.
Read straight through like a score, or jump to the movement you need. Each chapter stands on its own.
Anatomy
The five parts every loop has — named, then engineered.
Read → 02Patterns
Twelve shapes the loop can take, from ReAct to human-in-the-loop.
Read → 03Timescales
Four nested loops, four clocks — and where you conduct.
Read → 04Use cases
Where loops earn their keep, and which pattern fits each job.
Read → 05Trade‑offs
The bargain: money and latency for the chance to be right.
Read → 06Failure modes
Fifteen ways loops break in production, each with its fix.
Read → 07Demos
Four loops you can run in the browser. One is a cautionary tale.
Run → 08The practice path
Five rehearsals from playing it by hand to a loop you trust.
Start → 09Reference
The universal loop, in about twelve lines of code.
Read →