Skip to content

Core OS Runtime Scaffold Boundary

The current Private Alpha boundary is no longer best described as a proof slice. It is the first Core E2C OS runtime scaffold.

What the scaffold includes

  • E2C boots under its own product-level runtime harness
  • Cursor starts the runner only
  • ChatGPT-generated slots are structured candidate intake only
  • E2C loads admitted state, ledgers, registries, and capability catalogs
  • E2C creates Application requests
  • E2C selects responsibility cycles
  • E2C dispatches admitted capabilities where available
  • E2C emits JSON + FPC artifact pairs for terminal cycles
  • E2C routes ledger / feedback / resume payloads
  • E2C produces release / hold / block / replan decisions
  • E2C micro-releases absorbed capabilities

Out of scope for this public stage

  • Full public SaaS signup on this marketing site
  • Arbitrary repo ingestion
  • Payment checkout or self-serve onboarding
  • Autonomous legal, compliance, or security approval
  • Production deployment or correctness guarantees

← Back to Documentation · Core OS runtime release →