Lifecycle
The Bearing Delivery Lifecycle answers a simple question: how can AI-assisted repository work stay reviewable and bounded from request to evidence? It separates planning, owner authorization, implementation, assurance, review, integration assessment, and closeout.
The forward path
Section titled “The forward path”- Intake confirms one target repository and plan directory.
- Architectural Alignment maps the affected system from repository facts.
- Scope Definition settles material owner decisions.
- Planning and Design creates the technical plan, design,
seit.json,implementation.json, and Definition of Done Manifest together. - Owner authorization approves or changes that exact package.
- Bounded implementation executes approved slices and validation sets.
- Test Engineer assurance and Reviewer run independently at their declared cadence.
- Integration Engineer execution assesses the integrated result at its declared cadence.
- Closeout appends actual evidence.
When each boundary matters
Section titled “When each boundary matters”Planning happens before implementation because unresolved material intent blocks a trustworthy package. Bounded work starts only after the owner authorizes it. A declared assurance boundary runs once, allows one aggregated repair, and then closes deterministically; a candidate author never supplies its own independent assurance or review verdict.
Direct packets do not dispatch Coordinator. Coordinator is useful only for a one-wave need with proven-independent work, shared wave evidence, or aggregate repair ownership. The Orchestrator remains the parent controller and bookkeeper.
Failure is a stop, not a workaround
Section titled “Failure is a stop, not a workaround”If implementation discovery invalidates an approved scope, interface, security, acceptance, or authority claim, dependent work stops and returns to the owner. Diagrams and the Definition of Done Manifest explain state; neither grants execution, acceptance, release, or deployment authority.
Detailed process map
Section titled “Detailed process map”Use the retained public overview when you need the whole delivery path in one view: Work Intake → Lifecycle Planning → Owner Authorization Gate → Lifecycle Implementation → Completed Result and Evidence. Feedback returns requested changes to planning, keeps repair bounded within implementation, and sends completion findings to the responsible implementer. Release and deployment remain separate authority.
The full retained public diagram adds Planning, Implementation, and Systems Modeler Transfer Function panels.
The transfer-function panel is proposed architecture detail, not a released runtime capability; its text contracts remain authoritative.
Open full four-panel diagram ↗