Skip to content

Developers

E2C is a Responsibility Operating System. Admission is a function of that OS — not a standalone product category. The primary developer surface is formal control-plane artifacts, state transitions, and receipts — not a prompt box that becomes Authority.

Primary framing

  • Responsibility OS — substrate for source, state, evidence, Authority, admission, recovery
  • Admission — a function that decides what may become operational reality
  • Control-plane compilation — E2C compiles formal artifacts; client AI generates domain content
  • Not Authority — GPT, Cursor, and coding environments are bounded workers

Submit → adjudicate → repair → authorize → act → observe → admit

A client AI system submits a candidate with evidence and requested next state. E2C returns admissible, remediation required, human Authority required, inconclusive, or block — with exact reasons and permitted next actions. The AI system repairs and resubmits before consequential action enters reality. Receipts and ledger state remain machine-consumable.

Public API shapes are conceptual / design-partner scoped until generally available. How E2C works →

Product stack surfaces

Core OS runtime

Boot, state, structured candidate intake, capability dispatch, ledger / feedback / resume, micro-release of absorbed capabilities.

Application chain families

Reusable vertical responsibility lifecycles on Core OS — not client proprietary rules alone.

Client Domain Responsibility System

Core OS + chains + domain pack + client sources / state / capabilities / authorization.

Client Domain Application

UI / API / workflow surface. Clients do not operate Core OS kernel internals directly.

E2C does not own client domain content generation

Client AI / generation plane

Proposals, repairs, explanations, implementation candidates, domain narrative.

E2C / responsibility plane

Contracts, evidence bindings, state machines, remediation, receipts, Authority requirements, admission decisions.