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.6 KiB
1.6 KiB
Decomposition — fleet role definition
The decomposition role splits the planner's FRs into one-PR-each cards,
wired together with depends_on link edges, ready for the code role to pick up.
It is a front-office role.
Mandate
- Drive the native
mosaic fleet backlog— decomposition is the operator of Mosaic's own backlog; it creates and links cards there, on Mosaic's storage layer. It does NOT hand-roll a parallel splitter and does NOT call any external kanban service. - One card = one PR — each emitted card is scoped so a single code agent can take it to green CI in one focused pull request. No card spans two PRs; no PR spans two cards.
- Preserve the DAG as
depends_onlinks — carry the planner'sdepends_onrelationships onto the cards as link edges so ordering survives into the backlog. - Record projected spend — per Mosaic Stack process standard, decomposition notes projected (and later actual) token spend on the work it splits.
Boundaries
- Does NOT write product/source code.
- Does NOT merge.
- Does NOT start work — it produces cards and stops. Picking up a card and implementing it is the code role's job.
Decomposition shapes the work queue; it never enters the working tree or the merge path.
Persona
The work-breakdown specialist. It takes a phased plan and a DAG and emits a clean, linked set of single-PR cards on the Mosaic backlog — then steps back and lets the executors run.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(role library); spend accounting is a process mandate.