@alphazede/bearing-lite 0.1.0 → 0.1.8

package/skills/bearing-lite/SKILL.md

@@ -1,40 +1,47 @@
 ---
 name: bearing-lite
-description: >
-  Bearing Lite router for entry, resume, or unclear next action on repository
-  work. Locates the project plan, next ready task, dependency state, risk, and
-  smallest valid route among planning stages and roles. Activate for bearing
-  lite, start/resume bearing, route the next task, or choose the minimum role
-  path. Do not use for model or provider selection, package publication, deep
-  harness control-room work, or a single already-assigned role packet.
+description: Bearing Lite Router for Journeys. Not for ordinary work, assigned packets, implementation, or publication.
 ---
 
-# Bearing Lite Router
-
-Plugin entry skill. Not a work role. Owner Authority remains human-only.
-
-## Inputs
-
-Plan path, next ready task, dependencies, risk, and available native capabilities.
-
-## Select the smallest route
-
-1. Identify the project plan and next ready task. Missing plan fields stay `PROPOSED`.
-2. Invoke only missing planning stages: `repository-fit`, `set-bearings`, `gather-supplies`, `map-the-route`. Reuse valid evidence; do not replay completed stages.
-3. Choose the least costly role route that preserves dependencies and assurance:
-   - **Direct:** Crewmate → author self-check plus coordinator confirmation when `required_assurance` is `none`; otherwise the declared assurance roles. Add Park Ranger only when required or owner-selected. Validator and Park Ranger appear only when declared, owner-selected, or at a mandatory integrated phase gate.
-   - **Single wave:** Explorer → Crewmate packets with the same assurance rule → Surveyor when multi-packet or owner acceptance requires it. Never automatic Validator per packet.
-   - **Expedition:** Navigator → Trail Boss only for concurrent/conflicting waves → Explorer lanes → optional Sub-explorer → Crewmates, with assurance only where `required_assurance`, owner selection, or a mandatory phase gate requires it.
-   - **Long multi-phase:** Delegate Authority only when the owner explicitly delegates across sessions or Navigator replacement.
-4. Leave dormant roles unselected. No placeholder, receipt, or hidden state.
-5. Report honest hook coverage: full, partial, or skills-only procedural checks.
-
-## Never
-
-- Select models, providers, credentials, launchers, or tool routes.
-- Create, import, or interpret `.bearing` state, MCP, CLI, or a scheduler.
-- Expand owner authority, publish, or self-certify as Validator, Park Ranger, or Surveyor.
-
-## State and task record
-
-Task status lives only in the project plan. See `references/task-state.md` and `templates/task.md`. Orientation diagrams may load later under `references/` and `assets/`; text remains authoritative.
+The Router alone writes Journey planning state and owns owner conversation;
+planning nodes return owner questions. No second start confirmation, `.bearing`,
+or hidden ledger. plugin hosts are partial; skill-copy is skills-only.
+
+1. Say `Preparing this Journey.` Inventory visible nonterminal Journeys; acquire or
+   resume a generation-bound checkout lease before any planning write or dispatch.
+   A live same-checkout competitor returns `WAITING_ON` with sanitized competing identity;
+   Distinct explicitly approved compatible worktrees may proceed.
+2. New Journey: recommend Explorer Journey or Expedition with reason; say when
+   the other fits. Ask exactly: `What Journey shall
+   we Embark on—an Explorer Journey or an Expedition?`
+3. On resume, keep the same lease generation and next incomplete stage. Parent-proven
+   same-Journey progress refreshes `candidate_revision` on that generation.
+   Never replay accepted stages or duplicate a dispatch.
+4. If `~/.agents/bearing-lite/default-role-lineup.md` is absent, create a
+   proposed copy from `templates/default-role-lineup.md`; confirm one role at a
+   time. Never infer identity values.
+5. Run one missing stage in order: Repository Fit → Set Bearings → Gather
+   Supplies. The Router holds every owner conversation inline; Gather Supplies
+   is a Router-led interview, never dispatched. Dispatch a fresh session only
+   for bounded mechanical legwork (mapping, drafting) after stage intent is
+   clear, on a cheaper lower-reasoning model than the Router; integrate returns.
+6. Before Map the Route, display each role's primary/fallback, model, reasoning,
+   and active/standby/unused state. Ask `Is this a
+   good lineup for the roles on this Journey?`; never choose. Recommend cadence
+   with a reason plus one cheaper and one more expensive alternative stating
+   what each gives up or buys. Ask `How often would you like an independent
+   review—per slice, per round, or at the end?`
+7. Record route, lineup, and cadence before task mapping; if declined, record the named default explicitly.
+   The recorded snapshot is authoritative for this Journey. Later edits to
+   `~/.agents/bearing-lite/default-role-lineup.md` have no effect on it. Replace
+   only through an explicit owner-confirmed dated visible amendment. Invoke Map the Route with the snapshot.
+8. Every ready node gets a fresh session with lineup identity from the recorded snapshot.
+
+Return `READY`, `WAITING_ON`, `OWNER_DECISION_REQUIRED`, or `COMPLETE`. Fallback
+follows primary unavailability; both failing returns to owner.
+Allow three evidence-changing corrections. `max_assurance_rounds` is 3 per
+candidate lineage; Direct route checks `assurance_rounds`; Navigator is not required. At the
+bound return `OWNER_DECISION_REQUIRED` naming the candidate and count; new candidate lineage resets;
+release the checkout lease exactly once on `COMPLETE` or `CANCELLED`. Recover by
+explicit recorded generation increment that cannot steal a live lease. Process discovery
+cannot replace the lease. Never implement, self-assure, select models, or publish.

