Document Storage Architecture

Executive Summary

Document Storage Architecture defines how Algosure stores and governs documents and binary evidence. Object storage is used for files, while owning Domains retain metadata, access control, classification, lifecycle, and audit ownership.

Why This Exists

Algosure handles tender documents, compliance evidence, bid packs, generated documents, signed contracts, exports, supplier files, funding evidence, learning artifacts, and AI-generated documents. These files require tenant-scoped access and source-domain governance.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Governed document storage protects sensitive customer evidence, improves auditability, supports document workflows, and prevents object storage from becoming an unmanaged dumping ground.

Document Storage View

flowchart TB
    User[User or AIOS Workflow]
    Domain[Owning Domain]
    Metadata[(PostgreSQL Document Metadata)]
    ObjectStore[(Document / Object Storage)]
    Audit[(Audit Data)]
    Search[(Search Index)]

    User --> Domain
    Domain --> Metadata
    Domain --> ObjectStore
    Domain --> Audit
    Metadata --> Search

Document Ownership

Document Type	Owning Domain
Compliance evidence	Compliance.
Tender source documents	Opportunity or Bid depending on lifecycle stage.
Bid documents and generated bid packs	Bid.
Awarded contract documents	Contract.
Supplier documents and quote attachments	Supplier or Marketplace depending on source.
Funding evidence and partner documents	Funding.
Billing invoices and payment evidence	Billing.
Learning certificates and course artifacts	Learning.
AI-generated documents	Owning operational Domain with Intelligence reasoning reference.

Document Rules

Rule	Requirement
Object storage stores files	Object storage holds binary files but does not own business meaning.
Metadata is domain-owned	PostgreSQL stores document metadata, ownership, tenant, organization, classification, lifecycle, and retention state.
Access is policy-controlled	Document access requires tenant, organization, role, permission, ownership, classification, and workflow state checks.
Documents are auditable	Upload, view, download, edit, generate, sign, share, delete, and retention actions are audited.
Documents are classified	Classification drives access, retention, encryption, indexing, and AIOS eligibility.
AIOS document use is governed	AIOS can access documents only through scoped, approved, auditable workflows.

Non-Implementation Boundary

This document does not define bucket names, object keys, storage provider, file formats, antivirus tooling, OCR tooling, or final document metadata schema.