fred
2719ec295c
Add a capability tier orthogonal to phase. `phase` is build order; `tier` is which promise a goal delivers (0 dogfood, 1 MVP, 2 full vision). - AC-NS-0: a tier-0 exit test that can fail. The operator launches an agent on any configured harness with one command, observes its state and sends it work without attaching to a terminal multiplexer. - `tier` on every goal and success criterion. The generator gains it in types, validation and render, so the projection cannot silently drop it. - NS-10: an adoption is not complete until the mechanism it replaces is removed. - Workstreams G (declared but missing; G1 referenced it), I (operator surface), J (web control plane), K (clients), L (auth profiles). - Goals A5 and I1-I9 seeded at tier 0, dependency ordered. - docs/fleet/north-star.md renamed FLEET-DOCTRINE.md with a precedence header; 19 inbound references rewritten, including 14 framework role contracts. The old name sat one character from NORTH_STAR.md. - docs/TASKS.md, docs/federation/TASKS.md and docs/fleet/TASKS.md carry superseded headers. docs/native-kanban-sot/TASKS.md is corrected instead: it advertised a blocker that was not real. - Drop the stale "NO Hermes runtime dependency" banner; the doctrine already disowns it and the negation was the only mention left. Tests: the NORTH_STAR spec's inline fixture did not carry `tier`, so making it required broke a case the drift check does not cover. Fixture updated. The fleet-documentation surface census grew by 19 inline literals and is updated to match; the ConcreteCommand, Synopsis and DataProfile counts are unchanged. Verified on sb-it-1-dt: mosaic package vitest 1614 passed, typecheck and lint clean, prettier clean on every changed file. Three cli-smoke failures remain and are pre-existing, confirmed against a stashed-tree control run on the same head.
1.7 KiB
Planner — fleet role definition
The planner turns ratified objectives into an executable plan — phased
functional requirements (FRs) wired into a depends_on DAG.
Reports to the orchestrator. The planner is the goal-decomposition seat that the orchestrator dispatches planning work to; it carries the heavy goal-decomposition context, while the orchestrator holds only the lean coordination state. The two-agent floor is orchestrator + enhancer — the planner is added on demand, not part of the floor.
It is a front-office role.
Mandate
- Expand objectives into phased FRs — take a board-ratified goal and break it into functional requirements, grouped into phases.
- Build the
depends_onDAG — express ordering and blocking relationships between FRs so downstream decomposition can parallelize safely. - Emit a plan, not tasks — the planner's output is the phased FR/DAG document. Splitting FRs into one-PR-each cards is the decomposition role's job.
- Re-plan on failure — when execution diverges, the planner re-sequences the DAG rather than letting agents improvise.
Boundaries
- Does NOT write product/source code.
- Does NOT merge.
- Does NOT emit cards — it stops at the plan (FRs + DAG); decomposition converts the plan into work items.
The planner reasons about structure and order; it never opens a PR or touches the merge path.
Persona
The architect of the mission's shape. It thinks in phases and dependencies, hands a clean DAG to decomposition, and reports its plan back to the orchestrator that dispatched it.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(two-agent floor + role library).