Roles and sessions
Bearing Lite uses stable role identities across planning, implementation, and assurance sessions. Fresh independent assurance keeps an agent that writes a candidate from also certifying it.
Planning roles
Section titled “Planning roles”| Role | When it participates | Responsibility |
|---|---|---|
| Orchestrator | Planning control | Owner conversation, lease, sequencing, and direct-packet bookkeeping; observed, not selected. |
| Intake | Before planning | Confirms repository and plan directory. |
| Architectural Alignment | Before scope | Maps relevant existing architecture. |
| Scope Definition | Until intent settles | Resolves material owner decisions one at a time. |
| Planning and Design | After intent settles | Creates the five-artifact package. |
| Requirements Engineer | When a register applies | Runs the requirement quality gate. |
| Systems Modeler | After requirements | Selects a modeling mode before design finalization. |
| Plan Integrator | After specialist decisions | Assembles agreed outputs mechanically. |
| Scribe | Planning and execution | Transcribes events; cannot activate authority. |
Implementation and assurance roles
Section titled “Implementation and assurance roles”| Role | When it participates | Responsibility |
|---|---|---|
| Test Implementer | tdd before product work |
Writes tests and approved fixtures only. |
| Product Implementer | tdd after tests |
Writes the product set; neither implementer self-certifies. |
| Implementer | single_implementer |
Combines product and test work under one bounded packet. |
| Coordinator | Proven-independent one-wave work only | Continues lanes without nesting; never dispatches on a direct packet. |
| Light Implementer | Mechanical slices | Executes work_class: light only. |
| Test Engineer | Planning and assurance | Authors prospective verification, then independently assesses the exact candidate. |
| Reviewer | Declared review cadence | Independently finds and adjudicates defects. |
| Integration Engineer | Planning and execution | Plans assembly, then assesses the integrated result. |
Owner Authority is always human-only. onboard-bearing is a configuration skill, not a role route: it asks for one setting at a time and writes only explicit choices.
Why roles use separate sessions
Section titled “Why roles use separate sessions”Separate sessions keep authorship and independent judgment apart when role authority differs. In particular, a fresh Test Engineer assurance session reruns required claims against the exact stable candidate, so the agent that produced a candidate does not certify it.