Completion Notification without Polling
Contract
The durable result is the source of truth. A notification is only a pointer to that result and must not carry the only copy of the outcome.
On completion:
- Write and validate the terminal result artifact.
- Verify once that the intended recipient is available and safe to notify.
- Send one short, unambiguous result pointer.
- Check acceptance once when the transport requires it.
- Do not poll, repeatedly wake, or paste the full result.
Failure Behavior
Notification failure must not erase or invalidate a valid result. Record the notification as deferred and leave the durable artifact available for later consumption. Do not restart or recreate the recipient merely to deliver a completion notice.
Make delivery idempotent with a result identity or deduplication record. A retry may resend the same pointer only when policy allows it and the system can prove that the prior attempt was not accepted.
Authority Boundary
Delivery proves neither review nor approval. The recipient still decides whether to accept, reject, or re-scope the result.