Domain Map

Why This Exists

This document maps the Algosure domains and shows how they work together as one Digital Procurement Company.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

The domain map helps product, architecture, engineering, and AI design teams understand where each business responsibility belongs and how domains communicate.

Strategic Domain Structure

flowchart TB
    subgraph Foundation[Foundation Domains]
        Organization[Organization]
        Identity[Identity]
        Billing[Billing]
        Administration[Administration]
    end

    subgraph Procurement[Procurement Execution Domains]
        Compliance[Compliance]
        Opportunity[Opportunity]
        Bid[Bid]
        Contract[Contract]
    end

    subgraph Ecosystem[Procurement Ecosystem Domains]
        Supplier[Supplier]
        Marketplace[Marketplace]
        Funding[Funding]
        Learning[Learning]
    end

    subgraph Operating[Operating Intelligence Domains]
        Intelligence[Intelligence]
        Notification[Notification]
        Analytics[Analytics]
    end

    Organization --> Procurement
    Organization --> Ecosystem
    Identity --> Foundation
    Billing --> Foundation
    Compliance --> Opportunity
    Opportunity --> Bid
    Bid --> Contract
    Supplier --> Marketplace
    Marketplace --> Supplier
    Contract --> Funding
    Learning --> Analytics
    Notification --> Analytics
    Intelligence --> Procurement
    Intelligence --> Ecosystem
    Administration --> Foundation
    Administration --> Operating

Domain Groups

Group	Domains	Purpose
Foundation Domains	Organization, Identity, Billing, Administration	Establish customer context, secure access, commercial access, and platform governance.
Procurement Execution Domains	Compliance, Opportunity, Bid, Contract	Run the procurement lifecycle from readiness to opportunity to bid to delivery.
Procurement Ecosystem Domains	Supplier, Marketplace, Funding, Learning	Support suppliers, provider discovery, financing, and customer capability development.
Operating Intelligence Domains	Intelligence, Notification, Analytics	Provide reasoning, communication, reporting, and executive insight.

Procurement Lifecycle Alignment

flowchart LR
    Org[Organization Context]
    Ready[Compliance Readiness]
    Find[Opportunity Discovery]
    Pursue[Bid Preparation]
    Deliver[Contract Delivery]
    Learn[Learning and Improvement]
    Report[Analytics and Briefing]

    Org --> Ready
    Ready --> Find
    Find --> Pursue
    Pursue --> Deliver
    Deliver --> Learn
    Learn --> Report
    Report --> Org

Domain Map Rules

• Organization is the root business context.
• Identity is the access control foundation.
• Billing controls commercial entitlement signals.
• Intelligence supports reasoning and orchestration but does not own source facts.
• Notification delivers communication but does not own business facts.
• Analytics owns reporting models but does not mutate source facts.
• Administration configures and reviews but does not take source-domain ownership.

Modulith Interpretation

In Spring Boot Modulith terms, each domain should become a module with explicit public APIs, internal package boundaries, and domain events. The map should guide module structure, event contracts, and integration tests.