Skip to content

Core E2C OS runtime release

The first commercial E2C release is not a SaaS UI and not a full design-partner workspace. It is the Core E2C OS product-level runtime scaffold.

What this release proves

This release is successful when:

  • E2C boots
  • State and resume anchors load
  • Structured candidate intake is normalized
  • Application request is created
  • A responsibility cycle is selected
  • Engineering controlled cycle executes
  • Operational capabilities dispatch when available
  • Ledger / feedback / resume routes are emitted
  • Release, hold, block, or replan output is produced
  • Absorbed capabilities can micro-release

Authority boundary

  • Cursor starts the runner only
  • ChatGPT-generated slots are structured candidate intake only
  • E2C owns state, runtime, dispatch, ledger, feedback, resume, and micro-release

Still not claimed

  • Full public SaaS
  • Arbitrary repo ingestion
  • Full client-domain responsibility runtime
  • Production deployment guarantee

← Back to Documentation · Micro-release loop →