Notification Domain¶
Why This Exists¶
The Notification Domain is responsible for notification requests, channels, preferences, templates, reminders, escalations, delivery tracking, read status, notification priority, scheduling, and communication history.
Algosure is an AI Digital Procurement Company. Procurement work is deadline-driven, evidence-driven, and collaborative. A missed briefing, expiring document, approval delay, payment reminder, or contract milestone can affect the customer's ability to win and deliver work. Notification exists to make important procurement signals reach the right person through the right channel at the right time.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Notification owns notification request, preference, template, schedule, delivery, read status, escalation, and communication history.
Business Value¶
The Notification Domain improves procurement execution by reducing missed deadlines, accelerating approvals, supporting reminders, and maintaining communication traceability. It does not own the business facts being communicated. It owns the workflow that turns those facts into governed communication.
Domain Definition¶
The Notification Domain manages:
- Notification requests.
- Notification channels.
- Notification preferences.
- Notification templates.
- Reminders.
- Escalations.
- Delivery attempts and delivery status.
- Read status.
- Notification priority.
- Notification scheduling.
- Communication history.
Supported Notification Types¶
- Tender deadlines.
- Expiring documents.
- New recommended tenders.
- Compliance issues.
- Team approvals.
- Award notifications.
- Payment reminders.
- Briefing reminders.
- Bid task reminders.
- Contract milestone reminders.
- Learning reminders.
- Subscription and payment notifications.
Supported Channels¶
- In-app notifications.
- Push notifications.
- Email.
- SMS.
- WhatsApp.
- Future Outlook, Gmail, and calendar integrations.
Ownership Boundaries¶
| Concept | Owning domain |
|---|---|
| Notification requests, preferences, templates, schedules, delivery, read status, escalations, communication history | Notification |
| Tender facts, deadlines, briefing sessions, and recommendations | Opportunity |
| Bid tasks, approvals, proposal workflow, and submission state | Bid |
| Compliance facts, document expiry, verification, and readiness | Compliance |
| Contract milestones, invoices, payments, and delivery state | Contract |
| Learning progress and recommendations | Learning |
| Subscription and billing facts | Billing |
| AI prioritization, summarization, and timing recommendations | Intelligence |
Domain Relationship Overview¶
flowchart TD
Opportunity[Opportunity]
Compliance[Compliance]
Bid[Bid]
Contract[Contract]
Learning[Learning]
Billing[Billing]
Intelligence[Intelligence]
Notification[Notification Domain]
User[Recipient]
Opportunity -->|deadline and recommendation events| Notification
Compliance -->|expiry and issue events| Notification
Bid -->|task and approval events| Notification
Contract -->|milestone and payment events| Notification
Learning -->|learning reminder events| Notification
Billing -->|subscription/payment events| Notification
Intelligence -->|priority and timing recommendations| Notification
Notification -->|delivers through channels| User
Domain-Driven Design Position¶
Notification is a supporting domain that coordinates communication delivery across the Digital Procurement Company. Other domains publish events or request notifications. Notification creates delivery plans, applies preferences, renders templates, schedules messages, tracks delivery, records read status, and escalates when policy requires.
What This Domain Does Not Own¶
Notification does not own tender deadlines, compliance expiry facts, bid approval state, contract payment state, learning progress, or subscription entitlement facts. It stores references, message context, and communication history needed to deliver and audit notifications.