Committed vs. released
Committed is not a decision
Section titled “Committed is not a decision”VerifyProofBundleV2 returns a committed outcome: the claim ID, the digest of the sealed
receipt body, the challenge expiry, the allow horizon, and the sealed body bytes for
publication. It exposes no decision, boolean, or status an application could act on. An
application must not parse the sealed body to authorize.
The terminal result is allow, deny, or indeterminate, with one reason (for example
authorized, scope_denied, delegation_revoked, status_stale, trust_unavailable). It is
sticky for that challenge; recovery needs a fresh challenge.
The release gate
Section titled “The release gate”ReleaseV2Decision(handoff, signed receipt, configuration) runs these checks in order and stops
at the first that fails:
- Committed state. The claim is terminal and matches the handoff.
- Receipt. The signed receipt verifies under the configured verifier key and log ID.
- Body binding. The receipt body equals the sealed outbox body.
- Prior release. Any earlier release of this claim names the same receipt.
- Predecessor. The previous log entry is acknowledged and chains to this receipt.
- Acknowledgement. The independent checkpoint acknowledged this receipt.
- Clock. The authoritative clock has not moved backward.
- Deadlines. Acknowledgement and release are before the challenge expiry and, for an allow, before the allow horizon.
- Record. The release is durably recorded.
- Return a released decision.
| Result | Meaning |
|---|---|
released |
The only actionable result |
pending |
Retry later (receipt not appended, acknowledgement or clock unavailable) |
withheld |
Permanent for this claim (expired, horizon passed, clock regressed, receipt abandoned) |
rejected |
Permanent for this claim (invalid receipt, body or state mismatch, log fork) |
Release is idempotent: a recorded release returns the same decision and receipt, but every call re-checks the acknowledgement and the deadlines.
The action check
Section titled “The action check”The released decision is sealed: no constructor, copy, deserializer, or default value produces
an actionable one. Immediately before any side effect, the receiver calls its action check
(Allowed, allowed, ratify_v2_released_allowed) against its own authoritative clock. It is
true only for an allow while the clock is before the challenge expiry and the allow horizon.
Never gate a side effect on the release status, a decision string, or a receipt alone.
Application policy goes after release
Section titled “Application policy goes after release”Application policy may narrow a released allow. It cannot turn a committed outcome into a released one, rewrite a receipt, or call a cached product decision a Protocol allow.
Details: SPEC-v2 §6.9, §7.9, §9.12.
