When one loop isn't enough

Some quests overflow a single mind: audit this contract, fix what you find, update the docs, prepare the migration. Stuff all of it into one context and quality dilutes with every step — the last chapter told you why.

The move is ancient: decompose. Build a graph of steps:

• Nodes — small, focused tasks, each with its own curated bench.
• Edges — what flows between them: a spec, a diff, a report.

You've done this to code all your life — small functions, single duties, explicit inputs and outputs. Now do it to the work itself.