Terminology¶
Why This Exists¶
This document defines foundational terms used in the Algosure Blueprint.
Algosure is not tender software. Algosure is the world's first AI Digital Procurement Company. It gives each customer a Digital Procurement Company made up of Digital Professionals, Practices, Business Capabilities, SOPs, Organizational Memory, AI reasoning, executable workflows, and continuous learning.
The terminology standard ensures those concepts are named consistently and owned once.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
The owner is accountable for maintaining the controlled vocabulary and preventing duplicate names for the same concept.
Business Value¶
Clear terminology creates business value by reducing ambiguity, improving onboarding, strengthening governance, and making the Blueprint easier to implement consistently.
Terminology Rules¶
- Define each concept once.
- Use the approved name consistently.
- Link to the owning document where a fuller definition exists.
- Do not create synonyms unless a standard explicitly approves them.
- Preserve One Concept, One Owner.
Core Product Terms¶
| Term | Definition |
|---|---|
| Algoza | The company that builds Digital Companies. |
| Algosure | The world's first AI Digital Procurement Company. |
| Digital Company | A digital enterprise with roles, responsibilities, capabilities, workflows, memory, reasoning, and learning. |
| Digital Procurement Company | The customer-specific Digital Company delivered by Algosure for procurement work. |
| Blueprint | The master design for building Algosure as an AI-native Digital Enterprise. |
| Customer as CEO | The principle that the customer leads their Digital Procurement Company rather than merely using software. |
Enterprise Structure Terms¶
| Term | Definition |
|---|---|
| Digital Enterprise | A business operating model represented through governed digital structures. |
| Artificial Organization | A digitally represented organization that structures work, responsibility, memory, reasoning, workflows, KPIs, and learning. |
| Digital Procurement Headquarters | The customer-facing operating environment for leading the Digital Procurement Company. |
| Practice | A professional domain of procurement work with ownership, procedures, capabilities, memory, and performance measures. |
| Business Capability | A stable business ability the Digital Procurement Company must perform. |
| SOP | Standard operating procedure that defines repeatable work. |
| Organizational Memory | Durable knowledge captured from decisions, workflows, procedures, documents, suppliers, context, outcomes, and learning. |
| AI reasoning | Structured reasoning applied to procurement work using context, evidence, SOPs, memory, and guardrails. |
| Executable workflow | A workflow that operationalizes SOPs, decisions, reasoning, or business processes. |
| Continuous learning | The feedback loop that improves memory, SOPs, workflows, KPIs, and future reasoning. |
Practice Terms¶
| Practice | Definition |
|---|---|
| Executive Office | The Practice responsible for coordination, approvals, briefings, and executive workflow. |
| Business Analysis | The Practice responsible for business fit, requirements, readiness, and opportunity assessment. |
| Compliance | The Practice responsible for eligibility, rules, submission discipline, and compliance guardrails. |
| Procurement Intelligence | The Practice responsible for opportunity intelligence, market context, and procurement insight. |
| Bid Management | The Practice responsible for bid planning, response coordination, and proposal execution. |
| Contract Delivery | The Practice responsible for delivery readiness, obligations, and contract execution context. |
| Supplier Marketplace | The Practice responsible for supplier records, supplier intelligence, sourcing, and supplier relationships. |
| Funding | The Practice responsible for funding context, opportunities, and finance-related support. |
| Learning | The Practice responsible for procurement education, SOP literacy, and capability development. |
| Business Intelligence | The Practice responsible for KPIs, reporting, analytics, and management insight. |
Digital Professional Terms¶
| Digital Professional | Definition |
|---|---|
| Ari | Chief Procurement Officer who coordinates the Digital Procurement Company. |
| Ava | Executive Assistant who organizes approvals, briefings, and executive workflow. |
| Orion | Business Analysis lead responsible for business fit and readiness analysis. |
| Lex | Compliance lead responsible for eligibility, compliance checks, and submission discipline. |
| Nova | Procurement Intelligence lead responsible for opportunity and market intelligence. |
| Atlas | Bid Management lead responsible for bid planning and proposal execution. |
| Forge | Contract Delivery lead responsible for delivery readiness and contract execution context. |
| Nexus | Supplier Marketplace lead responsible for supplier intelligence and sourcing context. |
| Beacon | Funding lead responsible for funding opportunities and finance-related context. |
| Sage | Procurement Academy lead responsible for learning and capability development. |
| Pulse | Business Intelligence lead responsible for KPIs, reporting, analytics, and performance insight. |
Headquarters Terms¶
| Headquarters area | Definition |
|---|---|
| Executive Office | The customer leadership area for briefings, approvals, priorities, and coordination. |
| Board Room | The strategic decision area for portfolio, risk, governance, and performance review. |
| War Room | The focused execution area for urgent or high-priority procurement work. |
| Proposal Studio | The bid response area for proposal creation, review, and submission readiness. |
| Compliance Centre | The compliance area for eligibility, evidence, risks, and submission requirements. |
| Marketplace | The supplier area for sourcing, supplier context, and supplier relationships. |
| Academy | The learning area for procurement training, SOP adoption, and capability growth. |
| Intelligence Centre | The insight area for procurement intelligence, analytics, and KPIs. |
Principle Terms¶
| Term | Definition |
|---|---|
| One Concept, One Owner | Each durable concept must have one accountable owner and one primary definition. |
| Architecture Mirror Principle | Software architecture must mirror organizational architecture. |
| Business first, technology second | Business value and operating model lead technology choices. |
| Evidence before opinion | Recommendations and decisions should be grounded in source data, context, memory, and reasoning. |
| Automation with accountability | Automation must have ownership, guardrails, review paths, and measurable outcomes. |
Capability Mapping Terms¶
Every capability must map to:
| Mapping element | Meaning |
|---|---|
| Practice | The business domain that owns the capability. |
| Digital Professional | The professional accountable for the work. |
| SOP | The procedure that governs execution. |
| KPI | The measure of performance or outcome. |
| Data | The evidence, state, or records required. |
| Business outcome | The value created for the customer. |
Scope¶
This document defines foundational terminology. It does not replace detailed standards, decision records, or future domain-specific glossaries.