Compliance Relationships

Why This Exists

This document explains how Compliance relates to Organization, Intelligence, and other Algosure domains.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear relationships preserve ownership while making compliance readiness available across the Digital Procurement Company.

Relationship Diagram

flowchart TD
    Organization[Organization]
    Compliance[Compliance]
    Intelligence[Intelligence]
    Opportunity[Opportunity]
    Proposal[Proposal]
    Contract[Contract]
    Supplier[Supplier]
    Funding[Funding]
    Notification[Notification]
    Analytics[Analytics]
    Admin[Administration]

    Organization -->|identity and profile references| Compliance
    Intelligence -->|suggestions and analysis| Compliance
    Compliance -->|readiness and gaps| Opportunity
    Compliance -->|evidence and requirement status| Proposal
    Compliance -->|obligation readiness| Contract
    Compliance -->|supplier eligibility context| Supplier
    Compliance -->|funding eligibility evidence| Funding
    Compliance -->|expiry and risk alerts| Notification
    Compliance -->|events and scores| Analytics
    Admin -->|review support| Compliance

Relationship Map

Domain	Relationship	Ownership boundary
Organization	Supplies OrganizationId, identity, profile, directors, and organization facts.	Organization owns identity; Compliance owns compliance state.
Intelligence	Analyses compliance state and suggests actions.	Intelligence cannot mutate Compliance facts directly.
Opportunity	Uses readiness and tender-specific requirement assessment.	Opportunity owns opportunity lifecycle.
Proposal	Uses compliance evidence and requirement status in bid responses.	Proposal owns response content.
Contract	Uses compliance evidence for delivery readiness.	Contract owns obligations and execution.
Supplier	Uses compliance status for supplier eligibility context.	Supplier owns supplier records.
Funding	Uses compliance and financial evidence context.	Funding owns funding applications.
Notification	Sends expiry, gap, and risk alerts.	Notification owns delivery records.
Analytics	Consumes readiness, expiry, risk, and verification events.	Analytics owns projections.
Administration	Supports review, exception, and governance workflows.	Compliance owns final compliance state.

Ownership Rule

Compliance owns readiness, verification, expiry, evidence status, and compliance risk. Organization data referenced in compliance workflows remains Organization-owned.