Architecture 2026
Two operating environments + product system stack. Canonical public architecture.
Documentation
Public documentation for E2C. Start with Architecture 2026 and the current public boundary. Confidential runbooks and kernel internals are not published here.
Start here
Current public product boundary
Proven / in progress / not claimed.
How E2C works
Continuous Generate → Adjudicate → Repair → Act → Observe → Admit loop.
Core E2C OS runtime release
First commercial-origin release: product-level runtime scaffold — not a SaaS UI.
Core OS & runtime
Capability micro-release loop
Operational absorption → invocation record → micro-release → recursive availability.
Product / local / atomic runtime hierarchy
Three runtime levels inside a commercial E2C run.
GPT candidate-only boundary
Models propose; E2C admits and runs state.
Execution plane vs Responsibility plane
Coding / agent execution vs E2C responsibility runtime.
Responsibility artifacts overview
Artifacts → runtime-governed capability → micro-release.
Release / Hold / Block
Readiness semantics inside the continuous loop — not legal certification.
Design partner
Design partner operating model
How engagement works — downstream of Core OS maturity.
What design partners should prepare
What to bring, what to describe, and what not to submit publicly.
Data, security, and artifact boundary
Out-of-band sharing; GPT candidate-only boundary.
Run scope, time, and cost boundary
Run modes, preflight, continue gates, micro-release capitalization.
Inputs, outputs & non-claims
What E2C consumes
Evidence, artifacts, and structured candidate intake.
What E2C outputs
Artifacts, ledger entries, runtime payloads, micro-release candidates.
What E2C does not claim
Public non-guarantees and model-authority boundary.
Core OS Runtime Scaffold Boundary
Private Alpha public boundary detail.
Historical notes
Three E2C operating states (historical)
Superseded as primary framing by Architecture 2026. Kept for transition context.
E2C stage boundary (historical)
Legacy 0.1 / 0.5 / 1.0 staging. Prefer current public product boundary.