@alphazede/bearing-lite 0.2.2 → 1.0.0

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

@@ -1,21 +1,28 @@
 # Assurance budget policy
 
-Decision source: `OWNER-EMV-REVIEW-CADENCE-UNIFICATION-001` through
-`ROUTER-EMV-CADENCE-IMPLEMENTATION-001`.
+Decision source: `DEC-BDL-007`, `DEC-BDL-030`, `DEC-BDL-047`, `DES-BDL-007`.
 
-The implementation assurance budget is scoped to each **declared phase or
-wave**, not to the Journey and not to a slice. Automatic review is dispatched
-at the end of each declared phase or wave. `hooks/assurance-budget.cjs` is the
-exact runtime mirror of the block below; the block is authoritative.
+Cadence values are `slice`, `phase`, or `lifecycle`. Defaults are `phase`
+for Test Engineer assurance, `phase` for Reviewer, and `lifecycle` for
+Integration Engineer execution. A declared boundary runs each enabled
+session once, allows one aggregated repair, then uses deterministic closure
+without automatic rereview. `hooks/assurance-budget.cjs` is the exact
+runtime mirror of the block below; the block is authoritative.
 
 ```json
 {
-  "budget_scope": "per_declared_phase_or_wave",
+  "budget_scope": "per_declared_cadence_unit",
+  "cadence_values": ["slice", "phase", "lifecycle"],
+  "default_cadence": {
+    "test_engineer.assurance": "phase",
+    "reviewer": "phase",
+    "integration_engineer.execution": "lifecycle"
+  },
   "review_rounds": 1,
   "aggregated_repairs_max": 1,
   "post_repair_gate": "deterministic_PASS",
   "automatic_phase_or_wave_end_review": "required",
-  "automatic_per_slice_review": "prohibited",
+  "automatic_per_slice_review": "cadence_gated",
   "post_repair_rereview": "prohibited",
   "automatic_rereview_of_same_unit": "prohibited",
   "budget_reset_on_candidate_change": false,
@@ -31,21 +38,29 @@ exact runtime mirror of the block below; the block is authoritative.
 
 ## Unit identity
 
-Budget identity is `journey + unit_kind + unit_id`. The unit id is resolved
-from the frozen declaration: `waves[].id`, else `phases[].phaseId`, else the
-single `direct` sentinel when neither is declared. A unit id absent from the
+Budget identity is `lifecycle + unit_kind + unit_id`. The unit id is resolved
+from the frozen declaration according to the requested cadence unit kind:
+`slices[].id` for slice, `waves[].id` else `phases[].phaseId` for phase or
+wave, `journey_settings.lifecycle_id` for lifecycle, else the single `direct`
+sentinel when neither waves nor phases are declared. A unit id absent from the
 frozen declaration fails closed as `undeclared_review_unit`; renaming a
 declared unit's display name never mints a fresh budget.
 
+Slice-scope review is allowed only when the frozen cadence for that session
+is `slice`. Default `phase` cadence rejects automatic per-slice review.
+Lifecycle-end wording where `phase` cadence applies is a contract failure.
+
 The budget key
 records no route, provider, model, harness, account, or agent identity.
-Candidate revision, lease generation, assigned role, session, and
-slice id are likewise never key components, and none of them lowers a spent
-count.
+Candidate revision, lease generation, assigned role, session, and a non-unit
+`slice_id` field are likewise never key components, and none of them lowers a
+spent count. A declared slice or lifecycle unit retains its spent budget
+under the same `unit_kind` + `unit_id` key.
 
 ## Spending the budget
 
-- One review round per declared phase or wave. A second round on the same unit
+- One review round per declared cadence unit (slice, phase or wave, or
+  lifecycle). A second round on the same unit
   halts with `assurance_round_limit`.
 - A repairable verdict permits at most one aggregate repair. A second repair
   halts with `assurance_repair_limit`.
@@ -56,7 +71,8 @@ count.
   `review_after_repair` both require an owner amendment.
 - A transport receipt of `WAITING_ON` or `UNAVAILABLE` is not a spent round; it
   returns `NEEDS_MORE_EVIDENCE`.
-- The next distinct declared phase or wave carries its own budget.
+- The next distinct declared phase or wave carries its own budget. Declared
+  slice and lifecycle units likewise retain their spent counts.
 
 ## Planning review stays separate
 

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

@@ -1,112 +1,9 @@
-# Named lineup catalog
+# Obsolete lineup catalog
 
-Candidate procedure for the user-owned JSON catalog. It is not a staged
-lineup or route-review gate. Selection is not an authority grant.
+`lineups.json` is not live Bearing configuration. Use
+`references/profiles.md` and `~/.agents/bearing-lite/profiles.json`.
 
-## Location
-
-The live user catalog is exactly one file:
-
-`<absolute home>/.agents/bearing-lite/lineups.json`
-
-Resolve `<absolute home>` as a nonempty absolute `HOME`, else a nonempty
-absolute `USERPROFILE` on its platform; otherwise fail closed with
-`home_unresolved`. Do not use cwd, the package root, XDG, a relative
-`lineups.json`, or a second search root.
-
-The packaged catalog is package-root `lineups.json`. Never read it as user
-data. Never write the packaged catalog, including resolved symlink aliases
-of that file.
-
-Missing user file means no named profiles. Do not auto-create the live
-catalog. An empty `lineups` object is valid and is not an error. A
-malformed unused catalog cannot override explicit inline owner choices.
-
-## Configurable roles
-
-Catalog entries assign Explorer, Crewmate, Light Implementer, Test Engineer,
-Scribe, Plan Integrator, Systems Modeler, Integration Engineer, Requirements
-Engineer, Park Ranger, and Surveyor. The Light Implementer takes only slices
-whose `work_class` is `light` (criteria in `skills/light-implementer`); it
-has its own primary and fallbacks, usually a lighter and cheaper route. Navigator and Validator are not lineup roles;
-existing plans that still assign them use the compatibility diagnostics and
-treat the assignment as unused. Never fill agent, model, or reasoning values
-on the user's behalf. `review_cadence` is `at-end`.
-
-The Router is not a configurable role: it is whatever session is running
-planning. The Journey snapshot records the observed Router identity
-(harness, model, reasoning at that time). A catalog or snapshot entry with
-`role: Router` is ignored with the typed note `router_row_ignored`; it is
-never a deviation.
-
-Only verified primary unavailability activates its approved fallback. If
-both are unavailable, return `OWNER_DECISION_REQUIRED`.
-Activation within the frozen ordered fallbacks is a dated execution receipt,
-not a lineup amendment or a new owner approval. Verify the approved activation
-condition and remaining eligible routes before escalating exhaustion. A new
-identity or changed fallback condition requires an owner amendment; follow
-`owner-stops.md` for classification and batching.
-
-This catalog is the single lineup source. A legacy
-`~/.agents/bearing-lite/default-role-lineup.md` is never read or created;
-when one is present it is ignored with the typed note
-`legacy_lineup_md_ignored`. A missing catalog returns the typed outcome
-`no_named_profiles` and an inline-selection prompt.
-
-## Validity
-
-Named selection and save require a valid catalog. Bind
-`schemas/lineups.schema.json` Draft 2020-12 validation before named
-selection or save. That schema is the validation document, not a second
-search root for user data. Do not add a runtime catalog library.
-
-On load and on save, inspect raw object members first. Reject duplicate
-raw JSON keys; do not silently collapse. Then parse and apply Draft 2020-12
-validation against package-root `schemas/lineups.schema.json`. Fail closed
-as follows even when the schema cannot express the check:
-
-- Reject duplicate role assignments within each phase.
-- Reject ASCII case-fold collisions on both load and save. Do not trim
-  or case-fold names.
-- Defaults keys must resolve exactly. Unresolved defaults fail closed.
-- Invalid structure or name fails closed on both load and save.
-
-Refuse named selection or save on any of those failures. Do not invent a
-fallback profile and do not read packaged bytes as user data.
-
-## Selection
-
-Explicit inline owner choices require no catalog lookup and no extra
-confirmation. Consume them as already explicit.
-
-A named choice needs a valid catalog and an exact selected key. Do not trim
-or case-fold the name. Independent planning and implementation selections
-remain separate; the owner may pick two names, one name twice, or inline on
-either side.
-
-Optional user `defaults.planning` and `defaults.implementation` are
-recommendations requiring selection or confirmation. They are never a silent
-grant and not an authority grant. Do not apply them without that
-confirmation. Do not invent a packaged default.
-
-Copy selected entries into the Journey snapshot as a frozen snapshot copy.
-Preserve fallback array order. Bind a SHA-256 configuration digest of that
-frozen snapshot copy. Digest that copy only: selected entries with fallback
-order and selection sources. Exclude N/K/C, review cadence, route, and
-authority. Canonical JSON: UTF-8, sort_keys, compact separators.
-Later catalog edits do not mutate the frozen snapshot copy or its digest.
-
-## Save
-
-Save only on explicit owner request. Never save this Journey as a side
-effect of selection, freeze, or routing.
-
-Create versus replace: if replace is already explicit, do not ask again;
-otherwise preview the selected-entry replacement and confirm. Create must
-not overwrite an existing exact key. Replace updates only that key.
-
-Preserve unrelated valid keys and defaults. Refuse changed-input overwrite.
-Use a safe atomic update (sibling temp file, then rename).
-
-Do not write N/K/C, review cadence, route, or authority into catalog
-entries.
+Runtime never searches, merges, prefers, or falls back to `lineups.json`.
+A leftover user lineup returns `MIGRATION_REQUIRED` until onboard-bearing
+migrates it. Packaged `lineups.json` and `default-role-lineup.md` are
+removed by the S1L mechanical migration. Selection is not an authority grant.

package/skills/bearing-lite/references/owner-stops.md

@@ -5,10 +5,10 @@ Before asking, identify the unresolved decision, affected slices, evidence,
 and why the current policy or authority does not answer it. Never invent an
 extra role, review gate, approval checkpoint, or scope to resolve uncertainty.
 
-| Class | Decision | Router behavior |
+| Class | Decision | Orchestrator behavior |
 | --- | --- | --- |
 | A | Existing policy | Apply the cited rule and record a dated execution receipt. A real policy conflict is a C boundary decision. |
-| B | Approved fallback | Verify unavailability under the frozen fallback condition; activate the next eligible approved route and record evidence. Changing the lineup or fallback condition is C. |
+| B | Approved fallback | Verify unavailability under the frozen fallback condition; activate the next eligible approved route and record evidence. Changing the profile or fallback condition is C. |
 | C | Bound, scope, or policy conflict | Ask for the smallest amendment when it blocks ready work. Never reset a spent bound. |
 | D | Continue approved work | Use the effective continuation grant; never ask again while its conditions hold. Missing or expired authority is F. |
 | E | Integrated plan approval | Present the package once for approval or change; execution waits for explicit approval. |
@@ -19,17 +19,17 @@ expiry, and owner-hold checks. Missing evidence is `NEEDS_MORE_EVIDENCE`, not
 permission and not automatically an owner question. Recover discoverable
 evidence first; escalate a real unresolved boundary as C or F. Fallback
 activation is an execution receipt, not an authority amendment. Only the
-owner changes the frozen lineup or grants authority.
+owner changes the frozen profile or grants authority.
 
 ## Approval and authority
 
-Map the Route includes `authority.json.continuation` in the integrated gate:
+Planning and Design includes `authority.json.continuation` in the integrated gate:
 `granted`, `owner_decision_id`, named `exclusions`, and `expires_at` (UTC or
 null for event-based expiry). The surrounding envelope retains allowed and
 prohibited actions/paths, role grants, approval receipt, and nonempty
 `expiry_conditions`. Record explicit approval against the exact package;
 the continuation decision ID must occur in `granting_owner_decisions`.
-No grant is inferred from silence, a lineup selection, or passing checks.
+No grant is inferred from silence, a profile selection, or passing checks.
 
 Always exclude scope change, budget exhaustion, owner holds, and owner-only
 actions from the continuation grant. A separate explicit action grant can
@@ -41,9 +41,9 @@ provides no standing continuation grant. Do not manufacture a retroactive one.
 For first approval show outcome, scope/exclusions, role responsibilities,
 route, bounds, risks, open decisions and proof coverage in a concise summary.
 For revisions show changed requirements, design, proof cases, slices,
-lineup, authority and bounds against the last owner-reviewed package, citing
+profile, authority and bounds against the last owner-reviewed package, citing
 both revisions/digests. Explain invalidated approvals and unresolved decisions.
-Keep the complete frozen `review.html` accessible in both cases; a diff or
+Keep the complete frozen DoD Manifest accessible in both cases; a diff or
 freeze PASS is neither approval nor proof of semantic completeness. An
 unchanged package does not need reapproval. A changed package returns to the
 same gate, never an extra gate.
@@ -58,7 +58,7 @@ receipts, not fabricated questions. Required fields are defined by
 `schemas/journey.schema.json` and checked by the metrics helper.
 
 Queue nonblocking questions until wave end and present one batch with the
-wave receipt. Queue nonblocking owner-only closeout actions until Journey
+wave receipt. Queue nonblocking owner-only closeout actions until Lifecycle
 end. Required credentials, publication prerequisites, or other owner-only
 dependencies surface immediately when they block ready work. Do not defer
 safety/integrity intervention or an explicit owner stop. Each actual
@@ -78,7 +78,7 @@ Disjoint writes alone do not prove independence: check shared runtime,
 resources, integration order, and read/write dependencies. `parallel_safe`
 is evidence to inspect, not permission. Respect host concurrency limits and
 never dispatch completed or already-running work again. Keep dependent work
-pending. Owner holds apply to their stated scope, including the whole Journey
+pending. Owner holds apply to their stated scope, including the whole Lifecycle
 when so directed; they cannot be bypassed by calling work independent.
 
 ## Deterministic checks and measurement
@@ -87,7 +87,7 @@ Before a proposed stop, run `hooks/transition-order.cjs` with
 `action_kind: owner_stop_check` and `owner_stop` containing `class`,
 `blocking`, `evidence_ref`, `resolution_ref`, `authority`, `checked_at`,
 and `checks`. Checks are explicit booleans: `scope`, `budget`, `exclusions`,
-`expiry`, `owner_hold`, plus `policy` for A or `fallback` for B. Router must
+`expiry`, `owner_hold`, plus `policy` for A or `fallback` for B. Orchestrator must
 verify them against the actual frozen inputs; the helper does not authenticate
 receipts or interpret arbitrary path globs or expiry prose. C/E/F need the
 class, evidence reference and blocking flag; return ASK or QUEUE. A/B/D
@@ -96,13 +96,13 @@ procedural transition adapter, not a new registered host event, permission
 grant, scheduler, or security boundary. Skills-only hosts execute the same
 checklist and disclose unavailable deterministic checks.
 
-New Journeys set `owner_wait_tracking: true` and initialize
+New Lifecycles set `owner_wait_tracking: true` and initialize
 `owner_blocked_intervals: []`. Record intervals only while no authorized ready
 work can progress specifically because of unanswered owner questions. Each
 interval lists their `decision_ids`, `started_at`, and nullable `ended_at`.
 End the interval as soon as work can progress, even if some questions remain
 unanswered. Do not treat every dependency wait, off-hours gap, or commit gap as
-owner-blocked time. Never backfill unknown times. Legacy Journeys without
+owner-blocked time. Never backfill unknown times. Legacy Lifecycles without
 tracking report `unavailable`, not zero waiting.
 
 Run `node <plugin root>/hooks/owner-stops.cjs <journey.json> <as-of-UTC>` at
@@ -117,6 +117,6 @@ no telemetry or network transmission. Closeout renders these metrics and
 coverage limitations; it must not claim measured savings from legacy gaps.
 
 Operational target after settled scope: zero unnecessary stops per wave;
-one integrated approval batch and one closeout batch per unchanged Journey
+one integrated approval batch and one closeout batch per unchanged Lifecycle
 when closeout needs owner authority. Exceptions are recorded, never suppressed
 to hit a quota. Forecast savings only from verified classified observations.

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

@@ -6,18 +6,17 @@ 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) | technical-plan, design.md, seit.json, implementation.json, two-state review.html |
-| 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; split test-writing versus product |
+| Bearing Orchestrator | [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 |
+| Intake | [Kiro steering](https://kiro.dev/docs/steering/) | verified workspace and explicit global/workspace scope |
+| Architectural Alignment | [Kiro steering](https://kiro.dev/docs/steering/) | durable human-readable workspace context |
+| Scope Definition | [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 |
+| Planning and Design | [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) | technical-plan, design.md, seit.json, implementation.json, DoD Manifest |
+| Coordinator | LangChain subagents | bounded worker dispatch, proven-independent lane coordination, and result integration |
+| Implementer | Spec Kit implement step | bounded execution after approved planning; split test-writing versus product |
 | Scribe | event side lane | transcribes; cannot activate authority |
-| Plan Integrator | Spec Kit tasks gate | reconciles five artifacts; generates implementation.json and review.html |
+| Plan Integrator | Spec Kit tasks gate | reconciles five artifacts; generates implementation.json and DoD Manifest input |
 | Systems Modeler | MBSE view selection | after requirements; before design finalization |
-| Integration Engineer | assembly method | dual planning and execution sessions |
+| Integration Engineer | assembly method | dual planning and execution sessions; execution replaces Surveyor |
 | Test Engineer | Spec Kit gate | Planning and Assurance sessions; Validator absent from active roles |
-| Park Ranger | LangChain reviewer subagent | independent defect review with a typed return |
-| Surveyor | Spec Kit review gate | outcome comparison before completion |
+| Reviewer | LangChain reviewer subagent | independent defect review with a typed return |
+| onboard-bearing | first-run setup | explicit one-setting-at-a-time profile writes; no credentials |

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

@@ -0,0 +1,149 @@
+# Named profile catalog
+
+Candidate procedure for the user-owned JSON catalog. It is not a staged
+profile or route-review gate. Selection is not an authority grant.
+
+## Location
+
+The live user catalog is exactly one file:
+
+`<absolute home>/.agents/bearing-lite/profiles.json`
+
+Resolve `<absolute home>` as a nonempty absolute `HOME`, else a nonempty
+absolute `USERPROFILE` on its platform; otherwise fail closed with
+`home_unresolved`. Do not use cwd, the package root, XDG, a relative
+`profiles.json`, or a second search root.
+
+The packaged catalog is package-root `profiles.json`. Never read it as user
+data. Never write the packaged catalog, including resolved symlink aliases
+of that file.
+
+Missing user file means no named profiles. Do not auto-create the live
+catalog. An empty `profiles` object is valid and is not an error. A
+malformed unused catalog cannot override explicit inline owner choices.
+
+Runtime and skills never search, merge, prefer, or fall back to
+`lineups.json`. A leftover user `lineups.json` is not live configuration;
+return `MIGRATION_REQUIRED` until explicit migration validates it, writes
+and validates a semantically equivalent `profiles.json`, and removes
+`lineups.json`.
+
+## Configurable roles
+
+Catalog entries assign nested role/session routes for Implementer, Light
+Implementer, Coordinator, Reviewer, Test Engineer, Scribe, Plan Integrator,
+Systems Modeler, Integration Engineer, and Requirements Engineer. Systems
+Modeler has a planning session; Test Engineer has planning and assurance
+sessions; Integration Engineer has planning and execution sessions. Each
+session can be enabled or disabled. Cadence keys attach to
+`test_engineer.assurance`, `reviewer`, and `integration_engineer.execution`
+with values `slice`, `phase`, or `lifecycle`. Defaults are `phase`, `phase`,
+and `lifecycle`. The Light Implementer takes only slices whose `work_class`
+is `light` (criteria in `skills/light-implementer`); it has its own primary
+and fallbacks, usually a lighter and cheaper route. Surveyor, Explorer,
+Crewmate, Navigator, Park Ranger, and Validator are not profile roles;
+existing plans that still assign them use the compatibility diagnostics and
+treat the assignment as unused. Never fill agent, model, or reasoning values
+on the user's behalf.
+
+The Orchestrator is not a configurable role: it is whatever session is running
+planning. The Lifecycle snapshot records the observed Orchestrator identity
+(harness, model, reasoning at that time). A catalog or snapshot entry with
+`role: Orchestrator` or `role: Router` is ignored with the typed note
+`router_row_ignored`; it is never a deviation.
+
+Only verified primary unavailability activates its approved fallback. If
+both are unavailable, return `OWNER_DECISION_REQUIRED`.
+Activation within the frozen ordered fallbacks is a dated execution receipt,
+not a profile amendment or a new owner approval. Verify the approved activation
+condition and remaining eligible routes before escalating exhaustion. A new
+identity or changed fallback condition requires an owner amendment; follow
+`owner-stops.md` for classification and batching.
+
+This catalog is the single profile source. A legacy
+`~/.agents/bearing-lite/default-role-lineup.md` is never read or created.
+A missing catalog returns the typed outcome `no_named_profiles` and an
+inline-selection prompt. A leftover
+`~/.agents/bearing-lite/lineups.json` is ignored as live data with
+`MIGRATION_REQUIRED`.
+
+## Validity
+
+Named selection and save require a valid catalog. Bind
+`schemas/profiles.schema.json` Draft 2020-12 validation before named
+selection or save. That schema is the validation document, not a second
+search root for user data. Do not add a runtime catalog library.
+
+On load and on save, inspect raw object members first. Reject duplicate
+raw JSON keys; do not silently collapse. Then parse and apply Draft 2020-12
+validation against package-root `schemas/profiles.schema.json`. Fail closed
+as follows even when the schema cannot express the check:
+
+- Reject duplicate role assignments within each phase or session.
+- Reject ASCII case-fold collisions on both load and save. Do not trim
+  or case-fold names.
+- Defaults keys must resolve exactly. Unresolved defaults fail closed.
+- Invalid structure or name fails closed on both load and save.
+- Reject active Surveyor, Explorer, Crewmate, Navigator, Park Ranger, or
+  Validator role keys.
+
+Refuse named selection or save on any of those failures. Do not invent a
+fallback profile and do not read packaged bytes as user data.
+
+## Selection
+
+Explicit inline owner choices require no catalog lookup and no extra
+confirmation. Consume them as already explicit.
+
+A named choice needs a valid catalog and an exact selected key. Do not trim
+or case-fold the name. Independent planning and implementation selections
+remain separate; the owner may pick two names, one name twice, or inline on
+either side.
+
+Optional user `defaults.planning` and `defaults.implementation` are
+recommendations requiring selection or confirmation. They are never a silent
+grant and not an authority grant. Do not apply them without that
+confirmation. Do not invent a packaged default.
+
+Copy selected entries into the Lifecycle snapshot as a frozen snapshot copy.
+Preserve fallback array order. Bind a SHA-256 configuration digest of that
+frozen snapshot copy. Digest that copy only: selected entries with fallback
+order and selection sources. Exclude N/K/C, review cadence, route, and
+authority. Canonical JSON: UTF-8, sort_keys, compact separators.
+Later catalog edits do not mutate the frozen snapshot copy or its digest.
+
+## Save
+
+Save only on explicit owner request. Never save this Lifecycle as a side
+effect of selection, freeze, or routing.
+
+Create versus replace: if replace is already explicit, do not ask again;
+otherwise preview the selected-entry replacement and confirm. Create must
+not overwrite an existing exact key. Replace updates only that key.
+
+Preserve unrelated valid keys and defaults. Refuse changed-input overwrite.
+Use a safe atomic update (sibling temp file, then rename).
+
+Do not write N/K/C, review cadence, route, or authority into catalog
+entries.
+
+## Development strategy, cadence, concurrency, clean-session
+
+`development_strategy.mode` is `single_implementer` (speed default) or
+`tdd`. `tdd` orders Test Implementer before Product Implementer for a
+behavior-changing slice. Independent dependency-ready slices may run
+concurrently when write sets and mutable resources do not overlap.
+
+`planning_to_implementation_clean_session` is an explicit boolean with no
+preselected value. An approved Lifecycle may freeze an override in
+`implementation.json`.
+
+## Migration
+
+Migration preserves meaning from `planned_planning_assignments` and
+`implementation_assignments`. Map Crewmate to Implementer, Explorer to
+Coordinator, Park Ranger to Reviewer, Light Implementer unchanged, Test
+Engineer planning-phase rows to `test_engineer.planning` and
+implementation-phase rows to `test_engineer.assurance`. Do not auto-assign
+Integration Engineer execution from Surveyor; onboard-bearing asks which
+route to assign. Validate the new profile, then remove `lineups.json`.

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

@@ -0,0 +1,30 @@
+# Resume and liveness
+
+Resume reads `journey.json`, `workspace.md`, the active role contract, and
+the current task. It trusts accepted stages and confirmed decisions unless a
+bounded identity or drift check fails. It never adds a watchdog daemon,
+heartbeat service, global timeout, or model polling, and it never replays
+accepted planning.
+
+## Preflight
+
+Before resuming or dispatching a fallback, Orchestrator performs one
+host-native liveness check when that surface exists:
+
+| Class | Meaning | Action |
+| --- | --- | --- |
+| `RUNNING` | The dispatched session or process is still active | Never duplicate |
+| `COMPLETED` | Durable evidence shows the task finished | Advance only from that evidence |
+| `INACTIVE` / `EXITED` | The session is gone | Resume from last durable state with an approved fallback |
+| `UNKNOWN` | The host exposes no reliable status | Automatic orchestration returns `WAITING_ON`. Explicit owner-requested resume may replace the agent |
+
+Wait/status reliability varies by host and route. Host-native status checks
+are recommended when available. Missing expensive models or wrappers do not
+make a route ineligible.
+
+## Continuation
+
+A resumed or fallback agent does not receive raw conversation history. It
+continues the same pass and budget from durable artifacts. Confirmed owner
+decisions stay confirmed. A changed envelope, conflicting writer, new
+authority, or explicit owner choice starts fresh.

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

@@ -8,8 +8,8 @@ harness, account, or agent identity.
 
 ```json
 {
-  "reviewer_slots_min": 2,
-  "reviewer_slots_max": 2,
+  "reviewer_slots_min": 1,
+  "reviewer_slots_max": 1,
   "independence_required": true,
   "isolated_findings_until_aggregation": true,
   "candidate_fields": ["candidate_ref", "candidate_revision", "candidate_digest"],
@@ -23,7 +23,7 @@ harness, account, or agent identity.
 }
 ```
 
-Map the Route writes the separate Journey binding in the approved lineup
+Planning and Design writes the separate Lifecycle binding in the approved profile
 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

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

@@ -1,21 +1,21 @@
 flowchart TD
-    O[Owner Authority] <--> R[Stateful Bearing Lite Router]
+    O[Owner Authority] <--> R[Stateful Bearing Lite Orchestrator]
     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 -->|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
+    P -->|Intake| IN[Fresh Intake]
+    P -->|Architectural Alignment| AA[Fresh Architectural Alignment]
+    P -->|Scope Definition| SD[Fresh Scope Definition]
+    P -->|Planning and Design| PD[Fresh Planning and Design]
+    IN & AA & SD -->|typed return| R
+    R --> PD
+    PD -->|five artifacts with proposed route, profile, role states, reasoning, cadence| I{One integrated owner review}
+    I -->|change| PD
+    I -->|approve one packet| C[Implementer may continue in-wave]
+    I -->|approve one wave| E[Coordinator may continue in-wave]
+    I -->|approve Lifecycle: Orchestrator sequences waves| E
     E --> C
     C --> A{Declared phase or wave end candidate?}
     A -->|Assurance Test Engineer declared| V[Fresh Assurance Test Engineer]
-    A -->|Park Ranger declared| PK[Fresh Park Ranger]
-    A -->|Surveyor declared| S[Fresh Surveyor]
+    A -->|Reviewer declared| PK[Fresh Reviewer]
+    A -->|Integration Engineer execution declared| S[Fresh Integration Engineer execution]
     A -->|not yet| E
     V & PK & S -->|compact receipt| R

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`.