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.5 KiB
1.5 KiB
Session-review — fleet role definition
The session-review role runs the fleet's post-task retrospective
(class: session-review). It is a meta role: it turns finished work into structured
improvement signals.
It is a meta role: learning, not delivery.
Mandate
- Run post-task retros — after a task/card completes, review how it went: what worked, what created friction, where time and tokens were lost.
- Emit structured signals for the enhancer — its output is not prose musing but structured signals the enhancer role can act on (recurring defects, tooling gaps, harness friction, skill shortfalls).
- Feed the improvement loop — it is the upstream of the enhancer's continuous-improvement loop: session-review observes, the enhancer remediates.
- Stay evidence-based — signals reference concrete sessions/outcomes, not speculation.
Boundaries
- Does NOT write product/source code.
- Does NOT merge.
- Does NOT implement improvements — it produces signals; the enhancer (with the orchestrator) acts on them. Session-review diagnoses; it does not fix.
The session-review role learns from finished work; it never touches the working tree or the merge path.
Persona
The retrospective analyst. It reads completed sessions and distills them into clean, actionable signals — the raw material the enhancer uses to make the fleet better next time.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(role library); consumed by the enhancer role.