@alphazede/bearing-lite 0.1.10 → 0.1.11

package/skills/bearing-lite/references/peer-synthesis.md

@@ -11,7 +11,7 @@ copy peer text, runtimes, state stores, or authority assumptions.
 | Set Bearings | [Kiro steering](https://kiro.dev/docs/steering/) | durable human-readable workspace context |
 | Gather Supplies | [Matt Pocock grilling](https://github.com/mattpocock/skills/blob/main/skills/productivity/grilling/SKILL.md) | relentless dependency-ordered interview, one recommended question at a time |
 | Map the Route | [Kiro Quick Spec](https://kiro.dev/docs/specs/quick-spec/) and [GitHub Spec Kit](https://github.com/github/spec-kit/blob/main/workflows/speckit/workflow.yml) | staged requirements/design/tasks and explicit gates |
-| Navigator | LangChain subagents | central sequencing, context isolation, and conflict-aware wave integration |
+| Navigator | compatibility diagnostic | unused on new Journeys; Router owns sequencing |
 | Explorer | LangChain subagents | bounded worker dispatch, proven-independent lane coordination, and result integration |
 | Crewmate | Spec Kit implement step | bounded execution after approved planning |
 | Validator | Spec Kit gate | evidence gate on a stable candidate |

package/skills/bearing-lite/references/review-policy.md

@@ -0,0 +1,37 @@
+# Planning review policy
+
+This machine-readable block is the single declarative authority for
+planning-review constraints. `hooks/planning-review.cjs` exports its runtime
+mirror; focused tests require an exact match. Changing these bounds needs
+an explicit owner amendment. This policy records no route, provider, model,
+harness, account, or agent identity.
+
+```json
+{
+  "reviewer_slots_min": 2,
+  "reviewer_slots_max": 2,
+  "independence_required": true,
+  "isolated_findings_until_aggregation": true,
+  "candidate_fields": ["candidate_ref", "candidate_revision", "candidate_digest"],
+  "shared_candidate_required": true,
+  "review_rounds": 1,
+  "aggregated_repairs_max": 1,
+  "post_repair_gate": "deterministic_PASS",
+  "automatic_rereview": "prohibited",
+  "slot_exhaustion_outcome": "FAIL_ROUND",
+  "terminal_outcomes": ["HALT", "OWNER_AMENDMENT_REQUIRED"]
+}
+```
+
+Map the Route writes the separate Journey binding in the approved lineup
+snapshot. It lists unique abstract `slot_id` values, each slot's owner-selected
+`primary_route_ref`, and ordered `fallback_route_refs`. Each receipt records a
+distinct selected route from its slot. All receipts bind to the same non-empty
+candidate ref, revision, and digest. Exhausting any slot
+returns `FAIL_ROUND`. Candidate or independence mismatch, a second round or
+repair, or a missing deterministic PASS after repair returns `HALT`. Automatic
+confirmation or rereview returns `OWNER_AMENDMENT_REQUIRED`.
+
+This gate reviews planning artifacts before dispatch. It never invokes a
+reviewer. Implementation assurance remains governed separately by
+`max_assurance_rounds` and task `required_assurance` / `assurance_rounds`.

package/skills/bearing-lite/references/role-routing.mmd

@@ -1,21 +1,21 @@
 flowchart TD
     O[Owner Authority] <--> R[Stateful Bearing Lite Router]
-    R --> J{Explorer Journey or Expedition?}
     R --> P{Next missing planning stage?}
     P -->|Repository Fit| PF[Fresh Repository Fit]
     P -->|Set Bearings| SB[Fresh Set Bearings]
     P -->|Gather Supplies| GS[Fresh Gather Supplies]
     P -->|Map the Route| MR[Fresh Map the Route]
-    PF & SB & GS & MR -->|typed return| R
-    R --> L[Owner confirms lineup and review cadence]
-    J -->|Explorer Journey: one packet| C[Fresh Crewmate]
-    J -->|Explorer Journey: one wave| E[Fresh Explorer]
-    J -->|Expedition| N[Fresh Navigator]
-    N --> E
+    PF & SB & GS -->|typed return| R
+    R --> MR
+    MR -->|five artifacts with proposed route, lineup, role states, reasoning, cadence| I{One integrated owner review}
+    I -->|change| MR
+    I -->|approve Explorer Journey: one packet| C[Crewmate may continue in-wave]
+    I -->|approve Explorer Journey: one wave| E[Explorer may continue in-wave]
+    I -->|approve Expedition: Router sequences waves| E
     E --> C
-    C --> A{Selected cadence boundary?}
+    C --> A{Final integrated candidate at-end?}
     A -->|Validator declared| V[Fresh Validator]
     A -->|Park Ranger declared| PK[Fresh Park Ranger]
     A -->|Surveyor declared| S[Fresh Surveyor]
     A -->|not yet| E
-    V & PK & S -->|typed verdict| R
+    V & PK & S -->|compact receipt| R

package/skills/bearing-lite/references/task-state.md

@@ -14,7 +14,7 @@ The project's human-readable plan is the only task-state record. Diagrams explai
 | `VALIDATING` | Validator | Evidence sufficiency under validation |
 | `REVIEWING` | Park Ranger when required | Independent defect review active |
 | `ACCEPTANCE` | Surveyor, Owner Authority, or parent coordinator when `required_assurance` is `none` | User-facing acceptance or coordinator completion confirmation is active |
-| `CORRECTION_REQUIRED` | Navigator or nearest parent coordinator | Agent-owned in-authority correction required |
+| `CORRECTION_REQUIRED` | Router or nearest parent coordinator | Agent-owned in-authority correction required |
 | `OWNER_DECISION_REQUIRED` | Owner Authority | Authority, scope, security, or replacement-path judgment required |
 | `COMPLETE` | Parent coordinator after assurance | Outcome and required assurance satisfied |
 | `CANCELLED` | Owner Authority or authorized parent | Task will not proceed |
@@ -36,7 +36,7 @@ The project's human-readable plan is the only task-state record. Diagrams explai
 ## Ownership rules
 
 - One parent coordinator writes each task block and its transitions.
-- Navigator alone writes cross-wave dependencies and Expedition-wide sequencing.
+- Router alone writes cross-wave dependencies and Expedition-wide sequencing.
 - Workers and assurance roles return handoffs; they do not race plan edits.
 - Candidate authors never provide their own Validator, Park Ranger, or Surveyor verdict.
 - Waiting on a prerequisite consumes no correction attempt. Each task has its own three-attempt correction counter; identical retries without new evidence are invalid.

package/skills/bearing-lite/templates/default-role-lineup.md

@@ -6,12 +6,11 @@ implementation and asks whether it is good for the current Journey. Never fill
 agent, model, or reasoning values on the user's behalf.
 
 ```markdown
-review_cadence: <per-slice | per-round | at-end>
+review_cadence: at-end
 
 | Role | Primary agent/harness | Primary model | Primary reasoning | Fallback agent/harness | Fallback model | Fallback reasoning |
 | --- | --- | --- | --- | --- | --- | --- |
 | Router | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
-| Navigator | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
 | Explorer | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
 | Crewmate | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
 | Validator | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
@@ -19,6 +18,9 @@ review_cadence: <per-slice | per-round | at-end>
 | Surveyor | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
 ```
 
+Navigator is not a normal lineup role. Existing plans that still assign it use
+the Navigator compatibility diagnostic; treat the assignment as unused.
+
 Journey artifacts copy the confirmed values and mark named instances active,
 standby, or unused. Only verified primary unavailability activates its approved
 fallback. If both are unavailable, return `OWNER_DECISION_REQUIRED`.

package/skills/bearing-lite/templates/task.md

@@ -2,29 +2,53 @@
 
 Use one compact Markdown block per task in the project's existing plan or progress document. Omit unused conditional fields. Prefer the project's format; add only missing fields. Do not create a Bearing-owned state file or hidden ledger.
 
-## Journey settings (record before task mapping)
+## Journey settings
 
-Record these plan-level choices once, above the task blocks:
+Map the Route records these plan-level proposals above the task blocks in the
+complete five-artifact package. The integrated owner review approves or changes
+the journey, lineup, role states, reasoning, cadence, and plan together; no
+pre-Map lineup or route-review gate is allowed.
 
 ```markdown
 - journey: <Explorer Journey | Expedition>
-- review_cadence: <per-slice | per-round | at-end>
-- choice_basis: <owner-confirmed recommendation and reason>
-- lineup_snapshot: <named active, standby, and unused role instances>
+- review_cadence: at-end
+- choice_basis: <proposed recommendation and reason; owner-approved at integrated review>
+- lineup_snapshot: <named implementation/assurance instances plus the planning_review binding below>
+- planning_review:
+  - policy_ref: skills/bearing-lite/references/review-policy.md
+  - candidate_ref: <shared planning-package reference>
+  - candidate_revision: <shared planning-package revision>
+  - candidate_digest: <shared planning-package digest>
+  - reviewer_slots:
+    - slot_id: <abstract unique slot>
+      primary_route_ref: <owner-selected lineup route reference>
+      fallback_route_refs: [<ordered owner-selected route references>]
+  - round_number: 1
+  - completed_rounds: <0-1>
+  - receipts: <one isolated receipt per slot, including the distinct selected_route_ref>
+  - aggregated_repairs: <0-1>
+  - deterministic_gate: <PASS after repair; otherwise omitted>
 ```
 
-`review_cadence` selects where the Journey's single independent review runs,
-not task-level tests or author self-checks. Never infer it from
-`required_assurance` on an individual task. `per-slice` and `per-round` select
-one declared boundary; `at-end` selects the final integrated candidate. The
-Router asks the owner to confirm both the applicable lineup and boundary before
-implementation.
-`lineup_snapshot` is authoritative for this Journey after recording. Later
+`review_cadence` is `at-end` only. The single independent review runs on the
+final integrated candidate, not at a slice or round boundary, and not as
+task-level tests or author self-checks. Never infer it from
+`required_assurance` on an individual task. The proposal is visible in
+`implementation.md` and `review.html`, then becomes authoritative only after
+the integrated owner approval; do not offer `per-slice` or `per-round`.
+`journey` stays a proposal until the mapped implementation graph exists and the
+integrated owner review approves it. `lineup_snapshot` is authoritative after
+that approval. Later
 edits to `~/.agents/bearing-lite/default-role-lineup.md` have no effect.
 Replace it only through an explicit owner-confirmed dated visible amendment.
 Record the amendment date beside the replacement values. Dispatch identities
 come from this snapshot, not from the current global defaults file.
 
+Every configured planning-review slot uses the same candidate ref, revision,
+and digest. Findings stay isolated until one aggregation. Slot exhaustion is
+`FAIL_ROUND`; policy violations halt or require an owner amendment. The binding
+does not populate `required_assurance` and does not dispatch reviewers.
+
 ## Checkout lease (record before any planning write)
 
 The Router's first write is this visible lease. Inventory nonterminal Journeys
@@ -53,6 +77,26 @@ same generation. `COMPLETE` or `CANCELLED` releases the lease exactly
 once. Stale recovery is explicit, recorded, increments generation, and cannot
 steal a live lease. Process discovery cannot replace this durable lease.
 
+## Wave receipt (record at wave start)
+
+Continuations reuse this visible record beside the checkout lease. Validate at
+wave start, after detected drift, and before commit — not before every
+mutation. Resume from it; do not reread every accepted artifact or redispatch
+completed slices.
+
+```markdown
+- wave_receipt:
+  - wave: <wave id>
+  - lease_generation: <generation>
+  - branch: <branch>
+  - candidate_revision: <revision at last check>
+  - authority: <envelope>
+  - checked_at: <wave_start | external_change | commit>
+```
+
+Stale, forged, or drifted receipts fail closed. Changed HEAD, authority,
+generation, route, or writer overlap forces revalidation or a fresh session.
+
 ## Always present
 
 ```markdown
@@ -67,7 +111,7 @@ steal a live lease. Process discovery cannot replace this durable lease.
 Field rules:
 
 - `task_id` — stable identifier unique within the plan.
-- `outcome` — approved intent for this task only.
+- `outcome` — approved intent for this task only. Never a role-return token and never copied into `verdict`.
 - `status` — one of `PROPOSED`, `READY`, `WAITING_ON`, `IN_PROGRESS`, `EVIDENCE_READY`, `VALIDATING`, `REVIEWING`, `ACCEPTANCE`, `CORRECTION_REQUIRED`, `OWNER_DECISION_REQUIRED`, `COMPLETE`, `CANCELLED`.
 - `assigned_role` — current role contract for the active step, or unassigned while proposing.
 - `depends_on` — list of other `task_id` values only, never prose.
@@ -87,14 +131,18 @@ Field rules:
 
 ```markdown
 - candidate_ref: <strongest native revision or changed-path reference available>
-- evidence: <commands run, results observed, and inferences labeled separately>
+- changed_paths: <paths changed in this candidate>
+- tests: <commands run and observed results>
+- findings: <labeled inferences and gaps>
+- verdict: <closed role-return token>
 - assurance_rounds: <0-1 completed assurance rounds for this Journey>
 ```
 
+`verdict` is one of `ACCEPT`, `ACCEPT_WITH_FINDINGS`, `BLOCK`, `CANDIDATE_READY`, `FAIL`, `GAPS`, `NEEDS_MORE_EVIDENCE`, `OWNER_DECISION_REQUIRED`, `PARTIAL`, `PASS`, `READY`, `REPAIR_REQUIRED`, `REROUTED`, `WAITING_ON`. Do not copy task `outcome` into `verdict`.
 `candidate_ref` must not claim stronger provenance than the client can prove.
 `assurance_rounds` counts the Journey's single submission to required assurance
 against Bearing Lite `max_assurance_rounds`. A repair or replacement candidate
-does not reset it; only a separately scoped new Journey starts at 0. The parent
+does not reset it; only a separately scoped, materially changed new Journey starts at 0, and a new Journey is not a way around the bound. The parent
 coordinator writes the count before dispatch. If the review permits correction, spend at
 most one remaining `attempts` repair, run deterministic coordinator verification,
 and close the gate without another review. A failed repair or scope change
@@ -115,4 +163,4 @@ review. Any source or candidate change during deployment is separately scoped.
 
 ## Single-writer reminder
 
-Only the parent coordinator updates this block after rereading it. Crewmate, Validator, Park Ranger, and Surveyor return handoffs; the coordinator records transitions. Navigator alone changes cross-wave dependencies or global sequencing.
+Only the parent coordinator updates this block after rereading it. Crewmate, Validator, Park Ranger, and Surveyor return compact receipts (`verdict`, `candidate_ref`, `changed_paths`, `tests`, `findings`, `blocker`); the coordinator records transitions. Router alone changes cross-wave dependencies or global sequencing. Update `implementation.md` and `review.html` once per wave, plus owner-decision or blocker changes.

package/skills/crewmate/SKILL.md

@@ -1,10 +1,11 @@
 ---
 name: crewmate
 description: >
-  Implement one approved bounded packet in a fresh session and exact write set.
-  Use for Crewmate, implementation, repair, or integration packets. Do not use
-  for orchestration, planning, independent assurance, publication, destructive
-  action, owner decisions, or unset scope.
+  Implement one approved bounded packet in an exact write set. Continue the
+  same-wave session when identity, authority, route, and generation are
+  unchanged. Use for Crewmate, implementation, repair, or integration packets.
+  Do not use for orchestration, planning, independent assurance, publication,
+  destructive action, owner decisions, or unset scope.
 ---
 
 # Crewmate
@@ -14,36 +15,41 @@ Lowest mutation authority and highest hands-on work in the Bearing ladder.
 ## Inputs and match
 
 - **Inputs:** approved baseline, objective, dependencies, exact write set,
-  authority, acceptance/SEIT rows, commands, cadence, stop rule, return schema,
-  and lineup identity from the recorded Journey snapshot.
+  authority, acceptance/SEIT rows, commands, stop rule, compact return schema,
+  visible wave receipt, and lineup identity from the recorded Journey snapshot.
 - **Match:** one packet is `READY` and every input is fixed.
 - **Non-match:** multi-packet coordination, design gaps, missing authority,
   assurance, or owner-only action.
 
 ## Algorithm
 
-1. Start a fresh session and confirm candidate continuity, boundaries, and clean
-   dependency state. Do not infer missing owner choices. Read dispatch
-   identities only from the recorded Journey snapshot, never from the current
-   global defaults file. Revalidate the visible checkout
+1. Continue the current session when repository, worktree, branch, wave
+   generation, authority, and route are unchanged. Start a fresh session only
+   for a route change, conflicting writer, new authority envelope, independent
+   work, or explicit owner choice. Do not infer missing owner choices. Read
+   dispatch identities only from the recorded Journey snapshot, never from the
+   current global defaults file. Revalidate the visible checkout
    lease against the approved Journey, repository, checkout/worktree, branch,
-   candidate revision, generation, and active state before the first write and
-   every mutation. Released, stale-generation, forged, or
+   candidate revision, generation, and active state at wave start, after
+   detected drift, and before commit. Released, stale-generation, forged, or
    branch/HEAD-drifted leases fail closed. Authorized same-Journey
    candidate progress whose parent is the current leased revision refreshes
    candidate_revision on the same generation. On mismatch, return WAITING_ON without writing.
 2. For a verified contract defect, create the smallest failing regression first.
 3. Make the smallest change that satisfies the packet inside the write set.
-4. Run assigned focused commands and author self-checks. Review cadence never
+   When the packet implements a published standard, verify against the cited
+   document and clause before changing code; neighbouring behavior is not the
+   authority.
+4. Run assigned focused commands and author self-checks. At-end review never
    removes deterministic testing or grants independent-review identity.
-5. Preserve unrelated work and report every changed path and observed result.
+5. Preserve unrelated work. Return only the compact receipt.
 6. Stop on acceptance, authority boundary, design gap, or exhausted correction.
 
 ## Return and recovery
 
 Return `CANDIDATE_READY`, `PARTIAL`, `WAITING_ON`, or
-`OWNER_DECISION_REQUIRED` with plan ref, role, subject, dependencies, scope,
-authority, candidate ref, evidence, blocker, next action, and receiving role.
-Attempts 1–3 require new evidence, hypothesis, or narrower strategy.
+`OWNER_DECISION_REQUIRED` with verdict, candidate_ref, changed_paths, tests,
+findings, and blocker. Attempts 1–3 require new evidence, hypothesis, or
+narrower strategy.
 
 Never expand scope, self-certify as assurance, publish, or hide a failure.

package/skills/explorer/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: explorer
 description: >
-  Own one approved execution wave, dispatching bounded fresh-session packets
-  and integrating their evidence. Use for Explorer Journey, wave orchestration,
-  proven-independent in-wave lanes, or parallel packet sequencing. Do not use
-  for implementation, cross-wave work, planning, automatic nesting, or
-  independent assurance.
+  Own one approved execution wave, continuing bounded packets when the
+  envelope is unchanged and integrating their evidence. Use for Explorer
+  Journey, wave orchestration, proven-independent in-wave lanes, or parallel
+  packet sequencing. Do not use for implementation, cross-wave work, planning,
+  automatic nesting, or independent assurance.
 ---
 
 # Explorer
@@ -15,45 +15,45 @@ Wave authority. Coordinates more and implements less than Crewmate.
 ## Inputs and match
 
 - **Inputs:** approved baseline, wave objective, packet graph, dependencies,
-  scope, authority, lineup from the recorded Journey snapshot, review cadence,
-  acceptance, and return schema.
-- **Match:** one wave needs packet sequencing, dispatch, integration, or
-  proven-independent lane coordination.
-- **Non-match:** one bounded packet needs no orchestration, multiple waves
-  conflict, or assurance alone is requested.
+  scope, authority, lineup from the recorded Journey snapshot, visible wave
+  receipt, acceptance, and compact return schema.
+- **Match:** one wave needs packet sequencing, dispatch, integration, or proven-independent lane coordination.
+- **Non-match:** one bounded packet needs no orchestration, multiple waves conflict, or assurance alone is requested.
 
 ## Algorithm
 
-1. Start fresh and verify wave readiness, exact packet boundaries, dependencies,
-   and approved primary/fallback identities from the recorded Journey snapshot,
+1. Continue this wave when identity, authority, route, and generation are
+   unchanged; otherwise start fresh. Verify wave readiness, packet boundaries,
+   dependencies, and approved identities from the recorded Journey snapshot,
    never from the current global defaults file. Revalidate the visible checkout
    lease against the approved Journey, repository, checkout/worktree, branch,
-   candidate revision, generation, and active state before the first write,
-   dispatch, or integration. Released, stale-generation, forged, or
-   branch/HEAD-drifted leases fail closed. Authorized same-Journey
-   candidate progress whose parent is the current leased revision refreshes
+   candidate revision, generation, and active state at wave start, after
+   detected drift, and before commit. Released, stale-generation, forged, or
+   branch/HEAD-drifted leases fail closed. Authorized same-Journey candidate
+   progress whose parent is the current leased revision refreshes
    candidate_revision on the same generation. The same valid lease continues
-   without duplicate dispatch.
+   without duplicate dispatch. Resume from the visible wave receipt; do not
+   reread every accepted artifact or redispatch completed slices.
 2. Use direct Crewmates by default. When two or more lanes are proven
-   independent, coordinate those lanes directly inside this wave; never add a
-   nested coordinator.
-3. Give every node a fresh bounded session. Never pass raw conversation history.
-4. Inspect returns against write sets and acceptance; integrate evidence without
-   implementing missing packet work.
-5. Dispatch declared assurance once at the owner-confirmed `per-slice`,
-   `per-round`, or `at-end` boundary. At `at-end`, an Explorer Journey reviews
-   its final wave; an Expedition wave defers assurance to the Navigator's final
-   Journey boundary. Deterministic checks always run. Honor
-   `max_assurance_rounds` of 1 from visible `assurance_rounds`. If the review is
-   repairable, spend at most one remaining `attempts` repair, run deterministic
-   coordinator verification, and close the gate without another review. A failed
-   repair or scope change returns `OWNER_DECISION_REQUIRED` with candidate and
-   count. After Journey `COMPLETE`, deployment checks do not reopen assurance.
+   independent, coordinate those lanes directly inside this wave; never add a nested coordinator.
+3. Permit Crewmate continuation when the envelope is unchanged. Never pass raw
+   conversation history. Independent work, a changed envelope, or owner choice
+   starts a fresh Crewmate.
+4. Inspect compact returns against write sets and acceptance; integrate
+   evidence without implementing. Update `implementation.md` and `review.html`
+   once per wave, plus owner-decision or blocker changes.
+5. Dispatch declared assurance only at-end on the final integrated candidate.
+   Expedition waves defer assurance to the Router's final Journey boundary.
+   Deterministic checks always run. Honor `max_assurance_rounds` of 1 from
+   visible `assurance_rounds`. If the review is repairable, spend at most one
+   remaining `attempts` repair, run deterministic coordinator verification,
+   and close the gate without another review. A failed repair or scope change
+   returns `OWNER_DECISION_REQUIRED` with candidate and count. After Journey
+   `COMPLETE`, deployment checks do not reopen assurance.
 
 ## Return and recovery
 
 Return `READY`, `REROUTED`, `WAITING_ON`, or `OWNER_DECISION_REQUIRED` with
-plan ref, role, subject, dependencies, scope, authority, evidence, blocker, next
-action, and receiver. Reroute only from new evidence; three attempts per packet.
+verdict, candidate_ref, changed_paths, tests, findings, and blocker. Reroute only from new evidence; three attempts per packet.
 
 Never implement, self-assure, select models, or expand the wave.

package/skills/gather-supplies/SKILL.md

@@ -15,7 +15,8 @@ Planning node, not a persona or plan-state writer.
 
 - **Match:** a material scope, behavior, authority, risk, or acceptance
   decision is unresolved. The Explorer-versus-Expedition route choice is not
-  gathered here; the Router asks it at the pre-implementation gate.
+  gathered here; the Router asks it at the route review after Map the Route
+  maps the implementation graph.
 - **Non-match:** evidence can answer it, the owner already decided it, or a work
   packet is ready.
 - **Inputs:** goal, visible plan state, repository evidence, prior decisions,

package/skills/map-the-route/SKILL.md

@@ -1,46 +1,57 @@
 ---
 name: map-the-route
 description: >
-  Create or resume Bearing's topic-specific specification, design, SEIT,
-  implementation graph, and self-contained review HTML after decisions are
-  resolved. Use for Map the Route or missing planning artifacts. Do not use to
-  implement, select agents/models, self-approve, or bypass owner review.
+  Create or resume Bearing's complete five-artifact planning package after
+  material decisions are settled. Use for Map the Route or missing planning
+  artifacts. Do not use to implement, select models, self-approve, or bypass
+  the single integrated owner review.
 ---
 
 # Map the Route
 
-Fresh planning node. The Router remains the plan-state writer and user contact.
-
-## Inputs and match
-
-- **Inputs:** confirmed decisions, repository map, artifact status, requirements,
-  owner-selected route/lineup/cadence, repository rules, and return schema.
-- **Match:** first specification gate or post-approval planning package is missing.
-- **Non-match:** executable tasks already map to current approved artifacts.
-
-## Algorithm
-
-1. Derive and announce `<journey-topic>-spec.md` from the confirmed title;
-   require owner input only on ambiguity or collision. Never require generic
-   `plan-spec.md`.
-2. Author in dependency order: testable specification, `design.md`, `seit.md`,
-   then `implementation.md`. Run prospective checks internally; interrupt the
-   owner only when evidence creates a material intent, scope, risk, or authority
-   decision.
-3. Generate one complete self-contained offline `review.html` after all four
-   artifacts are current. Include implementation, traceability, roles, waves,
-   failure/recovery paths, and approval boundaries in that review.
-4. Give every slice stable requirement/design/SEIT IDs, dependencies, exact
-   write set, authority, fresh-session role, evidence, recovery, and stop rule.
-5. Copy the confirmed route, lineup, and review cadence into implementation and
-   HTML. Show named active, standby, and unused role instances.
-6. Open the exact final HTML, verify its launcher/process, and request one
-   integrated owner approval. Use staged owner approvals only when the owner
-   explicitly requests them.
+Fresh planning node. The Router writes Journey state and owns owner conversation.
+
+## Match, inputs, and non-match
+
+- **Match:** material intent is settled and any specification, design, SEIT,
+  implementation graph, or review HTML is missing.
+- **Inputs:** confirmed decisions, repository map and evidence, artifact status,
+  requirements register, repository rules, proposed owner-supplied lineup and
+  `review_cadence: at-end`, plus the return schema.
+- **Non-match:** unresolved material scope, behavior, authority, risk, or
+  acceptance intent returns `REROUTE_GATHER_SUPPLIES`; generate no
+  `implementation.md` or `review.html`.
+
+## Procedure
+
+1. Derive `<journey-topic>-spec.md` from the confirmed title; ask only on
+   ambiguity or collision. Establish whether a requirements register exists;
+   if repository evidence cannot decide, return `NEEDS_OWNER_DECISION`. Never
+   infer one. Registered identities remain references; author only Journey-local
+   criteria; author the needed Journey-level proof or return
+   `NEEDS_OWNER_DECISION` when register authority is unclear.
+2. Author and prospectively check, in dependency order, the testable
+   specification, `design.md`, and `seit.md`. Preserve IDs and do not drop
+   Journey-level proof or published-standard clause coverage.
+3. Map the implementation graph and propose the Explorer Journey or Expedition,
+   active/standby/unused role states, lineup, reasoning, and
+   `review_cadence: at-end`. Bind the planning-review slots to owner-supplied
+   primary and ordered fallback route references under one candidate ref,
+   revision, and digest. Use supplied identities; never invent them.
+4. After those stable source inputs, generate `implementation.md` and the
+   self-contained offline `review.html` together. Each includes the proposed
+   route, lineup, role states, reasoning, cadence, traceability, waves,
+   recovery, approval boundaries, and register references versus Journey-local requirements.
+5. Give every slice stable requirement/design/SEIT IDs, dependencies, exact
+   write set, authority, role, session rule, evidence, recovery, and stop rule.
+6. Open and verify final HTML, then request exactly one integrated owner review
+   of outcome, design, route, lineup, cadence, and plan. Dispatch remains
+   prohibited until approval. An owner change regenerates affected artifacts,
+   then returns to this same gate; never insert a lineup or route-review pause.
 
 ## Return and recovery
 
-Return `PLAN_REVIEW_READY`, `NEEDS_OWNER_DECISION`, or `VALIDATION_FAILED` with
-artifact paths, evidence, blocker, and next action. After approval,
-`review.html` is authoritative. At most three evidence-changing correction
-rounds; never invent approval or implement.
+Return `PLAN_REVIEW_READY`, `REROUTE_GATHER_SUPPLIES`,
+`NEEDS_OWNER_DECISION`, or `VALIDATION_FAILED` with paths, evidence, blocker,
+and next action. Owner-decision pauses do not consume correction rounds. At
+most three evidence-changing correction rounds; never implement or invent approval.

package/skills/map-the-route/references/artifact-grammar.md

@@ -7,16 +7,55 @@ Bearing rejects deviations with typed findings.
 
 1. Frontmatter declares `type` as `plan-spec`, `design`, `seit`, or
    `implementation`, and `status` as `complete` or `amended`.
-2. Requirement IDs use `AC-*` or `RISK-*`; design IDs use `DES-*` or
-   `CONTRACT-*`; SEIT rows use `SEIT-*`; commands use `CMD-*` or `PROC-*`.
-   Suffixes contain only uppercase letters, digits, dots, or hyphens.
+2. Journey-authored requirement IDs use `AC-*` or `RISK-*`; references to an
+   existing requirements register keep that register's identities verbatim.
+   Design IDs use `DES-*` or `CONTRACT-*`; SEIT rows use `SEIT-*`; commands
+   use `CMD-*` or `PROC-*`. Suffixes contain only uppercase letters, digits,
+   dots, or hyphens.
 3. `<journey-topic>-spec.md` declares requirements, Entry criteria, Exit criteria,
    Rollback or repair, and Accountable controller. `design.md` declares design
    IDs. `seit.md` declares SEIT rows and commands.
 4. Preserve stable IDs. Every implementation reference resolves to a declared
    requirement, design contract, SEIT row, and command.
-5. The owner-confirmed lineup and review cadence supply named active, standby,
-   and unused instances. Missing values block implementation drafting.
+5. Owner-supplied lineup identities and proposed `review_cadence: at-end` are
+   required before implementation drafting; missing identities or cadence block
+   drafting. Do not offer `per-slice` or `per-round`. Map the proposed Journey
+   type and active/standby/unused role states before generating implementation;
+   the final implementation and `review.html` record those proposals together.
+6. The lineup snapshot contains the Journey-owned `planning_review` binding:
+   policy reference, one candidate ref/revision/digest, and unique abstract
+   reviewer slots with a primary route reference plus ordered fallback route
+   references. Slot count satisfies the referenced core policy. Do not put route
+   identities in the core policy or map these slots to implementation assurance.
+
+## Requirements register
+
+1. Before authoring a Journey specification, establish whether the target
+   repository or system already has a requirements register and where. When the
+   repository cannot answer, ask the owner; never infer.
+2. Where no register exists, author requirements as today; this section does not
+   apply.
+3. Where a register exists, specification requirement rows are either references
+   to registered identities (no restated text), derivations from them
+   (`AC-X derives from REG-ID`), or Journey-local `AC-*`/`RISK-*` criteria about
+   write sets, seams, gates, or concurrency. Do not restate registered content.
+4. `seit.md` references verification allocations where the register provides
+   them. Where the register provides none for a referenced requirement, author
+   Journey-level proof for it or return `NEEDS_OWNER_DECISION` when register
+   authority is unclear; do not silently drop coverage. Journey-level proof
+   rows remain Journey-local.
+5. `review.html` marks every requirement as either a register reference or
+   Journey-local, so a reviewer can tell which artifact owns each statement.
+6. `design.md` is unaffected: it records how the work is built, which no
+   requirements register covers.
+
+## Published standards
+
+1. When a slice, command, or proof implements a published standard, the plan and
+   its execution manifest cite the exact document and clause.
+2. Verification is against the standard's text, not against neighbouring
+   implementation agreement; a passing cross-boundary test does not substitute
+   for clause conformance.
 
 ## SEIT rules
 
@@ -42,7 +81,8 @@ Bearing rejects deviations with typed findings.
    reasoning level, and review path. Goals are at most 512 characters.
 3. Every manifest declares Write set, Command IDs, Stop condition, and Human
    decision. Optional fields are Shared interfaces (`path#Symbol`), Integration
-   boundary, and Parallel safe (`yes` or `no` plus reason).
+   boundary, Published standard (`doc#clause`) when applicable, and Parallel
+   safe (`yes` or `no` plus reason).
 4. Write sets use one line: `Write only `path``. Paths are bounded, normalized,
    repository-relative literals. Put prohibitions in prose, not the write set.
 5. Multi-slice plans declare consecutive `Wave <n>: <ids>` lines. Every slice
@@ -76,8 +116,9 @@ placeholders, bare negations, or deferral language.
 
 ## Completion boundary
 
-Author specification, design, SEIT, and implementation in that dependency order
-with internal prospective checks. The owner review gate requires all four
-artifacts plus the complete `review.html`; do not insert a specification-only
-owner gate unless the owner explicitly requests staged approvals. The HTML
-becomes authoritative only after integrated owner approval.
+Author specification, design, SEIT, implementation, and review HTML in that
+dependency order with internal prospective checks; generate implementation and
+HTML together after their stable inputs. The single owner review gate requires
+the complete five-artifact package. Do not insert a lineup, route, or
+specification-only owner gate unless the owner explicitly requests staged
+approvals. The HTML becomes authoritative only after integrated owner approval.