Organization Domain¶
Why This Exists¶
The Organization Domain is the root domain of the Algosure Domain Model.
Algosure is the world's first AI Digital Procurement Company. It gives each customer a Digital Procurement Company made up of Practices, Digital Professionals, Business Capabilities, SOPs, Organizational Memory, AI reasoning, executable workflows, and continuous learning.
None of that can operate without a customer organization. Without an Organization, there is no compliance context, no opportunity eligibility, no proposal ownership, no contract party, no supplier profile, no funding applicant, no learning audience, no analytics subject, and no AI memory boundary.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
The Organization Domain itself is owned centrally because it defines the customer business context used by all other domains. Other domains may reference Organization data, but they must not duplicate Organization ownership.
Business Value¶
The Organization Domain creates business value by establishing a single governed source of customer business identity, profile, capability, resources, experience, procurement preferences, intelligence, and memory.
It enables Algosure to reason about a customer's procurement readiness, compliance position, bid fit, supplier role, funding needs, learning requirements, and performance without fragmenting the customer's identity across domains.
Domain Definition¶
The Organization Domain represents the customer business entity using Algosure.
It owns the durable business context for:
- Organization identity and profile.
- Ownership and users.
- Directors, contacts, addresses, branches, departments, and employees.
- Services, products, capabilities, equipment, and fleet assets.
- Past projects and client references.
- Certifications and licences.
- Financial profile and procurement preferences.
- Organization Intelligence Graph.
- Organizational Memory.
Why Organization Is The Root Domain¶
Organization is the root domain because every procurement workflow needs to know who the customer is, what the customer can do, where the customer operates, what evidence the customer has, what preferences apply, and what the customer has learned.
The Organization aggregate is the root aggregate for customer business context. It provides the identity and boundaries other domains reference.
What This Domain Owns¶
| Owned concept | Ownership meaning |
|---|---|
| Organization identity | The canonical customer organization record. |
| Organization profile | Legal, trading, operational, and descriptive profile data. |
| Organization users | Users associated with the organization business context. |
| Directors and contacts | Business people and roles linked to the organization. |
| Addresses and branches | Location and geographic operating context. |
| Services and products | What the organization offers. |
| Capabilities | What the organization can perform and prove. |
| Resources | Equipment, fleet, and operational assets. |
| Experience | Past projects and client references. |
| Certifications and licences | Evidence used by compliance and opportunity matching. |
| Procurement preferences | Customer procurement goals, filters, interests, and constraints. |
| Organization Intelligence Graph | Connected model of organization facts and relationships. |
| Organizational Memory | Durable customer-specific memory boundary. |
What This Domain Does Not Own¶
| Not owned | Owning domain |
|---|---|
| Compliance decisions for a specific opportunity | Compliance Domain |
| Opportunity records and tender lifecycle | Opportunity Domain |
| Proposal content and bid response execution | Proposal Domain |
| Contract obligations and delivery execution | Contract Domain |
| External supplier marketplace records | Supplier or Marketplace Domain |
| Funding applications and funding provider workflows | Funding Domain |
| Learning content catalogue | Learning Domain |
| Cross-organization analytics models | Analytics Domain |
| Billing accounts and invoices | Billing Domain |
The Organization Domain may provide data to these domains, but it does not own their business decisions.
Relationship To Other Domains¶
Other domains reference Organization by stable IDs. They may cache read models for performance, but the Organization Domain remains the source of truth for Organization-owned data.
flowchart TD
Org[Organization Domain]
Identity[Identity]
Compliance[Compliance]
Opportunity[Opportunity]
Proposal[Proposal]
Contract[Contract]
Supplier[Supplier]
Marketplace[Marketplace]
Funding[Funding]
Learning[Learning]
Intelligence[Intelligence]
Notification[Notification]
Analytics[Analytics]
Billing[Billing]
Admin[Administration]
AIMemory[AI Memory]
Org --> Identity
Org --> Compliance
Org --> Opportunity
Org --> Proposal
Org --> Contract
Org --> Supplier
Org --> Marketplace
Org --> Funding
Org --> Learning
Org --> Intelligence
Org --> Notification
Org --> Analytics
Org --> Billing
Org --> Admin
Org --> AIMemory
Organizational Context Created¶
This domain creates the organizational context for:
- Compliance: eligibility, documents, directors, certifications, licences, and business facts.
- Opportunities: matching, relevance, geography, industry, and capacity.
- Proposals: company profile, evidence, projects, references, and capabilities.
- Contracts: legal entity, contacts, delivery capacity, and operating footprint.
- Suppliers: supplier identity, services, products, and marketplace role.
- Funding: financial profile, funding needs, and organization eligibility.
- Learning: users, roles, maturity, and capability gaps.
- Analytics: organization-level KPIs, health, and performance context.
- AI memory: bounded organizational facts, history, preferences, and learned context.
Domain-Driven Design Position¶
Organization is a core domain aggregate root. It defines a bounded context and a ubiquitous language for customer business identity. Other domains must speak to Organization through IDs, APIs, events, and read models instead of recreating Organization concepts.
Scope¶
This document defines the Organization Domain foundation. It does not define implementation code, final database schemas, final OpenAPI contracts, or production infrastructure.