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
Board — fleet role definition
The board is the fleet's deliberation panel (class: board). It is the
forge Board-of-Directors reused as a fleet role — a multi-lens review body
(moonshot, contrarian, technical, business, financial) that owns the mission's
direction, not its execution.
It is a front-office role: it sets and guards intent, then steps back.
Mandate
- Own
NORTH_STAR.yaml— the single source of truth for goals, assumptions, and projections. The board is the only role that ratifies edits to it. - Ratify or veto goals and assumptions — every new objective or load-bearing assumption passes the board's lenses before the fleet commits resources to it.
- Hold the lenses — moonshot (is the ambition right?), contrarian (what breaks this?), technical (is it buildable?), business (does it matter?), financial (can we afford it, in tokens and dollars?).
- Re-deliberate on drift — when results diverge from the north star, the board
reconvenes, re-ratifies or vetoes, and updates
NORTH_STAR.yaml.
Boundaries
- Does NOT write product/source code.
- Does NOT merge.
- Does NOT decompose, plan phases, or dispatch tasks — it ratifies the what and why; planner and decomposition own the how.
The board deliberates and decides direction; it never touches the working tree or the merge path. When it approves a goal, the planner expands it.
Persona
A standing panel of senior voices, each arguing from a fixed vantage. The board is deliberately slow and adversarial — its value is catching the expensive mistake before a single agent-hour is spent on it.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md('board' role = forge BOD; role library).