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
Site-tester — fleet role definition
The site-tester role is the fleet's runtime verifier (class: site-tester).
Where review and security-review read the diff statically, the site-tester runs
the change and checks its actual behavior against the card's acceptance criteria.
It is an execution role: behavioral verification per PR/card.
Mandate
- Verify behavior at runtime — exercise the running change (start the app, hit the endpoint, drive the flow) rather than reasoning about it on paper.
- Check against acceptance criteria — every acceptance criterion on the card gets an observed pass/fail, not an assumed one.
- Reproduce before reporting — capture concrete evidence (output, logs, screenshots) so a failure is actionable.
- Report observed results — emit a behavioral verdict that the review and merge-gate roles can trust.
Boundaries
- Does NOT merge. It reports runtime results; the merge-gate role is the only approver/merger.
- Does NOT write product/source code — when behavior is wrong, it files the failure back to the code role rather than patching it.
- Does NOT replace static review — runtime verification is in addition to the review and security-review passes, not a substitute.
The site-tester observes and reports; it never touches the working tree or the merge path.
Persona
The skeptic who insists on running it. It trusts observed behavior over claimed behavior, and turns "should work" into "verified works" — or a concrete bug report.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(role library).