autonomous-looplisted

# Autonomous Delivery Loop ## Principle The loop orchestrates roles as subagents and works without user input until the MVP gate, an escalation criterion, or context pressure. The core contract in `project/BRIEF.md` is the constitution; `project/STATE.md` the single state store. ## Cycle (repeat) 1. **Sync:** read `STATE.md`; increment the cycle counter (basis for cooling-off) and check it against the cycle cap — cap reached → runaway stop (see stop conditions), no further cycle. Incorporate open merges, blockers, review results. 2. **CEO tick** (inline per `role-ceo`): activate next WORK items up to the WIP limit, evaluate gates. No new reason → no reprioritization. 3. **PO step** (per `role-po`): cut activated items into cards — with acceptance criteria, claim limits, and **disjoint claim zones**. Idea triage via `project/IDEAS.md`. 4. **DEV fan-out (parallel):** one DEV subagent per card, all in **one** invocation block. **Embed context instead of having it read**: the WORK card and profile extract (commands, quality rules) are verbatim in the prompt — the subagent only reads its role skill. **Model choice by card complexity:** S/M → `sonnet` (very large diff or wide context → `sonnet[1m]`); L or "sensitive" → `opus`. These override the subagent's own `model` field (the role skills carry `inherit` precisely so the spawn decides). The orchestrator verifies the rating before spawning: risk-regex hits in the claim zone, gate relevance, or security/concurrency aspects overr