loop-graph

# loop-graph — a graph of agent nodes, not a drifting loop ## What it does & why Turns a vague long-horizon request ("make it production-ready", "accuracy above baseline", "finish the migration") into a small **graph of agent nodes** that stays on-spec across many rounds: - an **executor node** — drives the work round by round against a single scoreboard; - a **supervisor node** — audits the work from *outside* the executor's context (re-verifying claimed-done against the shared standards) and corrects course before drift compounds. Why a graph, not a loop: an agent grinding a long task **is inside the context that drifted**, so it rationalizes scope creep and calls half-done work "done". The nodes talk only through durable, inspectable state (ledger, git tree, directives file) — never a shared, polluted context. **Each node runs on its own timer, and no node ever wakes another.** The executor fires, closes several verified rounds on warm context, and ends. The supervisor fires on a slower cadence, audits, appends corrections, and ends. A correction is picked up on the executor's next fire. Two independent clocks and one file edge — no dispatch, no resume prompt, no liveness protocol, and therefore nothing that can leave the run waiting for a wake that never comes. ## The graph it builds ``` ┌─────────────┐ reads / rewrites ┌──────────────┐ │ EXECUTOR │ ───────────────────▶ │ │ │ node │ ◀─────────────────── │ ledger...