Data Diagrams¶

Executive Summary¶

Data Diagrams provides Mermaid diagrams for the Algosure data architecture. The diagrams cover transactional data, read models, documents, search, semantic memory, audit data, retention, and analytics projections.

Why This Exists¶

Algosure data architecture spans PostgreSQL, read projections, object storage, search, vector memory, audit, outbox, and analytics. Diagrams make ownership and flow reviewable before implementation.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

The diagrams give architecture, engineering, data, AI, security, analytics, and integration teams a shared data baseline.

Primary Data Architecture Diagram¶

flowchart TB
    Domains[Domain Modules]
    PostgreSQL[(PostgreSQL)]
    Outbox[(Event / Outbox Data)]
    ReadModels[(Read Models)]
    Documents[(Document / Object Storage)]
    Search[(Search Index)]
    Vector[(AI Semantic Memory / Vector Store)]
    Audit[(Audit Data)]
    Analytics[(Analytics Projections)]

    Domains --> PostgreSQL
    Domains --> Outbox
    Domains --> ReadModels
    Domains --> Documents
    Domains --> Search
    Domains --> Vector
    Domains --> Audit
    Outbox --> Analytics
    ReadModels --> Analytics

Multi-Tenant Data Diagram¶

flowchart LR
    Tenant[TenantId]
    Organization[OrganizationId]
    User[User / Actor Context]
    Data[Domain-Owned Data]
    Documents[Documents]
    Events[Events]
    Memory[Semantic Memory]
    Audit[Audit]

    Tenant --> Organization
    Organization --> Data
    User --> Data
    Data --> Documents
    Data --> Events
    Data --> Memory
    Data --> Audit

Projection Diagram¶

flowchart LR
    Source[Source Domain Fact]
    Event[Domain Event]
    ReadModel[Read Model]
    Search[Search Projection]
    Analytics[Analytics Projection]

    Source --> Event
    Event --> ReadModel
    Event --> Search
    Event --> Analytics

Document Diagram¶

flowchart TB
    Domain[Owning Domain]
    Metadata[(PostgreSQL Metadata)]
    Object[(Object Storage)]
    Classification[Classification]
    Access[Access Control]
    Audit[Audit Data]

    Domain --> Metadata
    Domain --> Object
    Metadata --> Classification
    Classification --> Access
    Access --> Audit

Semantic Memory Diagram¶

flowchart LR
    Source[Source Domain or Document]
    Governance[Memory Governance]
    Intelligence[Intelligence]
    Vector[(Vector Store)]
    AIOS[AIOS Retrieval]
    Audit[Audit Data]

    Source --> Governance
    Governance --> Intelligence
    Intelligence --> Vector
    Vector --> AIOS
    AIOS --> Audit

Retention Diagram¶

flowchart TB
    Data[Data Item]
    Classify[Classify]
    Owner[Owning Domain]
    Retain[Retain]
    Archive[Archive]
    Delete[Delete]
    Review[Review]
    Audit[Audit Evidence]

    Data --> Classify
    Classify --> Owner
    Owner --> Retain
    Owner --> Archive
    Owner --> Delete
    Owner --> Review
    Retain --> Audit
    Archive --> Audit
    Delete --> Audit
    Review --> Audit

Diagram Notes¶

PostgreSQL is the primary operational store.
Domains own source facts.
Tenant and organization context apply to customer data.
Analytics owns projections, not source facts.
Intelligence owns AI memory records, not operational facts.
Search, read models, vector memory, and analytics are projections or governed records.
Classification, access control, retention, and audit apply across all data stores.