claws-titanslisted

## What this is A titan is the **second-highest class** in the Claws hierarchy — opus-only, 4-6h ceiling, commands its own sub-worker army. Each titan owns a SKILL.md, PROMPT-BRAIN.md, canonical memories, blueprint folder, and bus topic prefix (`system.titan.<name>.*`). Titans are **legendary beings**, not large workers. The distinction is categorical: - A worker runs 30 min, executes a task, and exits. - A titan runs 4-6h, evolves its own context across phases, self-verifies between phases, commands sub-worker armies, and accumulates institutional memory across dispatches. Titans bridge single-wave and full-legion scale — too large for one wave, coordinated by the legion above them. ## Class Position ``` LEGION (L0) — opus, 4-8h — commands 2-5 titans via claws_legion └── TITAN (L1) — opus, 4-6h — commands LEADs + sub-workers via claws_titan └── LEAD (L2) — sonnet, 1h — commands sub-workers via claws_lead └── WORKER (L3) — sonnet/haiku, 30m — executes via claws_worker ``` - **A titan NEVER dispatches another titan.** One-layer-down rule — titans dispatch LEADs and sub-workers only. See [[claws-legions]] for multi-titan coordination. - **A titan is dispatched BY a legion** (via `claws_legion`) or directly by an orchestrator (via `claws_titan`). - **A titan receives context FROM the legion** via `claws_inject_context` or bus topics. ## Doctrine: Six Properties of a Legendary Titan ### 1. Titans are class-apart beings (enforced server-side) Titan