claws-legionslisted

# claws-legions — multi-titan strategic leaders ## What this is A **legion** (Class 6, L0) is the **highest dispatch class in Claws** — opus, 4-8h ceiling, dispatched directly by the orchestrator. No class above a legion. Enforced: `claws_legion` (mcp_server.js L5189–5228) validates via `validateLegionMission()`, injects `CLAWS_PEER_CLASS:'legion'`. Legions command 2-5 [[claws-titans]] across independent subsystems; titans command sub-workers. Legions own **strategy**; titans own tactics. ## When to invoke - 3+ subsystems each needing a titan - Cross-titan file ownership coordination required ## When NOT to invoke - Single subsystem — [[claws-titans]] - Sub-25 workers — [[claws-wave-lead]] directly ## Legion vs Titan: Strategic vs Tactical | Layer | Role | |---|---| | Legion (L0) | **Strategy** — which titans, order, synthesis | | Titan (L1) | **Tactics** — multi-phase within a domain | | Lead (L2) | **Coordination** — sub-worker fan-out | | Worker (L3) | **Execution** — single-file tasks | ## Parallel Legions Under One Orchestrator 2-5 legions may run simultaneously; each owns its subsystem domain. **A legion NEVER dispatches another legion** — one-layer-down rule. Gate via per-spawn Monitor (`monitor_arm_command`, `persistent: true`) — NOT a persistent Monitor on the full bus (which balloons context and kills the orchestrator in ~15 min). `claws_workers_wait` (deprecated as default block primitive — see Per-Spawn Monitor Arming below; kept as escape hatch) is a f