Documentation
Architecture 2026, Core OS runtime release, continuous loop, micro-release loop, design partner path, and current public boundary.
Documentation hub →Support & community
Documentation, design-partner intake, investor inquiries, and builder resources for teams entering E2C through Core OS maturity and a controlled, bounded path.
Design partner path
Design partner engagements are downstream of Core OS. Before applying, review how engagement works and what not to submit through this public site.
Operating model → Data & security boundary →Request Private Alpha access
E2C Private Alpha is curated for institutional investors and selected design partners. Please indicate whether you are requesting:
- Design partner access — bounded project evaluation after Core OS maturity
- Investor materials — Core E2C OS runtime release — curated diligence shared out of band
- Strategic partnership
- Press / media
- General inquiry
For investor inquiries, curated materials may include:
- Architecture 2026 (two environments + product stack)
- Core E2C OS runtime release narrative
- Continuous responsibility-guided generation loop
- Frontier Models × E2C
- Capability absorption and micro-release doctrine
- Responsibility compounding / moat
- Design-partner path and non-goals
- Data room materials shared out of band
Start with the public Investors overview.
For design partner access, send only (high level — no confidential files):
- Project type
- Admission / release uncertainty
- Existing agents or harnesses
- High-responsibility outputs
- Whether an appropriate confidentiality path can be established
Contact us by email
We do not host an inquiry form on this site. Send your message directly to service@lbai.ai. Inquiries are reviewed weekly.
Security note: Please do not attach or paste confidential source code, secrets, production credentials, customer data, regulated data, or proprietary project files in your initial email.
If your project may be a fit for E2C Private Alpha, LBAI will provide an appropriate confidentiality and artifact-sharing path during onboarding.
Put your inquiry type in the subject line, for example:
- Investor materials — Core E2C OS runtime release
- Design partner access
- Strategic partnership
- Press / media
- General inquiry
In the email body, include your name, organization, and the context described above — high level only for design partners.