1. Initial fit review
LBAI reviews whether the project has a real responsibility admission problem: release uncertainty, high-stakes outputs, unclear evidence, disputed gates, or agent outputs that cannot safely enter operations.
Design partner operating model
E2C Private Alpha is a guided evaluation for selected high-responsibility AI-native teams. It is not self-serve SaaS, not production deployment, not legal or compliance certification, and not an unrestricted autonomous agent run.
Design Partner Path Depends on Core OS Maturity. E2C’s first commercial release builds the Core Responsibility OS runtime scaffold. Design partner engagements follow: Core OS runtime scaffold → operational capability absorption → application responsibility chain → client domain responsibility instance. Private Alpha engagements remain guided, bounded, and selected. E2C does not offer arbitrary repo ingestion or unrestricted autonomous review at this stage.
2. Confidentiality and sharing path
Before any sensitive repo, customer data, internal policy, or proprietary artifact is shared, LBAI establishes an appropriate out-of-band confidentiality and artifact-sharing process.
3. Bounded project scope
The engagement starts with one bounded AI-native project, repo, domain workflow, or release-readiness problem.
4. Evidence package intake
The design partner prepares project context, prior gate failures, policies, workflows, risk boundaries, human review notes, test results, or other evidence.
5. Run mode selection
LBAI and the design partner decide whether the first run is Diagnostic, Standard Admission, or Deep Admission.
6. Responsibility artifact construction
E2C converts admitted evidence into source-bound responsibility artifacts and state transitions.
7. Validation and authorization review
E2C separates construction, validation, and authorization so generated work does not automatically become release-ready.
8. Release / hold / block readiness package
The design partner receives an auditable readiness package showing what was admitted, what remains unresolved, and whether the scoped system is Release, Hold, or Block.
9. Feedback and follow-up
The design partner can provide additional evidence, authorize continuation, or use the result to decide whether to move deeper into E2C.