@alphazede/bearing-lite 0.2.1 → 1.0.0

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

@@ -12,9 +12,9 @@ The project's human-readable plan is the only task-state record. Diagrams explai
 | `IN_PROGRESS` | Assigned worker or coordinator | Assigned action is being performed |
 | `EVIDENCE_READY` | Parent coordinator | Candidate and evidence ready for next missing assurance |
 | `VALIDATING` | Assurance Test Engineer | 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` | Router or nearest parent coordinator | Agent-owned in-authority correction required |
+| `REVIEWING` | Reviewer when required | Independent defect review active |
+| `ACCEPTANCE` | Integration Engineer execution, Owner Authority, or parent coordinator when `required_assurance` is `none` | User-facing acceptance or coordinator completion confirmation is active |
+| `CORRECTION_REQUIRED` | Orchestrator 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 |
@@ -27,7 +27,7 @@ The project's human-readable plan is the only task-state record. Diagrams explai
 - `IN_PROGRESS` → `EVIDENCE_READY` with candidate and handoff; → `CORRECTION_REQUIRED` on correctable failure; → `OWNER_DECISION_REQUIRED` on security, authority, or integrity guard.
 - `CORRECTION_REQUIRED` → `READY` on attempt 1 or 2 with a new hypothesis and evidence; → `OWNER_DECISION_REQUIRED` on the third failed correction or out-of-contract amendment.
 - `EVIDENCE_READY` → `VALIDATING` | `REVIEWING` | `ACCEPTANCE` for the next missing required role; → `WAITING_ON` if assurance dispatch is unavailable.
-- During the single assurance round, an accepted Assurance Test Engineer or Park Ranger handoff returns to `EVIDENCE_READY` to select the next missing assurance role in declared order.
+- During the single assurance round, an accepted Assurance Test Engineer or Reviewer handoff returns to `EVIDENCE_READY` to select the next missing assurance role in declared order.
 - `VALIDATING` → `CORRECTION_REQUIRED` when more evidence or repair is needed; otherwise back through `EVIDENCE_READY` for remaining assurance.
 - `REVIEWING` → `CORRECTION_REQUIRED` | `EVIDENCE_READY` | `OWNER_DECISION_REQUIRED` by verdict.
 - `ACCEPTANCE` → `COMPLETE` when every required assurance accepted the same candidate; when `required_assurance` is `none`, parent-coordinator confirmation satisfies the assurance requirement; → `CORRECTION_REQUIRED` on acceptance gap.
@@ -36,27 +36,27 @@ 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.
-- Router alone writes cross-wave dependencies and Expedition-wide sequencing.
+- Orchestrator alone writes cross-wave dependencies and Lifecycle-wide sequencing.
 - Workers and assurance roles return handoffs; they do not race plan edits.
-- Candidate authors never provide their own Assurance Test Engineer, Park Ranger, or Surveyor verdict.
+- Candidate authors never provide their own Assurance Test Engineer, Reviewer, or Integration Engineer execution 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.
 - Each declared phase or wave receives at most one assurance round and one review-directed repair. Replacement candidates do not reset the count within that declared unit; the next distinct declared phase or wave carries its own 1/1 budget. The coordinator verifies that repair deterministically and does not dispatch assurance again.
 - `COMPLETE` is terminal for Bearing assurance. An already authorized deployment keeps operational verification and rollback readiness but does not reopen review; candidate-changing deployment work requires separate scope.
 
 ## Checkout lease
 
-The Router inventories visible nonterminal Journeys and holds one
+The Orchestrator inventories visible nonterminal Lifecycles 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
+- Same checkout plus a live other Lifecycle → `WAITING_ON` with sanitized
+  competing Lifecycle 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
+  mutation. Authorized same-Lifecycle 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

@@ -13,8 +13,8 @@ stateDiagram-v2
     CORRECTION_REQUIRED --> READY
     CORRECTION_REQUIRED --> OWNER_DECISION_REQUIRED: third failed correction
     EVIDENCE_READY --> VALIDATING: Assurance Test Engineer required
-    EVIDENCE_READY --> REVIEWING: Park Ranger required
-    EVIDENCE_READY --> ACCEPTANCE: Surveyor, owner, or coordinator when required_assurance is none
+    EVIDENCE_READY --> REVIEWING: Reviewer required
+    EVIDENCE_READY --> ACCEPTANCE: Integration Engineer execution, owner, or coordinator when required_assurance is none
     EVIDENCE_READY --> WAITING_ON: assurance dispatch unavailable
     VALIDATING --> CORRECTION_REQUIRED
     VALIDATING --> EVIDENCE_READY: pass, select next assurance

package/skills/bearing-lite/references/verification.md

@@ -0,0 +1,52 @@
+# Deterministic verification adapter
+
+Decision source: `DEC-BDL-036`, `DEC-BDL-037`, `DEC-BDL-053`, `DES-BDL-008`,
+`AC-BDL-009`, `CONTRACT-BDL-005`.
+
+`hooks/verification.cjs` is the exact runtime evaluator of this contract. It
+declares no hook class and registers no host event. A backend is never a role.
+Reverify is optional profile configuration; this adapter never downloads or
+installs it.
+
+A **request** binds candidate, claim, backend, stage, authority, expected
+result, and command/configuration, plus whether the backend is `selected` or
+`required` for that claim. A **receipt** binds the same candidate, claim,
+backend, version, command/configuration, and evidence digest. Status values
+are `VERIFIED`, `REFUTED`, `INCONCLUSIVE`, and `ERROR`.
+
+## Authority
+
+- **diagnostic** — Implementer, Light Implementer, and Integration Engineer
+  execution may emit diagnostic receipts. They help implementation and
+  integration. They never satisfy an assurance gate.
+- **assurance** — Test Engineer assurance independently reruns required claims
+  against the exact stable candidate in a fresh session. Reviewer may request
+  deterministic verification to adjudicate a specific suspected defect. The
+  Orchestrator routes and records; it never treats a backend as a role.
+
+Candidate authors cannot turn their own runs into an assurance PASS. An
+independent assurance session must rerun required claims. Diagnostic and
+assurance receipts remain distinguishable.
+
+## Backend activation
+
+Activation is selected OR required. Unavailability of an activated backend is a
+typed gap (`ERROR` / `backend_unavailable`), not success and not invented
+behavior. Only unselected AND unrequired absence stays inactive and is not a
+global failure. Profile `reverify.enabled` records user configuration;
+availability does not select Reverify for every task. Planning Test Engineer
+selects it on an applicable binary-level SEIT claim; Plan Integrator copies
+that selection and must not invent V&V.
+
+## Gates
+
+- Assurance gate: only an independent `assurance` receipt whose candidate,
+  claim, backend, version, command/configuration, and evidence digest bind the
+  current candidate, and whose status matches the expected result, may be
+  `gate_eligible`. `INCONCLUSIVE` and `ERROR` cannot become PASS.
+- Post-repair deterministic closure reruns required checks on the repaired
+  candidate without a second review round. Author diagnostics and stale
+  pre-repair evidence cannot close it. Automatic rereview is prohibited.
+
+Stale evidence is a receipt bound to a prior candidate or to a pre-repair
+evidence digest. Candidate mismatch fails closed.

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

@@ -2,18 +2,18 @@
 
 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
+## Lifecycle settings
 
-Map the Route records these plan-level proposals above the task blocks in the
+Planning and Design 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.
+the lifecycle, profile, role states, reasoning, cadence, and plan together; no
+pre-planning profile or route-review gate is allowed.
 
 ```markdown
