Current State¶

Executive Summary¶

The current Algosure Blueprint is an enterprise product architecture foundation. It defines what Algosure is, how the Digital Procurement Company is organized, which Domains own source facts, which Practices own operational capability, which Digital Professionals execute work, how AIOS orchestrates execution, and how core procurement processes operate.

Why This Exists¶

Current State provides a stable reference point before the repository moves into Architecture, Engineering, UX, and Integration layers. It helps prevent future work from bypassing established ownership rules or creating duplicate concepts.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

Current State gives leadership and delivery teams a concise understanding of the Blueprint baseline, allowing work to proceed from shared context rather than reinterpreting the product thesis.

Current Architecture Layers¶

Layer	Current State
Product Thesis	Algosure is the world's first AI Digital Procurement Company, not tender software.
Foundation	Strategic and documentation standards are established.
Domain Model	Core Domains are defined with DDD language, ownership, events, policies, APIs, database responsibilities, examples, and glossaries.
Practices	Operating departments are defined with responsibilities, governance, KPIs, meetings, reports, SOPs, relationships, and Digital Professional alignment.
Digital Professionals	Professional model and core profiles are defined for Ari, Ava, Orion, Lex, Nova, Atlas, Forge, Nexus, Beacon, Sage, and Pulse.
AIOS	Operating behaviour for orchestration, delegation, collaboration, reasoning, memory, approvals, events, governance, safety, and lifecycle is defined.
Business Capabilities	Capability standards and catalogue foundation are defined.
Business Processes	Core process standards and major procurement process waves are defined.
Roadmap	v0.1 release summary and next-wave sequencing are now defined.

Current Operating Model¶

flowchart LR
    CEO[Customer as CEO]
    Executive[Executive Office]
    Practices[Practices]
    Professionals[Digital Professionals]
    AIOS[AIOS]
    Domains[Domains]
    Processes[Business Processes]
    Analytics[Analytics and Reporting]

    CEO --> Executive
    Executive --> Practices
    Practices --> Professionals
    Professionals --> AIOS
    AIOS --> Processes
    Processes --> Domains
    Domains --> Analytics
    Analytics --> Executive

What Each Layer Means¶

Layer	Meaning
Foundation	Defines the mission, principles, standards, language, and documentation rules.
Domain Model	Defines business truth and ownership.
Practices	Defines how the Digital Procurement Company is organized operationally.
Digital Professionals	Defines governed AI workers that execute Practice work.
AIOS	Defines how AI work is orchestrated, audited, approved, and explained.
Business Capabilities	Defines stable units of business design.
Business Processes	Defines repeatable operating procedures and SOPs.
Roadmap	Defines sequencing, release state, and next investment areas.

Current Business Process Coverage¶

Process Wave	Status
Tender-to-Contract	Draft foundation complete.
Contract Delivery	Draft foundation complete.
Compliance Readiness	Draft foundation complete.
Marketplace and Supplier Sourcing	Draft foundation complete.
Funding Readiness	Draft foundation complete.
Procurement Academy Learning	Draft foundation complete.
Executive Reporting	Draft foundation complete.

Risks and Open Questions¶

Risk or Question	Current Position
Implementation architecture not yet defined	Defer to v0.2 Architecture Foundation.
UX model not yet defined in detail	Defer to Mobile UX and Web UX layers after architecture alignment.
Integration boundaries not yet operationalized	Defer to Integration Layer after architecture baseline.
Process waves are broad and draft	They require future review, prioritization, and implementation mapping.
Automation levels not yet assigned per process	Defer until architecture and engineering readiness are defined.
Source-domain event catalogue needs consolidation	Defer to Architecture Foundation and Event Architecture.
Notification Domain files appear deleted in current git status if present locally	Treat as unrelated worktree state unless explicitly addressed by a future work order.

Current Repository Status¶

The repository is documentation-heavy and Blueprint-oriented. It is ready for architecture design work but not yet ready for implementation build decisions. The next work should translate the stable product and operating model into architecture without changing the business ownership model.