alphazede/bearing-lite

Create or resume the visible Lifecycle workspace and bounded repository map after Intake is confirmed. Use for Architectural Alignment or stale project context. Do not use before fit, for owner decisions, design, implementation, hidden state, or deleting historical plans.

Bearing Lite Orchestrator for Lifecycles. Not for ordinary work, assigned packets, implementation, or publication.

Own one approved execution wave, continuing bounded packets when the 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.

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

Verify and propose one target repository and plan directory when repository 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.

Dual-session Integration Engineer for planning assembly strategy and 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.

Execute one approved light slice exactly as its packet states, verified by the packet's deterministic command. Use for Light Implementer, light, mechanical, scaffold, bind, assemble, regenerate, or runbook packets. Do not use for judgement work, authoring, repair, review, or any decision.

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.

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.

Create or resume Bearing's complete five-artifact planning package after material decisions are settled. Use for Planning and Design or missing planning artifacts. Do not use to implement, select models, self-approve, or bypass the single integrated owner review.

Write a bounded execution prompt for another agent.

One Requirements Engineer role, planning stage only. Use for the requirement register quality gate after Scope Definition and before the Systems Modeler finalizes mappings. Do not use inside a Lifecycle wave, or for V&V, SysML modeling, implementation, defect review, or publication.

Independently review one exact stable candidate for introduced actionable defects in a fresh session at the configured cadence boundary. Use for Reviewer, code review, or defect adjudication. Do not use for implementation, automatic review, evidence scoring, user acceptance, author self-review, or unconfigured slice/round boundaries.

Relentlessly resolve material owner decisions for a Bearing Lifecycle, one dependency-ordered question at a time, until shared understanding is explicit. Use for Scope Definition or unresolved plan intent, not for discoverable repository facts, design drafting, implementation, or settled decisions.

Transcribe Lifecycle decisions, authority events, ledger snapshots, and profile selections as an event side lane. Use for Scribe. Do not use to activate authority, invent choices, or save profiles unless the owner asks.

Select modeling mode and attach view metadata after Requirements Engineer work and before design finalization. Use for Systems Modeler planning session. Do not finalize requirement mappings against unstable requirements.

One Test Engineer role with Planning and Assurance sessions. Use for Planning Test Engineer, Assurance Test Engineer, SEIT authorship, or declared cadence-boundary V&V. Do not use for implementation, defect review, user acceptance, or unconfigured slice/round boundaries.