Skip to content

System Context

Executive Summary

System Context defines the C4 Level 1 view for Algosure. It identifies the people, organizations, external systems, and partner ecosystems that interact with Algosure without defining implementation details, integration mechanisms, APIs, schemas, infrastructure, or provider choices.

Why This Exists

Algosure operates as an AI Digital Procurement Company for customer organizations. The system context protects the architecture boundary before detailed design begins, so Domains, AIOS, Digital Professionals, tenant isolation, security, events, and integrations can be designed from a shared external view.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

The system context helps product, architecture, engineering, AI, security, data, operations, and integration teams agree on what Algosure is responsible for and what remains outside its control.

C4 Level 1 Scope

At C4 Level 1, Algosure is treated as one software system.

flowchart LR
    CEO[Customer Organization / CEO]
    Users[Organization Users]
    PublicTender[Public Tender Sources]
    PrivateTender[Private Tender Sources]
    Government[Government and Compliance Systems]
    Productivity[Email, Storage, Signature, and Messaging Platforms]
    Partners[Payment, Funding, and Marketplace Partners]

    Algosure[Algosure System]

    CEO --> Algosure
    Users --> Algosure
    PublicTender --> Algosure
    PrivateTender --> Algosure
    Government --> Algosure
    Productivity <--> Algosure
    Partners <--> Algosure

Inside Algosure

Inside Algosure means the platform owns the business capability, governing rules, audit obligations, tenant controls, source-of-truth decisions, and AIOS orchestration behavior.

Inside Area Context Responsibility
Tenant workspace Represents each customer organization as an isolated operating environment.
Domain modules and bounded contexts Own source facts, business rules, lifecycle state, commands, and domain events.
AIOS orchestration Coordinates work, context, delegation, approvals, events, exceptions, reasoning, and audit evidence.
Digital Professionals Execute delegated AI work inside Algosure guardrails; they do not act as independent external systems.
Workflow and process layer Runs procurement, compliance, bidding, funding, marketplace, learning, analytics, and notification processes.
Security and tenant isolation Enforces identity, authorization, least privilege, tenant boundaries, approvals, and auditability.
Event layer Publishes and consumes governed business events across Domains, workflows, AIOS, analytics, notifications, and integrations.
Integration boundary Mediates external sources and partner systems while preserving internal ownership.

Outside Algosure

Outside Algosure means the platform can request, receive, validate, enrich, exchange, or reference information, but the external party retains independent ownership, availability, policy control, and authoritative operation of that system or actor.

External Category Examples
Customer actors Customer organization, CEO, executive sponsors, administrators, procurement users, finance users, compliance users, bid contributors, approvers, and viewers.
Tender sources Public tender sources and private tender sources.
Government and compliance systems SARS, CIPC, CSD, CIDB, COIDA, B-BBEE agencies, and future government or country-specific systems.
Productivity and collaboration systems Gmail, Outlook, Google Drive, OneDrive, DocuSign, and WhatsApp.
Commercial partners Payment provider, funding partners, and marketplace providers.

Context Principles

Principle Context Meaning
Domain first External interactions must map to the Domain that owns the relevant facts and business language.
AIOS aligned AIOS orchestrates work and decisions but does not own source facts that belong to Domains or external authorities.
Multi-tenant by design Every external interaction must preserve tenant identity, tenant isolation, consent, authorization, and audit evidence.
Secure by design External access must be explicit, least-privilege, traceable, and reviewable.
Event-driven Important external observations, validations, documents, messages, payments, funding updates, and marketplace updates should become governed business events where appropriate.
Contract governed External interactions require deliberate contracts before implementation.

Non-Implementation Boundary

This document does not define:

  • API endpoints.
  • Authentication protocols.
  • Integration providers.
  • Data schemas.
  • Event names or payloads.
  • Database tables.
  • Infrastructure topology.
  • User interface flows.
  • AI model providers.