Notification Relationships

Why This Exists

This document explains how Notification relates to other Algosure domains.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Relationship clarity prevents Notification from becoming a duplicate store of procurement facts while still making the platform operationally responsive.

Relationship Diagram

flowchart TD
    Identity[Identity]
    Organization[Organization]
    Opportunity[Opportunity]
    Compliance[Compliance]
    Bid[Bid]
    Contract[Contract]
    Learning[Learning]
    Funding[Funding]
    Marketplace[Marketplace]
    Billing[Billing]
    Intelligence[Intelligence]
    Analytics[Analytics]
    Notification[Notification]

    Identity -->|recipient identity and access| Notification
    Organization -->|organization contacts and roles| Notification
    Opportunity -->|tender deadlines, briefings, recommendations| Notification
    Compliance -->|expiring documents and issues| Notification
    Bid -->|tasks, approvals, submission reminders| Notification
    Contract -->|milestones, payments, delivery reminders| Notification
    Learning -->|learning reminders| Notification
    Funding -->|application and repayment reminders| Notification
    Marketplace -->|quote and provider workflow reminders| Notification
    Billing -->|subscription and payment notifications| Notification
    Intelligence -->|priority, summary, timing support| Notification
    Notification -->|delivery and engagement metrics| Analytics

Relationship Catalogue

Domain	Relationship	Data ownership rule
Identity	Provides user identity, access, and user references.	Identity owns users. Notification owns recipient delivery state.
Organization	Provides organization contacts, teams, and role context.	Organization owns business profile. Notification owns communication history.
Opportunity	Requests tender deadline, briefing, and recommended tender notifications.	Opportunity owns tender facts. Notification owns delivery workflow.
Compliance	Requests expiring document and compliance issue notifications.	Compliance owns compliance state. Notification owns communication state.
Bid	Requests task, approval, and submission reminders.	Bid owns bid workflow state. Notification owns reminders and delivery.
Contract	Requests milestone, payment, invoice, and delivery reminders.	Contract owns contract facts. Notification owns communication records.
Learning	Requests learning reminders and recommendation prompts.	Learning owns learning state. Notification owns delivery state.
Funding	Requests funding application or repayment reminders.	Funding owns funding state. Notification owns delivery state.
Marketplace	Requests quote, provider, or marketplace workflow notifications.	Marketplace owns marketplace workflow state. Notification owns delivery.
Billing	Requests subscription and payment notifications.	Billing owns entitlement and payment facts. Notification owns delivery.
Intelligence	Supports summary, timing, and prioritization.	Intelligence owns reasoning output. Notification owns delivery decisions.
Analytics	Consumes delivery, read, and escalation metrics.	Analytics owns reporting views. Notification owns source records.

Boundary Rule

Notification stores source references, rendered message content, delivery results, and communication history. It does not store the full tender, compliance document, bid task, contract milestone, or billing invoice as owned business data.