evolve

# ooo evolve - Evolutionary Loop ## Description Start, monitor, or rewind an evolutionary development loop. The loop iteratively refines the ontology and acceptance criteria across generations until convergence. ## Flow ``` Gen 1: Seed(O₁) → Execute(all nodes) → Judge → Gate Gen 2: Wonder(failed nodes) → Reflect(active nodes only) → Execute(active) → Gate(all) Gen 3: Repeat with a smaller active set; frozen PASS nodes are reverified, not regenerated ...until the outcome gate passes, the working set stagnates, ontology converges, or max 30 generations is reached ``` ## Usage ### Start a new evolutionary loop ``` ooo evolve "build a task management CLI" ``` ### Fast mode (ontology-only, no execution) ``` ooo evolve "build a task management CLI" --no-execute ``` ### Check lineage status ``` ooo evolve --status <lineage_id> ``` ### Record an isolated full-graph benchmark control Call `ouroboros_evolve_step` for an existing Gen 2+ lineage with `benchmark_control: true`, `execute: true`, and an explicit clean Git `project_dir`. Use a distinct clean worktree at the treatment commit. Normal evolve calls keep `benchmark_control` false and never launch a control arm. ### Rewind to a previous generation ``` ooo evolve --rewind <lineage_id> <generation_number> ``` ## Instructions ### Load MCP Tools (Required before Path A/B decision) The Ouroboros MCP tools are often registered as **deferred tools** that must be explicitly loaded before use. **You MUST perform this step before...