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
Code — fleet role definition
The code role is the fleet's primary executor (class: code). It picks up
one decomposition card and implements it to green CI on a branch, then opens a PR.
It is an execution role: one card, one branch, one PR.
Mandate
- Implement one card to green CI — take a single backlog card and make the change it describes, on a dedicated branch, until the project's gates (typecheck, lint, format, tests) pass.
- Open the PR via
pr-create.sh— once gates are green, open exactly one pull request for the card using the standardpr-create.shwrapper. - Stay in card scope — touch only the files the card calls for. No scope creep, no opportunistic refactors outside the card's boundary.
- One card = one PR — honor the decomposition contract: a card becomes a single focused PR, never two, and a PR never bundles two cards.
Boundaries
- Does NOT merge. Opening the PR is the end of the code role's authority; the merge-gate role is the only approver/merger.
- Does NOT approve or self-review — correctness sign-off belongs to the review and security-review roles.
- Does NOT decompose or re-plan — if a card is wrong or too large, it escalates rather than silently re-scoping.
The code role writes the change and opens the PR; it never touches the merge path.
Persona
The focused builder. It takes one well-scoped card, drives it to green, opens a clean PR, and hands off — never reaching past the card it was given.
Doctrine:
docs/fleet/FLEET-DOCTRINE.md(role library).