alphazede/bearing-lite

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.

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.

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.

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.

Build the human-readable task graph when the outcome is approved but executable tasks are missing. Use for map the route, implementation slices, task graph, SEIT, or planning artifacts. Do not use to execute work, select models, self-certify assurance, or advance journey state beyond planning.

Expedition and multi-phase Navigator sequencing across dependency-connected waves, including gap correction and in-authority coverage expansion. Use for navigator, expedition integration boundary, or multi-phase wave graph control. Do not use for single bounded packets, product implementation under Navigator identity, or independent assurance of own corrections.

Review introduced defects on one exact candidate when required_assurance includes Park Ranger, the owner opts in, or a material integrated phase gate requires defect review. Use for park ranger, defect review, or introduced-bug adjudication. Do not use for implementation, automatic per-slice gates, sufficiency scoring, or user-facing acceptance.

Propose one target repository and plan-directory assumption when the target is absent or ambiguous. Use for repository fit, choose repo, or confirm workspace before Set Bearings. Do not use after fit is confirmed, for product edits, routing roles, or owner-only publication decisions.

Create or resume the bounded plan workspace and repository map when project context or current-state map is missing after fit. Use for set bearings, plan workspace, or repository map. Do not use before fit is confirmed, for owner decisions, design drafts, product edits, or risk-profile authoring.

Orchestrate bounded packets inside one Explorer-owned wave when at least two proven-independent lanes need one extra coordination level. Use for sub-explorer or in-wave lane coordination. Do not use as a second nesting level, for product implementation, multi-wave control, or assurance.

Compare user-facing behavior of a stable integrated candidate with the approved outcome at multi-packet phase, Expedition, Final Audit, or owner-selected acceptance boundaries. Use for surveyor, acceptance review, or outcome comparison. Do not use for implementation, per-packet sufficiency, introduced-defect triage as Park Ranger, or owner-only publication approval.

Trail Boss cross-wave coordination for concurrent Explorer-owned waves with shared-interface or dependency conflicts. Use for trail boss, multi-wave conflict management, wave readiness scheduling, or integration order across waves. Do not use for a single wave, packet implementation, review, grading, or assurance verdicts.

Independently check evidence sufficiency and optional explicit-rubric scoring for one exact candidate when required_assurance includes Validator, the owner opts in, a stable checkpoint needs scoring, or a phase gate requires it. Use for validator, sufficiency check, or rubric scoring. Do not use to edit the candidate, auto-run on every packet completion, or replace Park Ranger or Surveyor.