Define what the exercise can prove

Write down the event that starts the notification, the template version, recipient type, sender identity, provider receipt, and observer. Use a dedicated test inbox or another safe recipient. Do not use a customer or distribution list merely because it is convenient.

RFC 5321 specifies SMTP transport and submission behavior. It does not make a local test proof that someone received, read, understood, or consented to a business notification.

Exercise one bounded path

Trigger one ordinary, non-consequential event in a disposable or approved non-production fixture. Capture the operation ID, template version, safe recipient, provider-acceptance reference, and the follow-up observation. Review the rendered content for environment, links, scope, and wording before broadening the audience.

If a network error leaves the result uncertain, do not immediately resend. Check the provider or application record first under one operation identity or idempotency rule. A disabled button reduces one accidental repeat; it does not prove that the service deduplicates requests.

Keep a notification receipt

The local evidence/P95/notification-receipt.mjs artifact rejects an unbounded audience, a recipient not explicitly approved as an owned test inbox, missing template or provider record, and retry without an idempotency key:

npm test --prefix sites/howtox.com/evidence/P95

It validates a record shape only. It does not send mail or prove provider acceptance, delivery, rendering, consent, or reading.

Verification checklist

  • One harmless event and named safe recipient are approved.
  • The template, sender identity, and intended scope are recorded.
  • Provider acceptance and follow-up observation have separate evidence.
  • An unknown outcome has a reconciliation path before any resend.
  • A named operator owns duplicate containment and audience expansion.

Does provider acceptance prove that the recipient got the message?

No. It is one transport-stage observation. Retain it separately from any delivery, inbox, or business-workflow observation your system can legitimately make.