---
name: planning
description: "Use when an Engineer needs file-disjoint sprint plans."
---

# planning: one Engineer owns the plan
Exactly one active Engineer consumes the complete seed without routine operator questions, records evidence-backed assumptions,
and returns only scope-changing contradictions to root. Resume it; duplicates fail.
The flock has exactly two child lead role types: Engineer and Conductor; root sustains
exactly one active Engineer, and 2-6 Conductor lanes are the 99% envelope.
## Required contracts
Load and follow in order:
1. `thinking` for decomposition and explicit assumptions.
2. `sprint-graph` for deliverable, interface, dependency, lane, and evidence composition.
3. `references/orientation-manifest-contract.md` for Native pre/post custody.
4. `references/plan-contract.md` for plan-v2, capacity, review, and lanes.
5. `references/graph-contract.md` as the sole validator for deterministic byte-identical projections.
Author planning artifacts only. Never implement, dispatch execution, or write Native state.
Root runs closed probes; Native binds typed plan-v2 and canonical projections before execution.
Minimize vertical lanes; queue excess under the contract's five-way resident process ceiling.
Preserve overlapping capacity bands and proof requirements, never inventing a global cap.
The Engineer owns bounded Critic revision. The fourth rejection revokes/quarantines natively,
preserves evidence, forbids resume, and returns replacement custody to root.
An explicit `plant next seed and continue` may reuse root only under a new run binding with prior
child authority and review counts cleared before Planter and new Engineer. Fresh root preferred.

`plant` remains the thin command entry and `planting` remains the root-local Planter profile;
their intentional split is not an inheritance shortcut for Engineer planning.