Notification Glossary¶
Why This Exists¶
This glossary defines Notification Domain terms with precise meanings.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Shared language helps product, architecture, engineering, and communication design teams build a consistent Notification Domain.
Terms¶
| Term | Definition |
|---|---|
| Notification Request | A domain or workflow request to notify one or more recipients. |
| Notification | A message instance created and tracked by Notification. |
| Recipient | The target user, role, team, organization contact, or recipient rule for a notification. |
| Notification Channel | A delivery route such as in-app, push, email, SMS, WhatsApp, Outlook, Gmail, or calendar. |
| Notification Preference | User or organization settings for channels, timing, frequency, and notification types. |
| Notification Template | Approved message structure used to render notifications. |
| Reminder | A scheduled notification tied to time, recurrence, or a source-domain deadline. |
| Escalation | A policy-driven follow-up when a notification is unread, undelivered, or unacknowledged. |
| Delivery Attempt | A single attempt to send a notification through a channel. |
| Delivery Status | The delivery state of a notification or delivery attempt. |
| Read Status | Recipient-specific state showing unread, read, acknowledged, or dismissed. |
| Notification Priority | Urgency classification used for delivery and escalation decisions. |
| Notification Schedule | Timing plan for delivery. |
| Communication History | Auditable record of notification events and interactions. |
| Source Reference | Reference to the owning domain fact that caused the notification. |
| Channel Connector | Integration component for an external provider or calendar system. |
| Critical Override | Policy-based permission to bypass normal suppression for high-risk procurement communication. |
Boundary Notes¶
Notification terms describe communication workflow. Business terms such as tender, compliance document, bid task, contract milestone, course, invoice, and subscription remain defined in their owning domains.