The absent receipt
A reviewer cannot find a delivery receipt. It is tempting to conclude the message failed. Perhaps it did. Perhaps the receipt was stored elsewhere, the query lacked permission, or the service delivered while receipt persistence failed. Each possibility matters for the next action.
Missing evidence is evidence of a gap in the available record. It may be strong evidence that a required verification has not been performed. It is not automatically proof that the underlying event did not occur, just as a success log is not proof that it did.
Distinguish event from access
The PHS enforcement standard treats receipt failure and unconfirmed effects as first-class conditions, with separate reconciliation and recovery requirements. The claims discipline offers 'not checked' rather than forcing every unknown into success or failure. The Memory API test plan similarly distinguishes a missing result from a complete substrate verdict.
An operator may still need to stop, hold publication, or avoid retrying a payment until the ambiguity is resolved. That is a responsible action under uncertainty, not an invented conclusion about what happened.
Pause here: Is the evidence absent because the event failed, the record failed, or the search could not reach the right place?
Investigate the gap
First identify which receipt should exist and what system owns it. Search the authorized source, inspect the downstream state, and correlate independent IDs. If the effect is still uncertain, report it as uncertain and choose a retry path that cannot duplicate harm. Keep the investigation record for the next person.
An empty page in the travel diary tells us the traveler did not record the day. It does not tell us whether the traveler reached the village. We may need to ask the village.
My answer: Missing evidence blocks confirmation and may require a hold. It does not automatically prove the underlying action failed; investigate and report the gap precisely.