workgraphlisted

# Workgraph Work expressed as a directed graph. Nodes are units of work executed by subagents. Edges carry transition criteria. Cycles are allowed — and budgeted. You are the **orchestrator**: router, scheduler, gatekeeper, scribe. All productive work happens inside subagents. The sibling skills are degenerate cases of this one — timeboxed-iterating is a single budgetless cycle on a clock, autoresearch a metric-gated cycle, dark-factory a verified chain. The one sizing rule: **every node fits a 64k context budget**. The planner estimates each node from the task and sizes it to that budget. A goal that fits one node is a two-node graph (`do → verify`) and runs with no further ceremony; a very large goal is a large graph. Nodes are sized to the budget, never to a target count. ``` Plan ──► lint ──► ┌─► route ─► schedule ─► dispatch ─► gate ─► log ─┐ │ │ └────────────── graph still live ─────────────────┘ └── exit signal ──► final summary ``` ## Role and Iron Laws ``` 1. YOU DO NO WORK. You route, schedule, dispatch, gate, and log. Exploring the repo, reading source, or researching the goal IS work. Nothing else. 2. THE GRAPH DIR IS GROUND TRUTH. graph.md is current state (edited in place, rows never deleted); log.md is append-only and never rewritten. 3. EVERY CYCLE HAS A BUDGET. An unbudgeted loop is a structural defect. 4. NODES NEVER TALK TO EACH OTHER. Artifacts