-- journey: <Explorer Journey | Expedition>
-- review_cadence: at-end
+- lifecycle: <direct packet | coordinator wave | orchestrated waves>
+- review_cadence: phase
 - choice_basis: <proposed recommendation and reason; owner-approved at integrated review>
-- lineup_snapshot: <named implementation/assurance instances plus the planning_review binding below>
+- profile_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>
@@ -21,7 +21,7 @@ pre-Map lineup or route-review gate is allowed.
   - candidate_digest: <shared planning-package digest>
   - reviewer_slots:
     - slot_id: <abstract unique slot>
-      primary_route_ref: <owner-selected lineup route reference>
+      primary_route_ref: <owner-selected profile route reference>
       fallback_route_refs: [<ordered owner-selected route references>]
   - round_number: 1
   - completed_rounds: <0-1>
@@ -30,17 +30,18 @@ pre-Map lineup or route-review gate is allowed.
   - deterministic_gate: <PASS after repair; otherwise omitted>
 ```
 
-`review_cadence` is `at-end` for each declared phase or wave. The single
-independent review runs on that unit's integrated candidate at its end, not at
-a slice or round boundary, and not as
-task-level tests or author self-checks. Never infer it from
+Cadence values are `slice`, `phase`, or `lifecycle` for each declared phase or
+wave. Defaults are `phase` for Test Engineer assurance, `phase` for Reviewer,
+and `lifecycle` for Integration Engineer execution. The single independent
+review runs on that unit's integrated candidate at its declared cadence
+boundary, 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.json` 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/lineups.json` have no effect. The `Router`
+`implementation.json` and the DoD Manifest, then becomes authoritative only
+after the integrated owner approval.
+`lifecycle` stays a proposal until the mapped implementation graph exists and
+the integrated owner review approves it. `profile_snapshot` is authoritative
+after that approval. Later
+edits to `~/.agents/bearing-lite/profiles.json` have no effect. The `Orchestrator`
 row of the snapshot is the observed identity of the session that ran planning
 (harness, model, reasoning at that time); it is never a catalog selection and
 never a deviation.
@@ -55,14 +56,14 @@ 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
+The Orchestrator's first write is this visible lease. Inventory nonterminal Lifecycles
 first. Do not dispatch or write other planning state until the lease is
-`active` for this Journey.
+`active` for this Lifecycle.
 
 ```markdown
 - checkout_lease:
