# Bearing Lite

> Bearing Lite Router for Journeys. Not for ordinary work, assigned packets, implementation, or publication.

- Skill: `alphazede/bearing-lite` (Agent Skill, multi-file: 11 files)
- Install (CLI): `npx skillmds@latest add alphazede/bearing-lite`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alphazede/bearing-lite/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: alphazede (https://skillmd.com/u/alphazede)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alphazede/bearing-lite

---


The Router alone writes Journey planning state, owns owner conversation, and owns Expedition sequencing;
planning nodes return owner questions. Plugin hosts are partial; skill-copy is skills-only.

1. Say `Preparing this Journey.` Acquire or resume a generation-bound checkout lease before
   planning or dispatch. A live same-checkout competitor returns `WAITING_ON` with sanitized identity.
2. Resume the next incomplete stage in the same generation; refresh `candidate_revision`.
   Never replay accepted stages or duplicate dispatch. Invalid leases fail closed.
3. If `~/.agents/bearing-lite/default-role-lineup.md` is absent, create a
   proposed copy; never infer identity values. The recorded snapshot is authoritative for this Journey.
   Later edits to
   `~/.agents/bearing-lite/default-role-lineup.md` have no effect on it except through an
   explicit owner-confirmed dated visible amendment. Dispatch uses lineup identity from the recorded snapshot.
4. Run Repository Fit → Set Bearings → Gather Supplies; unresolved material intent blocks Map the Route.
5. Invoke Map the Route after settled intent. Do not ask for lineup or route
   before it; carry owner-supplied lineup and `review_cadence: at-end` as proposals.
   Follow `references/lineups.md` for catalog selection and save.
6. Enforce `references/review-policy.md`. Show one integrated
   approval-or-change gate for outcome, design, route, lineup, role states,
   reasoning, cadence, and plan. Record the approved Journey type and snapshot; regenerate changes.
   Never add a staged lineup or route-review gate.
   Dispatch only after approval.
7. Crewmate and Explorer may continue in-wave.
   Use the visible wave receipt and update implementation and review once per wave.

Return `READY`, `WAITING_ON`, `OWNER_DECISION_REQUIRED`, or `COMPLETE`.
`max_assurance_rounds` is 1 per declared phase or wave-end, not per Journey;
Direct route checks `assurance_rounds`, never
dispatch Navigator, and one review may authorize one repair. Verify repair
deterministically without another review; failed repair/scope change returns
`OWNER_DECISION_REQUIRED` naming the candidate and count. `COMPLETE` ends Bearing assurance.
Authorized deployment without reopening review.
Planning review is a separate pre-dispatch gate; it never consumes implementation
`required_assurance`, `assurance_rounds`, or `max_assurance_rounds`.
Release the lease once: release the checkout lease exactly once on `COMPLETE` or `CANCELLED`;
recovery needs explicit recorded generation increment.
Recovery cannot steal a live lease.
Selected or required capabilities activate. Unavailability of selected-or-required
capability is a typed capability gap, not success and not invented behavior.
Selected-only missing and required-only missing are typed gaps. Unselected
and unrequired absence remains inactive, not a global failure.
Never implement, self-assure, select models, or publish.