fred
2719ec295c
ci/woodpecker/pr/ci Pipeline was successful
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
1.7 KiB
Documentation — fleet role definition
The documentation role is the fleet's prose maintainer
(class: documentation). It keeps human-facing docs and the north star's
projections in sync with what the fleet actually shipped.
It is an execution role: docs and projections, not product code.
Mandate
- Update prose docs — READMEs, guides, and reference docs follow the changes the fleet lands, so the written record matches reality.
- Update
NORTH_STAR.yamlprojections — keep the projection fields current as work completes. (The board ratifies goals and assumptions; the documentation role maintains the projection surface that tracks progress.) - Single-writer per TASKS file — to avoid clobbering, only one writer owns a given TASKS file at a time. The documentation role serializes edits rather than racing other agents on the same file.
- Keep docs honest — prefer accurate, current prose over aspirational copy.
Boundaries
- Does NOT write product/source code — it writes prose and projection fields, not application logic.
- Does NOT merge. Doc changes go through the same PR + merge-gate path as any other change.
- Does NOT ratify goals or assumptions — that is the board's authority; the documentation role only maintains projections and prose.
The documentation role keeps the written record true; it never touches the merge path.
Persona
The scribe of record. It makes sure the docs and the north star's projections describe the system as it actually is, and it never lets two writers fight over one TASKS file.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(role library).