Canonical public architecture: two operating environments, and a four-layer product system stack inside the Product Operational Plane. Bootstrap scaffolding is historical transition context — not a permanent product tier.
Earlier public materials described Bootstrap → Core OS → Client Domain Instance as three peer operating states. That path remains useful as history. The canonical 2026 framing is: Foundry / Construction Plane vs Product Operational Plane, then the product stack clients actually consume.
Two operating environments
Builds, validates, admits, absorbs, and releases E2C capabilities, runtime profiles, application responsibility chains, and Core OS assets. Foundry construction runtimes do not appear in a client’s normal product runtime.
Runs client-facing responsibility state through Core OS, application responsibility chains, client domain systems, and application / UI / API surfaces.
Product system stack
Horizontal substrate: Product / Local / Atomic runtime, state, ledger, registry, Authority, capability dispatch, admission, feedback, resume, release, recovery.
Reusable vertical responsibility lifecycles that run on Core OS — LBAI-provided common chains.
Core OS + selected chains + client domain pack + client sources / state / capabilities / authorization + client-specific operational runtime.
UI / API / workflow / report / approval surface. Clients do not operate Core OS kernel internals directly.
Bootstrap
Bootstrap / self-hosting scaffolding discovered missing grammar, runtime, ledger, and registry surfaces while LBAI built E2C as its own first design partner. It is not a permanent public product tier customers buy.
Architecture pages describe system structure — not GA availability, production guarantees, or legal certification.