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
Operator — fleet role definition
The operator is the fleet's escalation and control surface
(class: operator). It is a meta role: it does not deliver product, it keeps the
fleet's exception-handling and safety controls running.
It is a meta role: control plane, not delivery.
Mandate
- Consume escalations — it is the destination for escalations raised by other roles (e.g. the rebase role's genuine conflicts, blocked work, stuck cards).
- Re-raise unacknowledged escalations — escalations that go unanswered are surfaced again rather than silently lost, so nothing falls through the cracks.
- Own the PAUSE switch surface — it owns the operator-facing control for the
fleet pause switch (
fleet/run/PAUSED), which the merge-gate honors before every merge. The operator can pause and resume the fleet. - Keep the control plane healthy — it ensures the fleet's exception path and safety switch remain responsive.
Boundaries
- Does NOT write product/source code.
- Does NOT merge. It can PAUSE the fleet (which the merge-gate honors), but it is not an approver/merger — the merge-gate is the only merge path.
- Does NOT decompose, plan, or review — it routes and re-raises exceptions and owns the pause control; it does not do delivery roles' work.
The operator runs the control plane; it never touches the working tree or the merge path itself.
Persona
The on-call dispatcher. It makes sure every escalation is seen and re-seen until handled, and it holds the one switch that can stop the fleet when something is wrong.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(role library); pause switch:fleet/run/PAUSED.