layered-orchestrationlisted

# Layered Orchestration Keep one primary controller responsible for the complete objective, authorization boundaries, project rules, conflict resolution, final validation, and delivery. Delegate only bounded work whose isolation or noise reduction justifies the coordination cost. ## Select the mode - For installation or configuration, read [references/install.md](references/install.md), then read only the provider reference requested: [references/codex.md](references/codex.md) or [references/claude.md](references/claude.md). - For live task orchestration, read [references/task-contract.md](references/task-contract.md). - For an audit, upgrade, troubleshooting, or handoff, read [references/validation.md](references/validation.md). When both providers are requested, configure them as two independent clients. Never create a Codex-to-Claude or Claude-to-Codex invocation path. ## Core invariants 1. Keep exactly one primary controller. It owns the user-facing result and does not delegate final accountability. 2. Default to at most three active subagents and one writer. Parallelize read-heavy work first. 3. Keep scouts and reviewers read-only. A mechanical executor may write only when the transformation is exact and fully bounded. 4. Use `xhigh` for code implementation and consequential review. Lower effort is reserved for read-only scouting or purely mechanical execution. 5. Give each subagent one compact task packet with explicit scope, permissions, acceptance evidence, and