Historical transition note. Canonical public architecture is Architecture 2026.
Prefer Architecture 2026: Foundry / Construction Plane vs Product Operational Plane, then Core OS → chain families → Client Domain Responsibility System → Client Domain Application. Bootstrap remains historical / self-hosting scaffolding — not a permanent product tier.
Human + GPT + Cursor + repo artifacts temporarily co-evolve responsibility state. Purpose: discover blocks, expose missing grammar / runtime / ledger / registry, and force stable responsibility patterns into the Core OS.
LBAI-owned responsibility operating substrate: kernel, runtime harness, ledger, registry, capability dispatch, structured intake, feedback, resume, release router, and micro-release loop.
A client uses Core E2C OS plus selected application responsibility chains and a domain pack to turn repo + narrative + messy reality into a client-specific responsibility runtime — surfaced through a Client Domain Application. Clients do not operate Core OS kernel internals directly.
Bootstrap E2C builds Core OS. Core OS runs application responsibility chains. Application responsibility chains build client domain instances.