-  - journey: <Journey id>
-  - controller: <Router>
+  - journey: <Lifecycle id>
+  - controller: <Orchestrator>
   - repository: <canonical repository>
   - checkout: <worktree or checkout identity>
   - branch: <branch>
@@ -72,10 +73,10 @@ first. Do not dispatch or write other planning state until the lease is
   - state: <active | released>
 ```
 
-Same checkout plus a live other Journey returns `WAITING_ON` with sanitized
-competing Journey and controller identities. Distinct explicitly approved
+Same checkout plus a live other Lifecycle returns `WAITING_ON` with sanitized
+competing Lifecycle 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
+not duplicate dispatch. Authorized same-Lifecycle 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
@@ -129,9 +130,9 @@ Field rules:
 - required_assurance: [Assurance Test Engineer]
 ```
 
-`required_assurance` lists only roles that must accept the same candidate (for example `Assurance Test Engineer`, and `Park Ranger` or `Surveyor` when their triggers apply).
+`required_assurance` lists only roles that must accept the same candidate (for example `Assurance Test Engineer`, and `Reviewer` or `Integration Engineer execution` when their triggers apply).
 
-test-writing Crewmate write set is tests and approved fixtures only. Product
+test-writing Implementer write set is tests and approved fixtures only. Product
 write set excludes tests and must not weaken independently authored tests.
 Neither self-certifies.
 
