graphkit

# graphkit — 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 **clean-context 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". graphkit's nodes talk only through durable, inspectable state (ledger, git tree, directives file) — never a shared, polluted context. The supervisor boots fresh each tick and judges the run like an outside reviewer. ## The graph it builds ``` ┌─────────────┐ reads / rewrites ┌──────────────┐ │ EXECUTOR │ ───────────────────▶ │ │ │ node │ ◀─────────────────── │ ledger.md │ ← single scoreboard │ (does work) │ │ (shared state)│ └─────────────┘ └──────────────┘ ▲ ▲ │ reads each round │ reads only (never writes it) │ │ ┌───...