Introduce a validated notification type and use transactional publication, current audience selection and repetition collapse.
Registration establishes the declaration before publication. The request retains event identity, audience processing selects eligible current staff, and collapse combines repeated contributions in the recipient inbox.
The structured steps and assertions carry their own provenance and sources. Test references describe inspected assertions at the pinned commits; this examination does not claim a fresh provider or browser execution.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Goal
Introduce a validated notification type and use transactional publication, current audience selection and repetition collapse.
End-to-end policy: none: Registration, publication, audience selection and collapse have backend evidence; other inbox journeys provide the browser experience for the final recipient view.