docs(fleet): tier the north star and declare the tier-0 operator surface #1336

Closed
opened 2026-08-20 22:34:45 +00:00 by fred · 1 comment
Collaborator

What

Adds a tier dimension to the fleet north star and declares the tier-0 (dogfood) operator surface.

  • 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: 0|1|2 on every goal and success criterion. tier is orthogonal to phase: phase is build order, tier is which promise the item delivers.
  • NS-10 — an adoption is not complete until the mechanism it replaces is removed.
  • Workstream G declared (goal G1 referenced a workstream that did not exist). New workstreams I (operator surface), J (web control plane), K (clients), L (auth profiles).
  • docs/fleet/north-star.md renamed to docs/fleet/FLEET-DOCTRINE.md with a precedence header; 19 inbound references rewritten, including 14 framework role contracts.
  • docs/TASKS.md, docs/federation/TASKS.md, docs/fleet/TASKS.md marked superseded. docs/native-kanban-sot/TASKS.md corrected instead — it advertised a false blocker.
  • Generator packages/mosaic/src/commands/fleet.ts gains tier in types, validation and render, so the projection cannot silently drop it.

Provenance

Change authored by jarvis-vscode (Jason's VS Code session, not a fleet seat) and handed to fred uncommitted. fred ran the verification that had not been run, fixed the four defects it surfaced, and landed it.

Defects found by running the full suite (the handoff had only run the drift check)

  1. fleet-north-star.spec.ts inline fixture missing the now-required tier field — the generator made it required, the fixture was never updated.
  2. Seven InlineLiteral doc-lint diagnostics: new inline backtick spans containing spaces violate the closed grammar enforced on docs/fleet/**.
  3. Doc-corpus census counts stale: InlineLiteral 863 -> 882, total surfaces 887 -> 906. The security-relevant categories (ConcreteCommand 4, Synopsis 5, DataProfile 15) are unchanged.
  4. Four TASKS.md files failed prettier --check; formatting them exposed that the banner's trailing > --- renders as a setext H2 underline. Removed.

Each was proved to be caused by this change with a stash-based control run on the same head.

Done when

  • PR merged to next
  • CI terminal green
  • this issue closed
## What Adds a `tier` dimension to the fleet north star and declares the tier-0 (dogfood) operator surface. - `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: 0|1|2` on every goal and success criterion. `tier` is orthogonal to `phase`: `phase` is build order, `tier` is which promise the item delivers. - `NS-10` — an adoption is not complete until the mechanism it replaces is removed. - Workstream `G` declared (goal `G1` referenced a workstream that did not exist). New workstreams `I` (operator surface), `J` (web control plane), `K` (clients), `L` (auth profiles). - `docs/fleet/north-star.md` renamed to `docs/fleet/FLEET-DOCTRINE.md` with a precedence header; 19 inbound references rewritten, including 14 framework role contracts. - `docs/TASKS.md`, `docs/federation/TASKS.md`, `docs/fleet/TASKS.md` marked superseded. `docs/native-kanban-sot/TASKS.md` corrected instead — it advertised a false blocker. - Generator `packages/mosaic/src/commands/fleet.ts` gains `tier` in types, validation and render, so the projection cannot silently drop it. ## Provenance Change authored by jarvis-vscode (Jason's VS Code session, not a fleet seat) and handed to fred uncommitted. fred ran the verification that had not been run, fixed the four defects it surfaced, and landed it. ## Defects found by running the full suite (the handoff had only run the drift check) 1. `fleet-north-star.spec.ts` inline fixture missing the now-required `tier` field — the generator made it required, the fixture was never updated. 2. Seven `InlineLiteral` doc-lint diagnostics: new inline backtick spans containing spaces violate the closed grammar enforced on `docs/fleet/**`. 3. Doc-corpus census counts stale: InlineLiteral 863 -> 882, total surfaces 887 -> 906. The security-relevant categories (ConcreteCommand 4, Synopsis 5, DataProfile 15) are unchanged. 4. Four `TASKS.md` files failed `prettier --check`; formatting them exposed that the banner's trailing `> ---` renders as a setext H2 underline. Removed. Each was proved to be caused by this change with a stash-based control run on the same head. ## Done when - PR merged to `next` - CI terminal green - this issue closed
fred closed this issue 2026-08-20 23:05:36 +00:00
Author
Collaborator

Merged to next as af43a7a6 (squash), head-pinned to 2719ec295c. Gates: CI 2582 terminal green (all steps OK); independent review APPROVED by rev-code-01, review id 239, pinned to the same head; queue guard state=terminal-success before merge. Auto-closed by the PR.

Two things recorded so they are not lost.

Non-blocking follow-up (rev-code-01, Should Fix). tier validation checks typeof only, so tier: 47 validates and renders "tier 47" into doctrine. The declared domain is 0|1|2 and a membership check is one line. phase carries the same pre-existing weakness. Folding this into task A5 (NORTH_STAR schema validator in CI) rather than filing it separately.

Diff-stat reconciliation, for anyone replicating. My tasking said 27 files +307/-71; rev-code-01 measured 29 files +312/-103 at the same head and named the cause. Both are correct for their diff form: three-dot (merge-base) gives 27/+307/-71, two-dot against next gives 29/+312/-103, and the two extra files are the agent-send pair that next advanced under this branch when #1335 landed. Verified on my side. merge-tree confirmed the merged tree keeps the #1335 guard, and the merge commit bears that out.

Closed by fred.

Merged to `next` as af43a7a6 (squash), head-pinned to 2719ec295c58. Gates: CI 2582 terminal green (all steps OK); independent review APPROVED by rev-code-01, review id 239, pinned to the same head; queue guard `state=terminal-success` before merge. Auto-closed by the PR. Two things recorded so they are not lost. **Non-blocking follow-up (rev-code-01, Should Fix).** `tier` validation checks `typeof` only, so `tier: 47` validates and renders "tier 47" into doctrine. The declared domain is 0|1|2 and a membership check is one line. `phase` carries the same pre-existing weakness. Folding this into task A5 (NORTH_STAR schema validator in CI) rather than filing it separately. **Diff-stat reconciliation, for anyone replicating.** My tasking said 27 files +307/-71; rev-code-01 measured 29 files +312/-103 at the same head and named the cause. Both are correct for their diff form: three-dot (merge-base) gives 27/+307/-71, two-dot against `next` gives 29/+312/-103, and the two extra files are the agent-send pair that `next` advanced under this branch when #1335 landed. Verified on my side. `merge-tree` confirmed the merged tree keeps the #1335 guard, and the merge commit bears that out. Closed by fred.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1336