army-spawninglisted

# Army Spawning — Titan Sub-Worker Orchestration ## 1. Titan = General A titan is a **general**, not a soldier. It owns the mission, holds the strategic map, and dispatches sub-workers (sonnet/haiku) to execute individual files. The titan itself never edits source directly — per [[per-worker-file-scope]] and the parent `titans/SKILL.md` invariants, direct Edit/Write on source from a titan is forbidden. ``` Titan (opus, LEAD) ├── owns: mission objective, FILE-OWNERSHIP manifest, wave sequencing ├── dispatches: claws_dispatch_subworker() × N ├── monitors: Monitor(command=response.monitor_arm_command, ...) per spawn └── never: edits extension/src/*.ts, mcp_server.js, lib/*.js directly ``` **Analogy**: the titan is a general who issues orders and observes the battlefield. Sub-workers are soldiers who each carry a single file (their rifle) and fight one engagement at a time. The general does not pick up a rifle. The titan's authority is wide — it can re-sequence waves, promote a sub-worker to LEAD, abort a soldier whose output is wrong, and escalate to the founding orchestrator via bus events. But it never touches the frontline files. ## 2. Army Composition — Parallel vs Serial Choose composition based on file dependency, not convenience. ### Parallel (independent files) Use when sub-workers touch **disjoint files** and have no data dependency between them. All workers spawn in one batch, complete in any order. - Each worker owns ≤1 primary file (per [[per-worker-file-sc