Release
The scoped responsibility state has enough admitted evidence, validation, and authorization to move forward. Release always implies an artifact trail: what was admitted, on what sources, and under which contracts.
Release / Hold / Block
Release / Hold / Block is not marketing language. It is the product-facing expression of E2C’s responsibility state transition system — readiness output, not legal certification or production safety guarantee. E2C runs the responsibility state transitions that produce these outcomes.
Hold
Progress pauses until specified evidence, authorization, or field corrections are satisfied. Hold is an explicit responsibility state — not silent stagnation.
Block
The proposed transition must not proceed. Block records why admission failed — false admission risk, source-boundary error, unauthorized next action, field pollution, or missing validation — so teams can correct or escalate with traceability.
Block is responsibility discovery
Block is not product failure. A Block means the proposed transition should not proceed under the current evidence, source boundary, authorization, or artifact state. The purpose of Block is to expose the responsibility gap so it can be corrected, routed, escalated, deferred, or held with traceability.
Boundary
These outcomes structure release readiness decisions. They do not constitute legal compliance sign-off, security certification, or a promise of business outcome. E2C produces readiness evidence for whether scoped state should move forward, hold, or block before the customer’s own release authority acts.