Enterprise Intelligence Architecture — Canonical Definitions
The authoritative enterprise vocabulary for representation, memory, coordination, consequence and learning
Document type: Arqua Canonical Vocabulary
Status: Published canonical reference
Architecture version: Arqua Canonical Architecture v1.0
Vocabulary scope: Enterprise-wide
Last reviewed: 11 July 2026
Canonical definitions may be clarified without changing their architectural meaning. Any material change to scope, ownership, parentage or relationship requires a versioned architecture decision.
This page defines the enterprise-wide vocabulary used across the Arqua architecture corpus.
These definitions establish the common meaning of the constructs that connect operational reality, enterprise representation, institutional memory, runtime context, governed coordination, execution and learning.
Domain-specific definition pages inherit from this vocabulary and may add specialised terms, but must not redefine the enterprise-level concepts without an explicit versioned architecture decision.
Standard fields for each definition: Term, Category, Canonical definition, Purpose, What it is not, Inputs, Outputs, Where it sits, Canonical parent, Related constructs, Canonical statement.
Definitions
Enterprise Asset
Category: Enterprise resource
Canonical definition: Any enterprise-owned or enterprise-recognised resource, representation, capability, service, record, product, interface, model, event stream or knowledge artefact that may be governed, managed, protected or published.
Purpose: To distinguish enterprise resources from Published Enterprise Products.
What it is not: Not automatically admissible for Enterprise Intelligence and not automatically published.
Canonical statement: Enterprise assets may exist anywhere; only Published Enterprise Products participate in Enterprise Intelligence.
Accepted Enterprise Representation
Category: Governed representation state
Canonical definition: An enterprise representation that has been accepted by the appropriate Business Domain, Data Domain or recognised enterprise authority for a declared scope and purpose.
Purpose: To provide the authoritative basis from which publication may occur.
What it is not: Not automatically published and not automatically available for Runtime Context Assembly.
Canonical statement: Acceptance establishes authoritative basis; publication establishes governed participation.
Enterprise Participation
Category: Constitutional Function
Canonical definition: The constitutional function that establishes which enterprise representations possess governed standing to participate in Enterprise Intelligence.
Purpose: To create the boundary between enterprise content and Enterprise Intelligence.
What it is not: Not publication workflow, not a registry, not platform governance and not the source of enterprise authority.
Canonical statement: Enterprise Participation establishes participation; Enterprise Product Publication operationalises participation; authority remains with the enterprise.
Enterprise Product Publication
Category: Implementation mechanism
Canonical definition: The implementation mechanism through which Enterprise Participation is operationalised by establishing publication workflow, lifecycle, governance, approval, withdrawal, metadata, interfaces, quality and evidence.
Purpose: To turn accepted representations and governed capabilities into Published Enterprise Products.
What it is not: Not the constitutional responsibility and not the source of authority.
Canonical parent: Enterprise Participation
Canonical statement: Publication operationalises participation; it does not create authority.
Published Enterprise Product
Category: Governed participation product
Canonical definition: An enterprise representation that has been intentionally granted governed participation standing within Enterprise Intelligence.
Purpose: To define what may participate in Runtime Context Assembly and operational reasoning.
What it is not: Not arbitrary enterprise content and not authority by itself.
Inputs: Accepted enterprise representation or governed enterprise capability, publication authority, semantic definition, interface, lifecycle, governance and quality expectations.
Outputs: Governed participation standing and registry-discoverable product or service interface.
Canonical parent: Enterprise Participation
Canonical statement: Publication establishes governed participation; it does not create authority.
Publication Standing
Category: Participation state
Canonical definition: The governed status indicating that an enterprise representation or capability has been intentionally published for participation in Enterprise Intelligence.
Purpose: To separate publishable enterprise assets from products that may participate in Runtime Context Assembly.
What it is not: Not ownership, not authority and not execution permission.
Canonical statement: Publication Standing determines whether a product may participate; Runtime Context Assembly determines whether it is suitable for a specific Operational Intent.
Publication Authority
Category: Governance role
Canonical definition: The recognised Business Domain, Data Domain or enterprise authority responsible for approving whether an accepted representation or capability may be published as a governed Enterprise Product.
Purpose: To keep publication accountable to enterprise authority rather than platform custody.
What it is not: Not the creator of business authority and not a technology platform role.
Canonical statement: Publication Authority approves participation standing; it does not create the underlying authority of the representation.
Publication Withdrawal
Category: Lifecycle control
Canonical definition: The governed removal, suspension or retirement of Publication Standing for a Published Enterprise Product.
Purpose: To prevent products from continuing to participate after authority, quality, lifecycle, semantic validity or permitted-use conditions no longer support participation.
What it is not: Not deletion of the underlying enterprise asset and not erasure of institutional memory.
Canonical statement: Product Withdrawal removes participation standing while preserving reconstructability.
Knowledge Product
Category: Published Enterprise Product type
Canonical definition: A governed knowledge representation, document set, evidence collection, memory projection or explanatory artefact published for participation in Enterprise Intelligence.
Purpose: To make knowledge consumable under declared scope, semantics, provenance, lifecycle and quality expectations.
What it is not: Not every document, wiki page, file or knowledge-base entry.
Canonical statement: Knowledge becomes an Enterprise Product only when publication standing is established.
Service Product
Category: Published Enterprise Product type
Canonical definition: A governed enterprise capability exposed through a service interface and published for participation in Enterprise Intelligence.
Purpose: To allow capabilities such as Identity Resolution, Authority Resolution, Semantic Resolution, Context Qualification, Execution Admissibility, optimisation, location or business calculation services to participate in Runtime Context Assembly and operational reasoning.
What it is not: Not every API, connector, microservice or platform service.
Canonical statement: Enterprise Intelligence consumes both information products and enterprise capabilities.
Decision Product
Category: Published Enterprise Product type
Canonical definition: A governed decision logic, decision evidence, decision service or decision-support artefact published for participation in Enterprise Intelligence.
Purpose: To expose decision capability or decision evidence under explicit authority, scope, semantic definition, lifecycle and quality expectations.
What it is not: Not automatic execution authority and not a substitute for Execution Admissibility.
Canonical statement: Decision Products may support proposed action; they do not authorise consequence.
Semantic Product
Category: Published Enterprise Product type
Canonical definition: A governed semantic definition, ontology, vocabulary, semantic contract, mapping or meaning surface published for participation in Enterprise Intelligence.
Purpose: To expose accepted enterprise meaning through governed participation boundaries.
What it is not: Not every glossary term, ontology statement or metadata entry.
Canonical statement: Semantic Products preserve meaning only when publication standing, authority and lifecycle are explicit.
Event Product
Category: Published Enterprise Product type
Canonical definition: A governed operational event, event stream or event interface published for participation in Enterprise Intelligence.
Purpose: To expose current operational signals under explicit ownership, schema, semantic definition, provenance, lifecycle and quality expectations.
What it is not: Not every message, log, stream or notification.
Canonical statement: Event Products make operational change available for governed participation; they do not by themselves establish authority.
Enterprise Intelligence Architecture
Category: Enterprise reference architecture
Canonical definition: The architecture through which an institution represents operational reality, forms governable understanding, preserves institutional continuity, assembles runtime context, coordinates action, governs consequence and learns from outcomes.
Purpose: To preserve coherent institutional understanding and self-governance as the enterprise changes.
What it is not: Not a data platform, AI platform, metadata catalogue, ontology, operating model or control system in isolation.
Where it sits: The whole Arqua architecture.
Canonical parent: Arqua Canonical Architecture
Canonical statement: Enterprise Intelligence Architecture governs how an institution understands, decides, acts and learns without losing continuity.
Operational Reality
Category: Foundational condition
Canonical definition: The enterprise as it actually exists and operates, independently of any single model, database, document, ontology, report or institutional belief about it.
Purpose: To establish that institutional representations are always representations of reality, not reality itself.
What it is not: Not a system of record, digital twin, graph, data model or accepted narrative.
Outputs: Observable events, states, behaviours, relationships and evidence.
Canonical statement: Reality precedes representation.
Observed Evidence
Category: Evidential input
Canonical definition: The records, events, measurements, documents, assertions, behaviours, traces and observations through which aspects of operational reality become available for institutional interpretation.
Purpose: To provide traceable grounds for forming, validating or challenging institutional representations.
What it is not: Not automatically accepted truth and not merely raw data.
Inputs: Operational events, records, documents, communications, sensor observations, system behaviour and human assertions.
Outputs: Evidence available for interpretation and representation.
Canonical statement: Evidence makes reality observable but does not make meaning authoritative.
Operational Evidence
Category: Evidential input
Canonical definition: Provenance-bearing information capable of supporting or challenging a claim about operational reality.
Purpose: To provide accountable grounds for accepting, rejecting or revising an institutional representation.
What it is not: Not automatically accepted truth and not merely data because it exists.
Canonical statement: Operational evidence supports or challenges representation; it does not by itself create institutional acceptance.
System Model Foundation
Category: Representational substrate
Canonical definition: The governed representational substrate through which boundaries, subjects, identities, relationships, states, events, contexts, claims, evidence, representation types and projections become coherently expressible across the enterprise.
Purpose: To make operational reality contractably representable.
What it is not: Not a single canonical database schema, ontology, knowledge graph or industry data model.
Inputs: Observed evidence, domain knowledge, operational structures and institutional distinctions.
Outputs: Coherent representational structures available for semantic acceptance and projection.
Canonical statement: Semantic contracts require contractable representations; contractable representations require a System Model Foundation.
Enterprise Reality Representation Framework
Category: Representation framework
Canonical definition: The architectural framework defining how System Model Foundation primitives combine into coherent source, domain, cross-domain, enterprise and purpose-specific representations of operational reality.
Purpose: To define how operational evidence becomes governed institutional representation beneath Enterprise Representation Intelligence.
What it is not: Not a fourth operating capability, technology platform, ontology product, knowledge graph, universal data model, separate enterprise architecture or commercial service.
Inputs: System Model Foundation primitives, operational evidence, domain structures, relationships, states, events, contexts, claims and provenance.
Outputs: Coherent enterprise representations available for interpretation, governance, acceptance and memory.
Canonical parent: Enterprise Representation Intelligence
Canonical statement: Enterprise Reality Representation Framework defines the representational structure; Enterprise Representation Intelligence operates the representational lifecycle.
Enterprise Representation Intelligence
Category: Continuously operating enterprise capability
Canonical definition: The continuously operating capability that discovers, interprets, reconciles, validates, governs and evolves the institution’s representations of operational reality.
Purpose: To keep institutional understanding aligned with changing operational reality.
What it is not: Not metadata enrichment, ontology management, knowledge-graph storage, AI inference or data quality in isolation.
Inputs: Observed evidence, existing representations, semantic policies, behavioural observations, outcomes and institutional decisions.
Outputs: Proposed representations, validated representations, representation challenges, accepted revisions and memory updates.
Where it sits: Between observed evidence and accepted institutional representation.
Canonical parent: Enterprise Intelligence Architecture
Related constructs: System Model Foundation, Intelligent Semantic Architecture, Institutional Memory, Representation Graph and Behaviour Validation.
Canonical statement: Enterprise Representation Intelligence continuously maintains institutional understanding through governed representation.
Accepted Institutional Representation
Category: Governed representation state
Canonical definition: A representation of operational reality that has passed the required institutional processes of interpretation, evidence assessment, semantic governance, authority and acceptance for a declared scope and purpose.
Purpose: To distinguish institutionally relied-upon meaning from raw evidence, inference, opinion and unaccepted model output.
What it is not: Not immutable truth, raw metadata, an AI-generated claim or an ontology statement merely because it exists.
Inputs: Candidate representations, evidence, governance decisions and acceptance authority.
Outputs: Institutionally reliable meaning available for memory, contracting and runtime use.
Canonical statement: Representation becomes institutional only when the institution accepts responsibility for relying upon it.
Enterprise Representation
Category: Institutional representation
Canonical definition: A structured institutional account of some bounded aspect of operational reality, expressed through subjects, identities, relationships, states, events, contexts, claims and evidence.
Purpose: To distinguish represented operational reality from raw data, semantic meaning, storage, ontology, knowledge graph or institutional memory.
What it is not: Not data, storage, ontology, semantic model, knowledge graph, digital twin, data product or institutional memory in isolation.
Canonical statement: Enterprise representation is the structured account through which operational reality becomes institutionally interpretable.
Institutional Memory
Category: Continuity capability
Canonical definition: The governed continuity of accepted institutional understanding, evidence, decisions, relationships, states and outcomes preserved across time, organisational change and technology evolution.
Purpose: To prevent the institution from repeatedly losing, fragmenting or silently rewriting what it knows.
What it is not: Not storage technology, a knowledge base, document repository, graph database, vector store or data lake in isolation.
Inputs: Accepted institutional representations, provenance, decisions, outcomes and revisions.
Outputs: Durable and reconstructable institutional understanding.
Canonical statement: The defining characteristic of institutional memory is continuity, not storage.
Semantic Governance Operating Model
Category: Institutional governance capability
Canonical definition: The operating model through which enterprise meaning is proposed, challenged, accepted, owned, versioned, evolved and retired.
Purpose: To establish institutional responsibility for meaning.
What it is not: Not glossary administration, data stewardship alone or a governance committee without operational authority.
Outputs: Accepted semantic architecture and governed semantic change.
Canonical statement: Meaning becomes institutional through governed acceptance.
Semantic Contract Surface
Category: Governed interoperability boundary
Canonical definition: The governed boundary through which accepted semantic architecture is exposed, bound and preserved across organisational, technical, analytical, operational and AI consumption contexts.
Purpose: To ensure accepted meaning travels without uncontrolled reinterpretation.
What it is not: Not an API alone, schema registry, ontology endpoint or data contract in isolation.
Inputs: Accepted semantic architecture, declared consumer purpose, permitted use, quality and governance obligations.
Outputs: Governed consumer binding.
Canonical statement: The Semantic Contract Surface preserves accepted meaning as it crosses boundaries.
Enterprise Memory Product
Category: Governed consumable representation
Canonical definition: A bounded, governed and reusable projection of institutional memory exposed for a declared operational, analytical, decision, workflow or AI purpose.
Purpose: To make institutional memory consumable without exposing the entire representational substrate.
What it is not: Not every table, file, topic, API, graph projection or document collection.
Inputs: Accepted institutional representation, semantic contract, provenance, purpose, ownership and permitted use.
Outputs: Purpose-bound and governed memory consumption.
Canonical statement: A memory product is a governed projection of institutional understanding.
Runtime Context Assembly
Category: Constitutional Mechanism
Canonical definition: The constitutional mechanism that forms and qualifies purpose-specific operational understanding from accepted enterprise representations for a defined Operational Intent.
Purpose: To produce Qualified Operational Understanding that people, systems, workflows and AI may rely upon for coordination, decisioning or admissibility evaluation without centralising institutional understanding.
What it is not: Not retrieval alone, prompt construction, static context storage, GraphRAG, data federation or a centralised knowledge store.
Inputs: Operational Intent, accepted enterprise representations, institutional memory, current evidence, actor identity, authority, policy, semantic contracts and operational state.
Outputs: Qualified Operational Understanding and a Qualified Context Manifest.
Canonical parent: The Constitutional Architecture of Enterprise Intelligence
Canonical statement: Runtime Context Assembly forms and qualifies operational understanding; it does not merely retrieve context and does not authorise execution.
Operational Intent
Category: Runtime intent boundary
Canonical definition: The explicit statement of the purpose for which operational understanding is being assembled, including the reasoning, decision, workflow or action boundary within which that understanding may be used.
Purpose: To bound context formation by purpose, actor, authority, policy, freshness, completeness, uncertainty and qualification threshold.
What it is not: Not a generic search query, prompt, user request or implementation instruction.
Outputs: Runtime assembly requirements and qualification criteria.
Canonical parent: Runtime Context Assembly
Canonical statement: Runtime Context Assembly begins with Operational Intent, not a generic information request.
Candidate Operational Understanding
Category: Runtime assembly state
Canonical definition: The assembled but not yet qualified operational understanding formed from accepted enterprise representations for a defined Operational Intent.
Purpose: To separate formation from institutional reliance.
What it is not: Not Qualified Operational Understanding and not evidence that reliance is admissible.
Inputs: Accepted enterprise representations, institutional memory, current evidence, semantic contracts, policy and authority context.
Outputs: Assembly Manifest and assembled context available for qualification.
Canonical parent: Runtime Context Assembly
Canonical statement: An enterprise may assemble context without yet having sufficient basis to rely upon it.
Assembly Manifest
Category: Runtime evidentiary artefact
Canonical definition: The record of the representations, services, authorities, policies, semantic versions, evidence, provenance and boundaries used to assemble Candidate Operational Understanding.
Purpose: To make context formation traceable before qualification.
What it is not: Not proof that the assembled understanding is complete, fresh, authoritative, policy-compliant or admissible.
Outputs: Evidence for Context Qualification.
Canonical parent: Runtime Context Assembly
Canonical statement: The Assembly Manifest records what was assembled; it does not by itself establish admissible reliance.
Context Qualification
Category: Runtime qualification process
Canonical definition: The evaluation of Candidate Operational Understanding against Operational Intent before that understanding may be relied upon for reasoning, coordination, decisioning or admissibility evaluation.
Purpose: To determine whether assembled understanding is complete, fresh, semantically consistent, authoritative, provenance-bearing, policy-compliant and sufficient for the intended use.
What it is not: Not retrieval scoring, model confidence, human approval alone or execution authorisation.
Inputs: Candidate Operational Understanding, Assembly Manifest, Operational Intent and qualification criteria.
Outputs: Qualified Context Manifest and qualification outcome.
Canonical parent: Runtime Context Assembly
Canonical statement: Formation does not establish reliance; qualification establishes the reliance state of assembled context. Context Qualification reliance states are distinct from the canonical Execution Admissibility typed outcomes and do not determine execution admissibility.
Qualified Context Manifest
Category: Runtime evidentiary artefact
Canonical definition: The evidentiary record describing the qualified operational understanding, the qualification process applied and the resulting qualification outcome.
Purpose: To support replayability, governance, AI explainability, operational traceability and review.
What it is not: Not execution authority, legal assurance or a replacement for the Architecture of Record.
Inputs: Context Qualification result, qualification criteria, Operational Intent and supporting evidence.
Outputs: Qualification evidence for coordination, decisioning or admissibility evaluation.
Canonical parent: Runtime Context Assembly
Canonical statement: The Qualified Context Manifest records why operational understanding may be relied upon, under what conditions, or why reliance is withheld. Reliance states are distinct from the canonical Execution Admissibility typed outcomes.
Qualified Operational Understanding
Category: Runtime understanding state
Canonical definition: Purpose-specific operational understanding that has been assembled from accepted enterprise representations and qualified against the Operational Intent.
Purpose: To provide a bounded, traceable and qualified basis for coordination, decisioning, AI participation or admissibility evaluation.
What it is not: Not institutional memory, not execution authority and not automatically accepted revised representation.
Inputs: Candidate Operational Understanding and Context Qualification.
Outputs: Operationally usable understanding for people, systems, workflows, AI and admissibility evaluation.
Canonical parent: Runtime Context Assembly
Canonical statement: Qualified Operational Understanding may support action; it does not itself authorise execution.
Representation Revision
Category: Governed learning process
Canonical definition: A governed change to institutional representation arising from new evidence, correction, reinterpretation, outcome learning or changed operational reality.
Purpose: To allow institutional understanding to change without silently rewriting prior meaning, provenance or accountability.
What it is not: Not automatic model retraining, uncontrolled ontology change or direct replacement of institutional truth by new data.
Canonical statement: Representation revision changes future understanding while preserving reconstructability of prior representation.
Enterprise Control Plane
Category: Distributed continuity and runtime governance architecture
Canonical definition: The distributed architecture that preserves identity, meaning, authority, provenance, permitted use, lineage, conformance, accountability and reconstructability as accepted architecture becomes implementation, runtime operation, decision, action, consequence and revision.
Purpose: To preserve institutional continuity across the transition from accepted understanding to operational action.
What it is not: Not a single software platform, orchestration engine, policy tool, AI gateway or centralised command system.
Inputs: Accepted architecture, institutional memory, authority, controls, implementation state and runtime evidence.
Outputs: Conformant operational implementation and governed runtime continuity.
Canonical statement: The Enterprise Control Plane preserves institutional continuity as architecture becomes action.
Enterprise Coordination Fabric
Category: Operational coordination environment
Canonical definition: The governed environment through which people, systems, workflows, services and intelligent agents exchange context, coordinate work and participate in shared enterprise outcomes.
Purpose: To enable distributed action without losing semantic, authority or accountability coherence.
What it is not: Not an integration platform, service bus, event mesh or multi-agent framework in isolation.
Inputs: Governed context, actor identity, authority, work state, coordination intent and policy.
Outputs: Coordinated enterprise activity.
Canonical statement: Enterprise coordination is the governed movement of context, intent and work across accountable actors.
Agent Control Plane
Category: Applied runtime control architecture
Canonical definition: The applied control architecture that governs enterprise agents through identity, registry, ownership, authority, permitted use, runtime enforcement, observability, evaluation, monitoring, security, cost control, lifecycle management and offboarding.
Purpose: To make AI-enabled runtime actors governable participants in enterprise operation.
What it is not: Not the whole Enterprise Control Plane, not an agent framework and not an AI observability dashboard.
Canonical parent: Enterprise Control Plane
Canonical statement: No agent without identity, owner, authority, scope, monitoring and offboarding.
Governed Coordination
Category: Runtime operating state
Canonical definition: The condition in which people, systems, workflows and agents coordinate using accepted meaning, valid authority, traceable context and enforceable operating constraints.
Purpose: To distinguish legitimate enterprise coordination from technically possible interaction.
Outputs: Proposed decisions, workflows and actions suitable for admissibility evaluation.
Canonical statement: Coordination becomes governed when meaning, authority, purpose and accountability remain intact across actors.
Execution Admissibility
Category: Consequence-boundary determination
Canonical definition: The institutional determination that sufficient authority, context, constraints, state and evidence exist for a proposed consequence-bearing action to execute at T=0. Resolution produces one canonical typed outcome: permitted, conditional, escalated, prevented or unresolved.
Purpose: To prevent technically executable actions from binding consequence without proven institutional integrity.
What it is not: Not decision approval, retrospective audit, model confidence or human review in isolation.
Canonical parent: Execution Admissibility Architecture
Canonical statement: No consequence-bearing state transition without proven integrity at the commit boundary.
Operational Consequence
Category: Bound institutional outcome
Canonical definition: The durable institutional outcome produced when an authorised action changes rights, obligations, state, access, ownership, records, infrastructure, funds or other consequence-bearing conditions.
Purpose: To identify the point at which action becomes institutionally real.
What it is not: Not an intention, recommendation, prediction or simulated output.
Canonical statement: Consequence is the durable institutional state created when execution binds.
Outcome Evidence
Category: Learning input
Canonical definition: The observable results, effects, state changes, exceptions and consequences produced by action and returned as evidence for evaluation.
Purpose: To determine whether institutional understanding, context, coordination and action produced the intended result.
What it is not: Not automatically a lesson, causal proof or authorised representation revision.
Outputs: Evidence available for validation, challenge and learning.
Canonical statement: Outcomes generate evidence; governance determines what the institution learns from it.
Behaviour Validation
Category: Representation assurance capability
Canonical definition: The continuous comparison of accepted institutional representations against observed data, events, relationships, behaviours and outcomes to determine whether those representations remain valid.
Purpose: To identify representational drift, contradiction, incompleteness and semantic decay.
What it is not: Not model evaluation, data quality checking or anomaly detection alone.
Outputs: Validation evidence, representation challenges and proposed revisions.
Canonical statement: Institutional understanding must remain testable against operational behaviour.
Representation Evolution
Category: Governed learning process
Canonical definition: The controlled revision, extension, supersession or retirement of institutional representations in response to new evidence while preserving provenance, continuity and prior interpretive states.
Purpose: To allow the institution to learn without silently rewriting its history.
What it is not: Not automatic model retraining, uncontrolled ontology change or direct rewriting of institutional truth by outcome data.
Inputs: Outcome evidence, behavioural validation, semantic challenge and authorised governance decisions.
Outputs: Revised and reaccepted institutional representation.
Canonical statement: Learning changes representation through governed revision, not automatic overwrite.