package/skills/bearing-lite/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Bearing Lite"
+  short_description: "Route a stateful repository Journey"
+  default_prompt: "Use $bearing-lite to start or resume this Journey, resolve planning one stage at a time, confirm the lineup and review cadence, then dispatch fresh bounded sessions."
+
+policy:
+  allow_implicit_invocation: false

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

@@ -0,0 +1,19 @@
+# Peer synthesis evidence
+
+Bearing keeps its own skills-first identity, visible Markdown state, authority
+ladder, and assurance separation. The catalog synthesizes behavior; it does not
+copy peer text, runtimes, state stores, or authority assumptions.
+
+| Bearing skill | Strongest compared peer | Behavior retained |
+| --- | --- | --- |
+| Bearing Router | [LangChain subagents](https://docs.langchain.com/oss/python/langchain/multi-agent/subagents) and [handoffs](https://docs.langchain.com/oss/python/langchain/multi-agent/handoffs) | central conversational supervisor, bounded handoff, fresh context |
+| Repository Fit | [Kiro steering](https://kiro.dev/docs/steering/) | verified workspace and explicit global/workspace scope |
+| 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 |
+| 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 |
+| Park Ranger | LangChain reviewer subagent | independent defect review with a typed return |
+| Surveyor | Spec Kit review gate | outcome comparison before completion |

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

@@ -1,34 +1,21 @@
 flowchart TD
-    O[Owner Authority] --> R[Bearing Lite Router]
+    O[Owner Authority] <--> R[Stateful Bearing Lite Router]
+    R --> J{Explorer Journey or Expedition?}
     R --> P{Next missing planning stage?}
-    P -->|Repository Fit| PF[Repository Fit]
-    P -->|Set Bearings| SB[Set Bearings]
-    P -->|Gather Supplies| GS[Gather Supplies]
-    P -->|Map the Route| MR[Map the Route]
-    PF --> R
-    SB --> R
-    GS --> R
-    MR --> R
-    P -->|none| Q{Smallest valid route}
-    Q -->|direct| C[Crewmate]
-    Q -->|wave| E[Explorer]
-    Q -->|expedition| N[Navigator]
-    Q -->|long multi-phase| D[Delegate Authority]
-    D --> N
-    N --> TB{Multiple active or conflicting waves?}
-    TB -->|yes| T[Trail Boss]
-    TB -->|no| E
-    T --> E
-    E --> X{Nested split needed?}
-    X -->|yes| SE[Sub-explorer]
-    SE --> C
-    X -->|no| C
-    C --> A{required_assurance / next missing?}
-    A -->|none: coordinator confirms| Q
-    A -->|Validator| V[Validator]
-    A -->|Park Ranger| PK[Park Ranger]
-    A -->|Surveyor| S[Surveyor]
-    A -->|owner acceptance| O
-    V --> A
-    PK --> A
-    S --> O
+    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
+    E --> C
+    C --> A{Selected cadence boundary?}
+    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

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

@@ -8,7 +8,7 @@ The project's human-readable plan is the only task-state record. Diagrams explai
 | --- | --- | --- |
 | `PROPOSED` | Parent coordinator | Task exists but is not execution-ready |
 | `READY` | Parent coordinator | Dependencies, scope, authority, and route are satisfied |
-| `WAITING_ON` | Parent coordinator | Named prerequisite or independent-assurance dispatch unavailable |
+| `WAITING_ON` | Parent coordinator | Named prerequisite, checkout-lease conflict, or independent-assurance dispatch unavailable |
 | `IN_PROGRESS` | Assigned worker or coordinator | Assigned action is being performed |
 | `EVIDENCE_READY` | Parent coordinator | Candidate and evidence ready for next missing assurance |
 | `VALIDATING` | Validator | Evidence sufficiency under validation |
@@ -40,3 +40,21 @@ The project's human-readable plan is the only task-state record. Diagrams explai
 - 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.
+
+## Checkout lease
+
+The Router inventories visible nonterminal Journeys and holds one
+generation-bound checkout lease before any planning write or dispatch.
+
+- Same checkout plus a live other Journey → `WAITING_ON` with sanitized
+  competing Journey and controller. Distinct explicitly approved compatible
+  worktrees may proceed.
+- Resume keeps the same generation and must not duplicate dispatch.
+- `COMPLETE` or `CANCELLED` releases the lease exactly once.
+- Stale recovery is explicit, recorded, increments generation, and cannot
+  steal a live lease. Forged or stale-generation records fail closed.
+- Branch or HEAD drift from the leased identity stops the transition before
+  mutation. Authorized same-Journey candidate progress whose parent is the
+  current leased revision refreshes `candidate_revision` on the same
+  generation. Foreign controller, branch/worktree, or unrelated HEAD still
+  fail closed as `WAITING_ON`.

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

@@ -1,7 +1,7 @@
 stateDiagram-v2
     [*] --> PROPOSED
     PROPOSED --> READY
-    PROPOSED --> WAITING_ON
+    PROPOSED --> WAITING_ON: named prerequisite or checkout-lease conflict
     WAITING_ON --> READY: prerequisite satisfied
     WAITING_ON --> EVIDENCE_READY: fresh assurance available
     WAITING_ON --> CANCELLED

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

@@ -0,0 +1,24 @@
+# Bearing Lite global defaults
+
+Store the user-owned copy at
+`~/.agents/bearing-lite/default-role-lineup.md`. The Router displays it before
+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>
+
+| 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 |
+| Park Ranger | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
+| Surveyor | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET | OWNER_TO_SET |
+```
+
+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,6 +2,56 @@
 
 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)
+
+Record these plan-level choices once, above the task blocks:
+
+```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` controls independent review frequency, not task-level tests or
+author self-checks. Never infer it from `required_assurance` on an individual
+task. `per-round` means after each integrated execution or correction round;
+`at-end` means one review of the final integrated candidate. The Router asks the
+owner to confirm both the applicable lineup and cadence before implementation.
+`lineup_snapshot` is authoritative for this Journey after recording. 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.
+
+## Checkout lease (record before any planning write)
+
+The Router's first write is this visible lease. Inventory nonterminal Journeys
+first. Do not dispatch or write other planning state until the lease is
+`active` for this Journey.
+
+```markdown
+- checkout_lease:
+  - journey: <Journey id>
+  - controller: <Router>
+  - repository: <canonical repository>
+  - checkout: <worktree or checkout identity>
+  - branch: <branch>
+  - candidate_revision: <candidate revision>
+  - acquired_at: <acquisition time>
+  - generation: <positive integer>
+  - state: <active | released>
+```
+
+Same checkout plus a live other Journey returns `WAITING_ON` with sanitized
+competing Journey and controller identities. Distinct explicitly approved
+compatible worktrees may proceed. Resume keeps the same generation and does
+not duplicate dispatch. Authorized same-Journey candidate progress whose
+parent is the current leased revision refreshes `candidate_revision` on the
+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.
+
 ## Always present
 
 ```markdown
@@ -37,9 +87,15 @@ Field rules:
 ```markdown
 - candidate_ref: <strongest native revision or changed-path reference available>
 - evidence: <commands run, results observed, and inferences labeled separately>
+- assurance_rounds: <0-3 completed assurance rounds for this candidate lineage>
 ```
 
 `candidate_ref` must not claim stronger provenance than the client can prove.
+`assurance_rounds` counts each candidate version submitted to required assurance
+in one candidate lineage against Bearing Lite `max_assurance_rounds`. A repair
+of the same work stays in the lineage. A new candidate lineage resets the count
+to 0. The parent coordinator writes the count and checks it before redispatched
+assurance.
 
 ## Waiting or correcting only
 

package/skills/crewmate/SKILL.md

@@ -1,37 +1,49 @@
 ---
 name: crewmate
 description: >
-  Implement one approved mutation, execution, or integration packet inside its
-  exact write set with native tools. Use for crewmate, implement packet, bounded
-  coding task, or apply a write-set change. Do not use for wave orchestration,
-  multi-packet control, self-certification, publication, or expanding authority.
+  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.
 ---
 
 # Crewmate
 
-## Trigger
-
-- **Match:** one approved implementation, repair, or integration packet is READY with fixed scope and authority.
-- **Non-match:** multi-packet orchestration, wave ownership, assurance review, owner decisions, or unset write sets.
-
-## Inputs
-
-Plan path, packet objective, acceptance, allowed paths, commands, stop condition, `required_assurance`, expected handoff.
-
-## Responsibility
-
-Smallest honest change in the write set. For verified contract bugs, add a failing regression first, then repair. Run assigned focused commands. Preserve unrelated work.
-
-## Return
-
-Handoff fields: `plan_ref`, `role`, `subject`, `depends_on`, `scope`, `authority`, `outcome`, `evidence`, `blocker`, `next_action`, `receiving_role`.
-
-Outcomes: `CANDIDATE_READY`, `PARTIAL`, `WAITING_ON`, `OWNER_DECISION_REQUIRED`. Receiver: parent coordinator; Validator only when `required_assurance` includes it or owner opts in.
-
-## Independence
-
-Never self-certifies. `required_assurance: none` means author self-check plus coordinator confirmation—not automatic Validator/Park Ranger.
-
-## Correction
-
-Repair evidenced failures inside authority. Design, write-set, or acceptance changes escalate without silent expansion.
+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.
+- **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
+   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
+   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
+   removes deterministic testing or grants independent-review identity.
+5. Preserve unrelated work and report every changed path and observed result.
+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.
+
+Never expand scope, self-certify as assurance, publish, or hide a failure.

package/skills/explorer/SKILL.md

@@ -1,38 +1,57 @@
 ---
 name: explorer
 description: >
-  Wave-owner orchestration: sequence and dispatch bounded packets inside one
-  approved wave without implementing them. Use for explorer, wave ownership,
-  packet orchestration, or parallel dispatch planning. Do not use for product
-  implementation, multi-wave Trail Boss control, nested Sub-explorer defaulting,
-  or independent assurance of wave output.
+  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.
 ---
 
 # Explorer
 
-## Trigger
-
-- **Match:** an approved wave contains work packets that need orchestration, sequencing, or parallel dispatch (not the implementation itself).
-- **Non-match:** a single already-bounded implementation packet with no wave orchestration need; multi-wave Trail Boss duty; assurance review.
-
-## Inputs
-
-Plan path, wave objective, packets, dependencies, scope, authority, `required_assurance`, expected handoff.
-
-## Responsibility
-
-Issue disjoint Crewmate packets, inspect returns against allowlists, and hand off for coordinator confirmation or required assurance. Never implement or audit the packets itself.
-
-## Return
-
-Handoff fields: `plan_ref`, `role`, `subject`, `depends_on`, `scope`, `authority`, `outcome`, `evidence`, `blocker`, `next_action`, `receiving_role`.
-
-Outcomes: `READY`, `REROUTED`, `WAITING_ON`, `OWNER_DECISION_REQUIRED`. Receiver: Sub-explorer, Crewmate, or parent coordinator.
-
-## Independence
-
-Wave owner only. Does not provide Validator, Park Ranger, or Surveyor verdicts for candidates produced under its dispatch when it is author-equivalent.
-
-## Correction
-
-Reroute incomplete packets with new evidence. Authority or design amendments escalate to parent coordinator or Owner Authority.
+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.
+
+## Algorithm
+
+1. Start fresh and verify wave readiness, exact packet boundaries, dependencies,
+   and approved primary/fallback 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 on the same generation. The same valid lease continues
+   without duplicate dispatch.
+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 at `per-slice` or after each integrated execution
+   or correction round at `per-round`. At `at-end`, an Explorer Journey reviews
+   its final wave once; an Expedition wave defers assurance to the Navigator's
+   final Journey boundary. Deterministic checks always run. Before redispatched
+   assurance, honor `max_assurance_rounds` from visible `assurance_rounds`. At
+   the bound, return `OWNER_DECISION_REQUIRED` with candidate and count; do not
+   dispatch another repair or review. A new candidate lineage resets the count.
+
+## 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.
+
+Never implement, self-assure, select models, or expand the wave.

package/skills/gather-supplies/SKILL.md

@@ -1,33 +1,53 @@
 ---
 name: gather-supplies
 description: >
-  Resolve only material owner decisions that block a complete plan after the
-  workspace exists. Use for gather supplies, owner decisions, plan-spec
-  assumptions, or blocking scope questions. Do not use for design drafting,
-  implementation, product edits, or replaying settled owner answers.
+  Relentlessly resolve material owner decisions for a Bearing Journey, one
+  dependency-ordered question at a time, until shared understanding is explicit.
+  Use for Gather Supplies or unresolved plan intent. Do not use for discoverable
+  repository facts, design drafting, implementation, or settled decisions.
 ---
 
 # Gather Supplies
 
-Procedural stage. Not a persona.
-
-## Match / non-match
-
-- **Match:** material open decisions block scope, architecture, security, authority, or acceptance.
-- **Non-match:** decisions already recorded; Map the Route can proceed; pure implementation packets.
-
-## Inputs
-
-Goal, repository evidence, plan workspace, and prior owner Q&A.
-
-## Procedure
-
-1. Ask only material questions; reuse durable prior answers without re-asking.
-2. For each question: recommendation, evidence, options/tradeoffs, affected section, safe default.
-3. Apply completed answers into the validated plan specification only.
-4. Keep requirements testable with stable IDs; record blockers instead of inventing approval.
-5. Exit with zero-to-few bounded questions, applied plan-spec, or `OWNER_DECISION_REQUIRED`.
-
-## Never
-
-Design the route, draft implementation slices, edit product code, or overwrite a recorded owner answer with a default.
+Planning node, not a persona or plan-state writer.
+
+## Match and inputs
+
+- **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.
+- **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,
+  open decision tree, and return schema.
+
+## Algorithm
+
+1. Inspect the repository and available evidence before asking. Never ask the
+   owner for a fact tools can establish.
+2. Select the earliest unresolved decision whose dependencies are satisfied.
+3. Ask exactly one question, relayed to the owner through the Router. Lead
+   with the recommended answer and why, then explain only material
+   alternatives and tradeoffs. Wait for the owner.
+4. Challenge vague terms, contradictions, unsafe assumptions, and incomplete
+   acceptance. A default, probability, or silence is not approval.
+5. Follow the affected dependency branch. Revisit an earlier answer when new
+   evidence conflicts; otherwise do not replay it.
+6. Buffer confirmed decisions in the active session. Do not persist, patch, or
+   re-render Journey state after each answer.
+7. Return one consolidated decision batch to the Router at a natural checkpoint:
+   the dependency branch is complete, Map the Route is next, handoff/context
+   loss is imminent, or the owner requests a flush.
+8. When no material branch remains, summarize the shared interpretation and ask
+   for explicit confirmation that shared understanding has been reached; then
+   return the final decision batch.
+
+## Return and recovery
+
+Return `DECISION_CONFIRMED`, `SHARED_UNDERSTANDING_CONFIRMED`,
+`NEEDS_EVIDENCE`, or `OWNER_DECISION_REQUIRED` with decision ID, answer,
+rationale, affected requirements, buffered decision count, remaining branch,
+checkpoint, and next action. Stop after three evidence-changing attempts on one
+blocked decision.
+
+Never write Journey state, choose for the owner, design, or implement.