Configuration and onboarding
Run onboard-bearing after installation when you need a named profile. It asks one setting at a time, never selects or writes a value without an explicit instruction, and preserves unaddressed existing values.
What persists
Section titled “What persists”The only persistent user configuration is ~/.agents/bearing-lite/profiles.json. It can record named role and session routes, fallbacks, enablement, development strategy, planning review, assurance cadence, concurrency, clean-session behavior, holds, and optional Reverify.
Use an explicit onboarding conversation rather than an invented configuration file:
profile: deliverystrategy: single_implementerreview cadence: phaseclean session: enabledThese are example choices, not preselected defaults or executable JSON. onboard-bearing persists a value only after explicit direction.
planning_to_implementation_clean_session controls the handoff after the owner accepts the planning package. When enabled, the planning Orchestrator renders a fresh implementation-start handoff from the approved package. When disabled, the same Orchestrator continues from durable artifacts. An approved Lifecycle may freeze an override in implementation.json.
Use single_implementer when one Implementer should combine work. Use tdd when Test Implementer must write tests and approved fixtures before Product Implementer writes the product set. Cadence values are slice, phase, or lifecycle.
Optional components you must enable deliberately
Section titled “Optional components you must enable deliberately”Coordinator is available, not automatic: enable it only for proven-independent work in one wave, shared wave evidence, or aggregate repair ownership. A direct packet never dispatches Coordinator.
Review coverage assist is optional deterministic support. It records what is reviewable, excluded, and governed, but finds no defects and produces no verdict. Reverify is an optional third-party backend: Bearing Lite never bundles, downloads, installs, or invokes it; its bridge only shapes a request and receipt a caller provides.
First-run and migration recovery
Section titled “First-run and migration recovery”Validate the resulting profile readback. A missing user file returns no_named_profiles; do not copy a packaged catalog over it. A leftover lineups.json is not live configuration and returns MIGRATION_REQUIRED until onboarding validates the old lineup, asks for the Integration Engineer execution route, writes an equivalent profiles.json, validates readback, and removes the old file.