Developer Manual
Results and errors
Handle closed outcomes and recovery boundaries safely.
Treat public outcomes as a closed set and branch explicitly.
| Outcome | Dispatch meaning | Safe application action | Prohibited action |
|---|---|---|---|
COMMITTED | Independent verifier established PRESENT | Render only an approved bounded claim and retain evidence | Claim more than the verified effect |
DISPROVED | Independent verifier established ABSENT_FINAL | Report that the requested effect was not confirmed and investigate policy/business cause | Treat provider acknowledgment as success |
UNKNOWN | Dispatch may have crossed and effect truth is unresolved | Preserve identities and evidence; perform permitted verifier-only reconciliation | Blind redispatch |
CLARIFICATION_REQUIRED | Proposal or grounding is insufficient before dispatch | Ask for the missing bounded clarification | Choose a candidate silently |
AUTHORIZATION_DENIED | Policy did not permit the exact operation | Stop before dispatch and present an appropriate denial | Execute with a different or stale context |
PROVIDER_REJECTED | Provider returned a bounded rejection | Record the attempt and follow host policy | Map it directly to DISPROVED without verification |
PRECONDITION_FAILED | Provider precondition failed | Refresh or clarify according to host policy | Retry blindly |
INTEGRATION_FAILURE | Host integration could not complete its boundary | Preserve diagnostic evidence without exposing secrets | Claim success or conceal the boundary failure |
UNKNOWN is unresolved world state, not ordinary success or permission to retry. Reconciliation verifies the original effect and never creates a second provider dispatch.