Responsibility artifacts
Source-bound objects with field-presence discipline, admitted into the state space for agents, harnesses, and release surfaces to consume through validated state interfaces.
What E2C outputs
System-consumable responsibility state — not slide decks or monitoring dashboards alone.
State ledger entries
Traceable records of adjudication, validation, authorization, and allowed transitions — durable operating history, not ephemeral chat context.
Release outcomes
- Release — readiness admitted with artifact trail
- Hold — further evidence or authorization required
- Block — state must not proceed; reason recorded
- Replan — scoped path must be revised before continuation
Runtime and operational outputs
E2C also produces product-runtime outputs:
- Invocation records
- JSON + FPC artifact pairs
- Ledger write plan payloads
- Feedback records and resume plan payloads
- Next-context export records
- Micro-release candidates
- Block / GAP diagnostics
- Release / hold / block / replan decisions