From 2a7e7289b3fec7fc43eb39fd5e62824e5a4ec36a Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Mon, 18 May 2026 23:12:02 -0400 Subject: [PATCH] docs(notification-outbox): polish Notification Service prose and heading scope --- docs/requirements/Component-NotificationService.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/requirements/Component-NotificationService.md b/docs/requirements/Component-NotificationService.md index ab5a0d1..c2de73f 100644 --- a/docs/requirements/Component-NotificationService.md +++ b/docs/requirements/Component-NotificationService.md @@ -2,7 +2,7 @@ ## Purpose -The Notification Service is the central component that manages notification-list and SMTP definitions and provides the per-type delivery adapters used to send notifications. It manages notification lists, manages email server configuration, and supplies the stateless "deliver one notification" adapter implementations that the Notification Outbox invokes at delivery time. +The Notification Service is the central component that manages notification-list and SMTP definitions and provides the per-type delivery adapters used to send notifications. It manages notification-list and SMTP definitions, and supplies the stateless "deliver one notification" adapter implementations that the Notification Outbox invokes at delivery time. The Notification Service no longer delivers notifications from sites. Notification delivery has been inverted: a site script's notification is store-and-forwarded to the central cluster, and the central **Notification Outbox** owns dispatch and delivery, calling an `INotificationDeliveryAdapter` supplied by this component. See [`Component-NotificationOutbox.md`](Component-NotificationOutbox.md). @@ -66,7 +66,7 @@ NotificationStatus status = Notify.Status(id); Delivery is performed centrally by the Notification Outbox, which calls the `INotificationDeliveryAdapter` registered for the notification's `Type`. The behavior below describes the Email adapter. -### Recipient Handling +### Recipient Handling (Email) - A single email is sent per notification, with all list recipients in **BCC**. The from address is placed in the To field. - Recipients do not see each other's email addresses. - No per-recipient deduplication — if the same email address appears in multiple lists and a script sends to both, they receive multiple emails.