Intelligence Relationships

Why This Exists

This document explains how the Intelligence Domain relates to Organization and other major Algosure domains.

Intelligence coordinates work across domains, but it does not own their source business facts.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear relationships allow Algosure Intelligence to reason across the Digital Procurement Company while preserving domain ownership and trust.

Relationship Diagram

flowchart TD
    Intelligence[Intelligence Domain]
    Organization[Organization Domain]
    Graph[Organization Intelligence Graph]
    EventMesh[Event Mesh]
    Execution[Procurement Execution Engine]
    Compliance[Compliance]
    Opportunity[Opportunity]
    Proposal[Proposal]
    Contract[Contract]
    Supplier[Supplier]
    Funding[Funding]
    Learning[Learning]
    Analytics[Analytics]
    Audit[Audit and Administration]

    Organization --> Graph
    Graph --> Intelligence
    EventMesh --> Intelligence
    Intelligence --> Execution
    Intelligence --> Compliance
    Intelligence --> Opportunity
    Intelligence --> Proposal
    Intelligence --> Contract
    Intelligence --> Supplier
    Intelligence --> Funding
    Intelligence --> Learning
    Intelligence --> Analytics
    Intelligence --> Audit

Relationship Map

Domain or layer	Relationship	Ownership boundary
Organization	First dependency for customer context and Organization Intelligence Graph.	Organization owns source facts.
Event Mesh	Supplies events and receives intelligence events.	Event Mesh transports; domains own event meaning.
Procurement Execution Engine	Receives governed execution requests.	Execution layer owns workflow execution state.
Compliance	Receives reasoning support and evidence interpretation.	Compliance owns compliance decisions.
Opportunity	Receives matching and fit recommendations.	Opportunity owns opportunity lifecycle.
Proposal	Receives drafting, review, and evidence support.	Proposal owns proposal content and workflow.
Contract	Receives delivery readiness reasoning.	Contract owns contract obligations.
Supplier	Receives supplier recommendation support.	Supplier owns supplier records.
Funding	Receives funding fit reasoning.	Funding owns funding applications.
Learning	Receives learning recommendations and feedback.	Learning owns curriculum and progress.
Analytics	Consumes intelligence events and KPIs.	Analytics owns analytics projections.
Administration and Audit	Reviews intelligence activity and policy outcomes.	Administration owns support workflows; Intelligence owns AI audit events.

Organization Dependency Rule

Customer-bound intelligence must begin with Organization context. Intelligence must reference OrganizationId and Organization Intelligence Graph state where relevant.

Event Mesh Interaction

The Intelligence Domain consumes events such as OrganizationProfileUpdated and publishes events such as ReasoningCompleted, HumanApprovalRequired, and ExecutionRequested.

Ownership Rule

Intelligence may recommend changes to other domains. It must route those changes through the owning domain rather than writing directly to source-owned data.