Failure semantics are stated by phase so a policy result is not confused with delivery, execution, recording, or export.
The phase vocabulary and retry disclosure implemented by the public website simulation.
Policy disposition, execution outcome, authoritative-record status, and optional export status answer different questions. A successful policy decision does not imply that the tool ran or that evidence was retained.
Unavailable or expired approval is not permission. Missing evidence, malformed observer output, duplicate delivery, and record failure remain explicit states.
The integration owner decides when reconciliation is complete and whether another attempt is safe. Changed input, policy, configuration, or state may change a later result.
Each retry receives a new attempt identifier and is evaluated against the current normalized input, policy, configuration, and relevant state.
Interactive demonstration · Evidence: website-action-flowLimit: Re-evaluation is not evidence of idempotency or durable duplicate suppression.
An unknown downstream outcome prevents the website scenario from claiming success and calls for reconciliation before a new side effect.
Interactive demonstration · Evidence: website-action-flow, public-hooks-sourceLimit: The website does not operate a production reconciliation service.
The page does not prove exactly-once execution, durable deduplication, or production reconciliation.
The cited public source does not establish the behavior of every possible adapter or deployment.