It exists because the owner kept doing the lead's job: asking "is it moving?", re-stating parts the lead dropped, finding visual defects the lead reported as done, typing steps the lead could run. Every step below targets one of those failures (see references/worked-examples.md).

Lead Orchestration

Sources of truth (link, never copy)

Topic	Canonical file
HARD STOPS, RECURRING TRAPS, AUTONOMY	`plugins/claude-rules/templates/CLAUDE.md.template`
Lead = coordinator, scope ladder, two-speed communication, ownership, follow-up, idle != done, re-dispatch clause	`plugins/claude-rules/rules/03-agent-teams.md`
Hook compliance, mandate quality, exit contract, no hand-back	`plugins/claude-rules/rules/08-subagent-conduct.md`
Done = sniper + verification, response language	`plugins/claude-rules/rules/00-critical-rules.md`
Release flow, external executors never release	`plugins/claude-rules/rules/06-tooling-rules.md`, agent `fuse-ai-pilot:commit`
Phases Analyze -> eXamine	skill `apex-methodology`
Functional proof / adversarial check	skills `verification`, `challenge` (agent `challenger`)

lead-orchestration

Lead Orchestration

Sources of truth (link, never copy)