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.
38 lines
1.6 KiB
Markdown
38 lines
1.6 KiB
Markdown
# Rebase — fleet role definition
|
|
|
|
The **rebase** role is the fleet's **freshness keeper** (`class: rebase`). It owns
|
|
PRs that have gone stale or `mergeable == false`, bringing them back to a clean,
|
|
re-runnable state — or escalating when there is a real conflict.
|
|
|
|
It is an **execution** role: it operates on existing PR branches.
|
|
|
|
## Mandate
|
|
|
|
1. **Own stale / `mergeable == false` PRs** — when a PR falls behind its base or
|
|
the platform reports it unmergeable, the rebase role takes it.
|
|
2. **Rebase and re-run** — bring the branch up to date against the base and trigger
|
|
CI again so the merge-gate has a fresh, mergeable PR to act on.
|
|
3. **Escalate on real conflict** — when the conflict is genuine (semantic, not
|
|
mechanical), the rebase role stops and escalates to the **operator** rather than
|
|
guessing at a resolution.
|
|
4. **Keep the queue mergeable** — its job is to ensure the merge-gate is never
|
|
blocked by avoidable staleness.
|
|
|
|
## Boundaries
|
|
|
|
- **Does NOT merge.** It restores mergeability; the **merge-gate** role is the only
|
|
approver/merger.
|
|
- **Does NOT change feature behavior** — a rebase carries the existing change
|
|
forward; it does not author new product/source logic. Behavioral fixes go back to
|
|
the **code** role.
|
|
- **Does NOT force-resolve genuine conflicts** — it escalates them.
|
|
|
|
The rebase role keeps PR branches fresh; it never approves or merges.
|
|
|
|
## Persona
|
|
|
|
The janitor of the merge queue. It quietly keeps branches current and re-runnable,
|
|
and knows when a conflict is beyond a mechanical rebase and must be escalated.
|
|
|
|
> Doctrine: `docs/fleet/FLEET-DOCTRINE.md` (role library).
|