Compliance Domain

Why This Exists

The Compliance Domain is responsible for procurement readiness, compliance requirements, compliance documents, expiry monitoring, verification, readiness scoring, and compliance risk.

Algosure is the world's first AI Digital Procurement Company. In procurement, an organization cannot reliably pursue opportunities, submit proposals, win contracts, access funding, or build supplier trust without compliance discipline. Compliance is therefore a core domain, not a supporting checklist.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Compliance owns compliance state, requirements, verification, readiness, expiry, compliance evidence, Procurement Readiness Score, and Compliance Risk.

Organization owns company identity. Intelligence may analyse and recommend, but it must not directly mutate compliance facts without approved Compliance commands.

Business Value

The Compliance Domain helps customers understand whether they are procurement-ready, what evidence they have, what documents are expired or missing, what requirements apply to a tender, and what risk should be addressed before submission.

Domain Definition

The Compliance Domain manages:

• Compliance requirements.
• Compliance documents.
• Compliance evidence.
• Verification state.
• Expiry monitoring.
• Tender-specific compliance requirements.
• Procurement Readiness Score.
• Compliance Risk.
• South African procurement context including SARS, CIPC, CSD, CIDB, COIDA, B-BBEE, and tax compliance.

South African Procurement Context

The Compliance Domain must support South African procurement requirements and evidence patterns, including:

Context	Compliance relevance
SARS	Tax compliance status, tax numbers, and tax-related evidence.
CIPC	Company registration, directors, legal status, and company identity evidence.
CSD	Central Supplier Database registration and supplier eligibility.
CIDB	Construction grading and construction-sector eligibility where applicable.
COIDA	Compensation for Occupational Injuries and Diseases Act evidence where required.
B-BBEE	B-BBEE level, certificate, affidavit, expiry, and verification context.
Tax compliance	Eligibility and risk area for public procurement.
Document expiry	Time-based risk for certificates, licences, and declarations.

What Compliance Owns

Owned concept	Ownership meaning
Compliance Requirement	Canonical compliance requirement definition and tender-specific requirement interpretation.
Compliance Document	Compliance document record, status, expiry, and evidence metadata.
Compliance Evidence	Evidence used to satisfy requirements.
Verification	Verification state and verification outcomes.
Procurement Readiness Score	Compliance readiness score and scoring components.
Compliance Risk	Risk assessment tied to missing, expired, weak, or conflicting evidence.
Expiry Monitoring	Monitoring of document and evidence validity dates.

What Compliance Does Not Own

Not owned	Owning domain
Organization identity, legal name, directors as company profile facts	Organization Domain
AI reasoning sessions and suggestions	Intelligence Domain
Opportunity lifecycle and tender records	Opportunity Domain
Proposal drafting and submission workflow	Proposal Domain
Contract execution and obligations	Contract Domain
Supplier marketplace listing ownership	Marketplace or Supplier Domain

Domain Relationship Overview

flowchart TD
    Org[Organization Domain]
    Compliance[Compliance Domain]
    Intel[Intelligence Domain]
    Opportunity[Opportunity Domain]
    Proposal[Proposal Domain]
    Contract[Contract Domain]
    Events[Event Mesh]

    Org -->|OrganizationId and company identity| Compliance
    Intel -->|AI suggestions and analysis| Compliance
    Compliance -->|Readiness and risk| Opportunity
    Compliance -->|Evidence and requirement status| Proposal
    Compliance -->|Compliance obligations| Contract
    Compliance --> Events
    Events --> Compliance

Domain-Driven Design Position

Compliance is a core procurement domain. It has its own aggregates, entities, value objects, domain events, policies, and business rules. It references Organization identity, but it owns compliance state and compliance decisions.

Scope

This document defines the Compliance Domain foundation. It does not define final legal advice, production verification integrations, OpenAPI specifications, database schemas, or regulatory interpretation guarantees.