@@ -172,4 +173,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, Test Engineer, 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.json` and `review.html` once per wave, plus owner-decision or blocker changes.
+Only the parent coordinator updates this block after rereading it. Implementer, Test Engineer, Reviewer, and Integration Engineer execution return compact receipts (`verdict`, `candidate_ref`, `changed_paths`, `tests`, `findings`, `blocker`); the coordinator records transitions. Orchestrator alone changes cross-wave dependencies or global sequencing. Update `implementation.json` and the DoD Manifest once per wave, plus owner-decision or blocker changes.

package/skills/{explorer → coordinator}/SKILL.md

@@ -1,59 +1,59 @@
 ---
-name: explorer
+name: coordinator
 description: >
   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
+  envelope is unchanged and integrating their evidence. Use for Coordinator,
+  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
+# Coordinator
 
-Wave authority. Coordinates more and implements less than Crewmate.
+Wave authority. Coordinates more and implements less than Implementer.
 
 ## Inputs and match
-
 - **Inputs:** approved baseline, wave objective, packet graph, dependencies,
-  scope, authority, lineup from the recorded Journey snapshot, visible wave
+  scope, authority, profile from the recorded Lifecycle 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. 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,
+   dependencies, and approved identities from the recorded Lifecycle snapshot,
    never from the current global defaults file. Revalidate the visible checkout
-   lease against the approved Journey, repository, checkout/worktree, branch,
+   lease against the approved Lifecycle, repository, checkout/worktree, branch,
    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
+   branch/HEAD-drifted leases fail closed. Authorized same-Lifecycle candidate
    progress whose parent is the current leased revision refreshes
    candidate_revision on the same generation. The same valid lease continues
    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
+2. Use direct Implementers by default. When two or more lanes are proven
    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
+3. Permit Implementer continuation when the envelope is unchanged. Never pass raw
    conversation history. Independent work, a changed envelope, or owner choice
-   starts a fresh Crewmate.
+   starts a fresh Implementer.
 4. Inspect compact returns against write sets and acceptance; integrate
-   evidence without implementing. Update `implementation.json` and `review.html`
+   evidence without implementing. Update `implementation.json` and the DoD Manifest
    once per wave, plus owner-decision or blocker changes.
-5. Dispatch declared assurance automatically at wave-end on this wave's
-   integrated candidate. Deterministic checks always run. Honor
+   Apply `../bearing-lite/references/owner-stops.md` for queued questions,
+   blocking prerequisites, proven-independent progress and owner holds; never
+   add unapproved roles or gates.
+5. Dispatch declared assurance automatically at wave-end, or the configured cadence
+   boundary, on this wave's integrated candidate. Deterministic checks always run. Honor
    `max_assurance_rounds` of 1 per declared phase or wave 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. The next distinct declared
    phase or wave carries its own budget. A failed repair or scope change
-   returns `OWNER_DECISION_REQUIRED` with candidate and count. After Journey
+   returns `OWNER_DECISION_REQUIRED` with candidate and count. After Lifecycle
    `COMPLETE`, deployment checks do not reopen assurance.
 
 ## Return and recovery
-
 Return `READY`, `REROUTED`, `WAITING_ON`, or `OWNER_DECISION_REQUIRED` with
 verdict, candidate_ref, changed_paths, tests, findings, and blocker. Reroute only from new evidence; three attempts per packet.
 

package/skills/{crewmate → implementer}/SKILL.md

@@ -1,14 +1,15 @@
 ---
-name: crewmate
+name: implementer
 description: >
   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.
+  unchanged. Use for Implementer, Product Implementer, Test Implementer,
+  implementation, repair, or integration packets. Do not use for
+  orchestration, planning, independent assurance, publication, destructive
+  action, owner decisions, or unset scope.
 ---
 
-# Crewmate
+# Implementer
 
 Lowest mutation authority and highest hands-on work in the Bearing ladder.
 
@@ -16,13 +17,14 @@ Lowest mutation authority and highest hands-on work in the Bearing ladder.
 
 - **Inputs:** approved baseline, objective, dependencies, exact write set,
   authority, acceptance/SEIT rows, commands, stop rule, compact return schema,
-  visible wave receipt, and lineup identity from the recorded Journey snapshot.
+  visible wave receipt, and profile identity from the recorded Lifecycle 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.
-- **Split:** test-writing Crewmate may change only tests and approved
-  fixtures. Product Crewmate write set excludes tests and must not weaken
-  independently authored tests. Neither self-certifies.
+- **Split:** `tdd` orders test-writing Test Implementer before Product Implementer.
+  Test Implementer may change only tests and approved fixtures. Product Implementer
+  write set excludes tests and must not weaken independently authored tests.
+  `single_implementer` writes product plus tests. Neither self-certifies.
 
 ## Algorithm
 
@@ -30,12 +32,12 @@ Lowest mutation authority and highest hands-on work in the Bearing ladder.
    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,
+   dispatch identities only from the recorded Lifecycle snapshot, never from
+   the current global defaults file. Revalidate the visible checkout
+   lease against the approved Lifecycle, repository, checkout/worktree, branch,
    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
+   branch/HEAD-drifted leases fail closed. Authorized same-Lifecycle
    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.
@@ -43,8 +45,8 @@ Lowest mutation authority and highest hands-on work in the Bearing ladder.
    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.
+4. Run assigned focused commands and author self-checks. At-end review never removes
+   deterministic testing or grants independent-review identity; diagnostic verification receipts never satisfy an assurance gate.
 5. Preserve unrelated work. Return only the compact receipt.
 6. Stop on acceptance, authority boundary, design gap, or exhausted correction.
 

package/skills/{repository-fit → intake}/SKILL.md

@@ -1,19 +1,20 @@
 ---
-name: repository-fit
+name: intake
 description: >
   Verify and propose one target repository and plan directory when repository
-  identity is absent or ambiguous. Use for Repository Fit before Set Bearings.
-  Do not use after owner-confirmed fit, for parent-wide exploration, planning
-  decisions, product edits, role routing, or publication.
+  identity is absent or ambiguous. Use for Intake before Architectural
+  Alignment. Do not use after owner-confirmed fit, for parent-wide exploration,
+  planning decisions, product edits, role routing, or publication.
 ---
 
-# Repository Fit
+# Intake
 
-Fresh planning node. It returns evidence; the Router records the decision.
+Fresh planning node. It returns evidence; the Orchestrator records the decision.
+Intake handles input and repository selection.
 
 ## Inputs and match
 
-- **Inputs:** Journey goal, authorized candidate roots, visible prior decisions,
+- **Inputs:** Lifecycle goal, authorized candidate roots, visible prior decisions,
   repository rules, and discovery limits.
 - **Match:** target root, repository identity, or plan location is unresolved.
 - **Non-match:** the owner already named and confirmed the repository and plan.
@@ -27,7 +28,7 @@ Fresh planning node. It returns evidence; the Router records the decision.
    owner evidence with a typed finding.
 4. Propose exactly one repository and one plan-directory assumption with path
    evidence and a short reason.
-5. Return one owner confirmation question through the Router. A recommendation
+5. Return one owner confirmation question through the Orchestrator. A recommendation
    is not confirmation.
 
 ## Return and recovery
@@ -37,4 +38,4 @@ Return `FIT_PROPOSED`, `FIT_CONFIRMED`, `FIT_UNAVAILABLE`, `FIT_MALFORMED`, or
 Retry only from new evidence, at most three attempts.
 
 Never write files, walk unapproved parents, rank endless alternatives, or
-advance the Journey itself.
+advance the Lifecycle itself.

package/skills/integration-engineer/SKILL.md

@@ -2,39 +2,44 @@
 name: integration-engineer
 description: >
   Dual-session Integration Engineer for planning assembly strategy and
-  execution assembly of the exact integrated candidate. Use for Planning
-  Integration Engineer or Execution Integration Engineer. Do not
-  implement missing product behavior or self-certify.
+  execution-session system-level validation of the exact integrated candidate.
+  Use for the Integration Engineer planning session or execution session. Do
+  not implement missing product behavior or self-certify.
 ---
 
 # Integration Engineer
 
 Planning and execution sessions are separate because authority differs.
+The planning session owns assembly strategy. The execution session owns
+final system-level validation and integrated technical assessment.
 
 ## Inputs and match
 
 - **Inputs:** items/versions, compatibility, order, entry criteria,
-  configuration identity, authorized glue, interfaces.
-- **Match:** progressive assembly is required.
+  configuration identity, authorized glue, interfaces, approved outcome.
+- **Match:** progressive assembly is required, or Lifecycle-end execution
+  assessment is declared. Default execution cadence is `lifecycle`.
 - **Non-match:** product implementation, requirement rewrite, test
-  authorship.
+  authorship, Reviewer defect adjudication.
 
 ## Algorithm
 
-1. Planning Integration Engineer defines items/versions, compatibility,
+1. The planning session defines items/versions, compatibility,
    order, entry criteria, stubs, configuration identity, post-step V&V
    handoffs, anomaly/rollback/recovery, and the final integrated
    candidate after requirements, views, and design interfaces stabilize.
-2. Execution Integration Engineer confirms identities and readiness,
-   assembles approved elements, applies only authorized integration
-   glue, exercises interfaces, records anomalies or rollback, produces
-   the exact integrated candidate, and hands to Assurance Test Engineer.
+2. The execution session starts a fresh session, rejects author
+   ancestry, independently performs final system-level validation and
+   integrated technical assessment against the approved user-facing
+   outcome at Lifecycle completion by default or an explicit override.
+   Deterministic-verification receipts from this session are diagnostic
+   and do not self-certify the candidate.
 3. Missing Integration Engineering method skill is a typed capability
    gap, not invented behavior.
 
 ## Return and recovery
 
-Return `CANDIDATE_READY` or `OWNER_DECISION_REQUIRED` with verdict,
+Return `CANDIDATE_READY`, `GAPS`, or `OWNER_DECISION_REQUIRED` with verdict,
 candidate_ref, changed_paths, tests, findings, and blocker.
 
 Never implement missing product, revise requirements or design, weaken

package/skills/light-implementer/SKILL.md

@@ -14,9 +14,9 @@ command decides pass or fail, and nothing is decided in-session.
 
 ## Inputs and match
 
-- **Inputs:** the Crewmate packet contract (baseline, objective, exact write
+- **Inputs:** the Implementer packet contract (baseline, objective, exact write
   set, authority, commands, stop rule, return schema, visible wave receipt,
-  lineup identity from the recorded snapshot) for a slice whose
+  profile identity from the recorded snapshot) for a slice whose
   `work_class` is `light`.
 - **Match:** every criterion holds:
   1. Inputs are all named and present: paths, digests, UIDs, a runbook.
@@ -33,16 +33,17 @@ command decides pass or fail, and nothing is decided in-session.
 
 ## Algorithm
 
-1. Revalidate the checkout lease exactly as the Crewmate does. On mismatch
+1. Revalidate the checkout lease exactly as the Implementer does. On mismatch
    return `WAITING_ON` without writing.
 2. Do exactly what the packet states, inside the write set, and nothing else.
 3. Run the packet's verification command at the candidate revision. Record
-   exit status, output digest, and changed paths.
+   exit status, output digest, and changed paths. Any deterministic-verification
+   receipt is diagnostic only and never satisfies an assurance gate.
 4. If any step needs a choice the packet did not make, stop before writing
    further and return `NEEDS_MORE_EVIDENCE` with `reclassify: judgement`
    and the exact question. Never guess, never escalate silently.
 5. There is no in-wave repair loop. A failing command returns the typed
-   failure with its output; the Router decides.
+   failure with its output; the Orchestrator decides.
 
 ## Return and recovery
 

package/skills/onboard-bearing/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: onboard-bearing
+description: >
+  Guided first-run and later configuration of profiles.json. Use for
+  onboard-bearing, profile setup, or explicit configuration change. Do not
+  use to infer settings, store credentials, or write during ordinary
+  Lifecycles.
+---
+
+# onboard-bearing
+
+Reusable guided configuration. Inspects `profiles.json` when present. Asks
+one setting at a time. May recommend; never selects or writes without the
+user's explicit instruction. Preserves every unaddressed existing value.
+
+## Inputs and match
+
+- **Match:** first run, missing profile, explicit configuration change, or
+  `MIGRATION_REQUIRED` from a legacy lineup catalog.
+- **Non-match:** ordinary Lifecycle dispatch, silent repair of a valid profile.
+
+## Algorithm
+
+1. Resolve `<absolute home>/.agents/bearing-lite/profiles.json` per
+   `references/profiles.md`. Never read packaged bytes as user data. Never
+   search, merge, prefer, or fall back to `lineups.json`.
+2. If a user `lineups.json` exists, return `MIGRATION_REQUIRED`. Do not
+   consume it as live configuration. Migration validates the lineup, asks
+   which route to assign to Integration Engineer execution, writes a
+   semantically equivalent `profiles.json`, validates readback, then removes
+   `lineups.json`. Do not auto-assign Surveyor or any retired role.
+3. Ask settings one at a time with no preselected value: named role/session
+   routes and fallbacks, session enablement, development strategy,
+   planning review, assurance cadence, concurrency, clean-session, holds, and
+   optional Reverify. Declining Reverify or its download persists
+   `reverify.enabled: false` for that named profile.
+4. Write only explicit choices atomically. Validate Draft 2020-12 readback
+   against `schemas/profiles.schema.json`. Store no credentials.
+
+## Return and recovery
+
+Return `READY`, `MIGRATION_REQUIRED`, `no_named_profiles`, or
+`OWNER_DECISION_REQUIRED` with verdict, candidate_ref, changed_paths, tests,
+findings, and blocker.
+
+Never invent a setting, write the packaged catalog, or keep a lineup fallback.

package/skills/plan-integrator/SKILL.md

@@ -1,21 +1,21 @@
 ---
 name: plan-integrator
 description: >
-  Reconcile specialist outputs and generate implementation.json and
-  review.html. Use for Plan Integrator. Do not invent owner intent,
+  Reconcile specialist outputs and generate implementation.json and the
+  DoD Manifest input. Use for Plan Integrator. Do not invent owner intent,
   requirements, models, or V&V, or author V&V.
 ---
 
 # Plan Integrator
 
-Consumes stable specialist outputs, invokes Map the Route, cross-validates
-the five artifacts, and generates `implementation.json` and two-state
-`review.html`.
+Consumes stable specialist outputs, invokes Planning and Design, cross-validates
+the five artifacts, and generates `implementation.json` and
+`implementation.json.dod_manifest` without adding judgment.
 
 ## Inputs and match
 
 - **Inputs:** settled decisions, technical-plan, design.md, seit.json
-  drafts, lineup freeze, authority envelope.
+  drafts, profile freeze, authority envelope.
 - **Match:** specialist outputs are stable enough to reconcile.
 - **Non-match:** unresolved owner intent; V&V authorship.
 
@@ -23,19 +23,19 @@ the five artifacts, and generates `implementation.json` and two-state
 
 1. Cross-validate the five canonical artifacts. Copy design-lens names
    from design.md; never invent lens IDs.
-2. For `journey_type: specification`, default an Expedition wave to scaffold →
-   author from the gated register → Test Engineer verification cases → bind to the host
-   → readback of the bound revision and digest from the host → Park
-   Ranger with both named in the review request → owner decision. A deviation
-   is a planning-review finding.
-3. Generate `implementation.json` and `review.html` (`planning-review`,
-   then `final-closeout`) when inputs are stable.
+2. After Systems Modeler and Planning Test Engineer return, copy the
+   Integration Engineer planning anomaly, rollback, recovery, and V&V
+   handoffs and the bound proof cases mechanically.
+3. Generate `implementation.json` and the DoD Manifest projection
+   (`planning`, then append-only closeout) when inputs are stable.
 4. Classify every slice `work_class: light` or `judgement` with a
    `work_class_reason`, using the five criteria in `skills/light-implementer`.
    Light slices carry the Light Implementer role and at least one
    `command_id`; the freeze rejects any other light slice.
 5. Request a Planning Test Engineer delta after relevant decision,
-   requirement, or design changes. Do not author V&V.
+   requirement, or design changes. Do not author V&V. Copy selected
+   deterministic-verification backends from Planning Test Engineer;
+   never invent claims, methods, or Reverify selection.
 
 ## Return and recovery