E2C Architecture v0.1 — how business evidence becomes source-bound artifacts, ledger state, and release-ready outcomes. Kernel internals and confidential runbooks are not published here.
A responsibility artifact is a source-bound, field-disciplined object that represents an admissible slice of enterprise reality — not raw documents, not model output alone, and not informal approval. Artifacts carry enough structure for the kernel to adjudicate transitions: what sources apply, which fields are present, what actions are allowed next, and what must be blocked.
E2C starts with source-bound responsibility artifacts, but the commercial product is not a pile of artifacts. The Core E2C OS turns artifacts into a runnable responsibility system:
The state ledger records admitted responsibility state — not a generic event log. Transition contracts define which state changes are allowed, what evidence is required, and who or what may authorize the next step. E2C adjudicates whether a candidate output may enter this space; it does not replace your model or coding harness.
Artifacts are not the end state. A responsibility artifact or capability becomes infrastructure only when it can be resolved through registry / ledger state, invoked through runtime callable surfaces, executed under product-level runtime harness, recorded through invocation evidence, routed through feedback / resume / release payloads, and absorbed through a system micro-release. Construction is not value release. Operational absorption is.
Kernel implementation details, confidential slot runbooks, and design-partner-only API references are shared out of band. This page is a public architecture note for Private Alpha v0.1 — not a production deployment or compliance guarantee.