Runtime Context Assembly

Architectural Category: Runtime architectural mechanism

Canonical parent: Enterprise Intelligence Architecture

Vocabulary reference: Enterprise Intelligence Architecture — Canonical Definitions

Forming and Qualifying Operational Understanding

Arqua Architecture Paper

Version 2.0 | July 2026

Mark Tovey, Arqua Pty Ltd

Runtime Context Assembly constructs the institutional context required for a particular operational intent, drawing together the relevant meaning, state, authority, evidence, constraints and temporal conditions for that use.

Executive Summary

Runtime Context Assembly is not defined as a retrieval pattern.

It is the architectural mechanism responsible for forming qualified operational understanding at runtime.

Runtime Context Assembly is responsible for:

• forming purpose-specific Candidate Operational Understanding;
• qualifying that understanding before institutional reliance; and
• enabling distributed Enterprise Intelligence without requiring centralised information.

Retrieval, federation, APIs, Kafka, MCP and platform technologies are implementation mechanisms. They are not the architectural responsibility itself.

The responsibility is not to discover information wherever it happens to sit. The responsibility is to form and qualify purpose-specific operational understanding from accepted enterprise representations exposed through Published Enterprise Products, so that people, applications and artificial intelligence can reason, decide and coordinate on a bounded, qualified basis. Qualification for reliance is not execution authorisation.

Public Responsibility anchors

Runtime Context Assembly currently exposes two stable public Responsibility anchors:

ARQ-RESP-RCA-001 — Purpose-Specific Context Formation & Cross-Source Composition

For a declared enterprise purpose, Context Formation assembles the candidate operational understanding required for that purpose from eligible participating representations, products and services while preserving sufficient identity, scope and provenance.

Formation ≠ Qualification.

A successful query, retrieval, federation, agent-tool call or multi-source composition does not by itself establish that the resulting context is fit for institutional reliance.

ARQ-RESP-RCA-002 — Purpose-Relative Context Qualification for Bounded Reliance

Context Qualification evaluates Candidate Operational Understanding against the requirements applicable to its declared purpose before that understanding is relied upon institutionally.

Relevant concerns may include completeness within scope, freshness/currentness, semantic consistency, applicable authority, provenance, constraints, uncertainty and sufficiency for intended use.

Qualification ≠ Execution Admissibility.

Qualified context may inform a proposed action. It does not itself authorise consequence-bearing execution.

Persistent-agent interpretation

Persistent agents make this separation more important.

OpenAI's dots capability provides a current example: an always-on agent may retain feedback-informed state, use connected tools, operate through its own cloud computer and browser, handle recurring work and continue toward goals over time.

Those capabilities can participate in Context Formation. They do not make retained context perpetually valid.

For a later purpose or action:

persistent memory ≠ current qualified context

The relevant context may need to be reassembled, refreshed or requalified where purpose, authority, source state, permissions, policy, evidence or other material conditions have changed.

Provider capability evidence does not establish that dots, or any other agent runtime, implements Runtime Context Assembly or Context Qualification in full.

Architectural Thesis

Enterprise Intelligence does not require institutional understanding to be centralised.

It requires accepted enterprise representations to be capable of forming qualified operational understanding whenever and wherever the enterprise must reason, decide or act.

Runtime Context Assembly is the architectural mechanism responsible for this capability.

Architectural Definition

Runtime Context Assembly is the architectural mechanism that receives an Intent Scope, selects Published Enterprise Products and constructs Qualified Operational Understanding through Context Qualification for the declared enterprise purpose. Its assembly activity forms Candidate Operational Understanding; that understanding becomes qualified for bounded reliance only when the applicable qualification requirements are satisfied. It does not authorise execution.

Accepted representations provide the authoritative basis.

Published Enterprise Products provide governed participation.

Intent is a first-class architectural element within the System Model Foundation. Intent Scope is the derived operational boundary for operational understanding.

The architectural responsibility is not to consume enterprise content wherever it happens to sit. Runtime Context Assembly assembles only the context required by the active Intent Scope.

The emphasis is deliberate.

Runtime Context Assembly forms and qualifies.

It does not merely discover and retrieve.

Discovery and retrieval may occur during implementation. They do not define the architectural responsibility.

Standard Architectural Mechanism Specification

Asset Traceability

Runtime Context Assembly consumes Published Enterprise Products within an active Intent Scope.

Its context-formation activity produces Candidate Operational Understanding and an Assembly Manifest.

Context Qualification evaluates that candidate against Operational Intent and the applicable qualification criteria. It records the qualification outcome in a Qualified Context Manifest. Qualified Operational Understanding results only where the evaluation supports reliance for the declared use; otherwise the reasons for withholding reliance remain explicit.

Qualified Operational Understanding may support Enterprise Coordination, decisioning, AI participation and Execution Admissibility evaluation. It does not itself authorise execution.

Context Qualification remains a distinct responsibility within the overall Runtime Context Assembly mechanism. Separating formation from qualification does not reduce RCA to retrieval or move qualification outside its architectural scope.

Intent Scope

An Intent Scope defines the minimum authoritative operational understanding required to achieve a specific enterprise purpose. It establishes the operational boundary within which Runtime Context Assembly selects, assembles and qualifies enterprise representations.

Intent Scope is derived from Intent, a first-class architectural element within the System Model Foundation. Intent Scope is a derived boundary, not a representation primitive.

Intent Scope exists because enterprises do not require complete knowledge of reality.

They require sufficient understanding to perform a specific purpose.

Operational understanding is therefore assembled relative to an Intent Scope rather than attempting enterprise-wide completeness.

Context Sufficiency replaces Context Completeness.

Intent Scope is the boundary between enterprise knowledge and operational understanding.

It determines:

• which Published Enterprise Products may participate;
• which Projection Specifications are required;
• which semantic relationships are relevant;
• which qualification policies apply; and
• what constitutes sufficient operational understanding.

Enterprise Product Publication establishes what may participate in Enterprise Intelligence.

Intent Scope establishes what must be assembled for a specific enterprise purpose.

Why Runtime Context Assembly Exists

Institutional Memory preserves accepted understanding over time.

Operational reality continues to change.

People, systems, workflows and AI do not need all institutional memory at once. They require qualified operational understanding for a specific purpose, actor, authority, decision, workflow or proposed action.

Runtime Context Assembly exists because qualified operational understanding must be assembled for the moment of use.

It must be bounded.

It must be traceable.

It must be qualified.

It must be suitable for the operational intent for which it will be used.

Without this mechanism, enterprises either centralise information in ways that weaken operational fidelity or allow systems to assemble context informally without sufficient evidence, authority or qualification.

Intent

Intent represents the purpose an enterprise seeks to achieve. Within Arqua, it provides the architectural purpose for assembling and qualifying enterprise understanding.

Runtime Context Assembly does not create Intent. Intent belongs to the System Model Foundation as a first-class architectural element.

Runtime Context Assembly receives the Intent Scope derived from that Intent rather than beginning from generic information requests.

Operational Intent bounds the applicable requirements for:

• scope;
• authority;
• policy;
• required representations;
• freshness;
• completeness within the declared scope;
• acceptable uncertainty; and
• qualification threshold.

Intent declares purpose; it does not create authority or override enterprise policy. Execution Admissibility remains responsible for the separate determination concerning a proposed consequence-bearing action.

Intent prevents context from becoming an unbounded information bundle.

It establishes why understanding is being formed, who or what may rely upon it, what action or decision boundary it may support, and what qualification standard must be satisfied before institutional reliance is permitted.

Intent declares the enterprise purpose.

Intent Scope translates that purpose into the minimum authoritative operational understanding required for runtime assembly.

Runtime Lifecycle

Intent Scope
↓
Published Enterprise Products
↓
Projection Specifications
↓
Context Assembly Library
↓
Candidate Operational Understanding
↓
Context Qualification
↓
Qualified Operational Understanding

This lifecycle describes formation and qualification within Runtime Context Assembly, rather than a retrieval workflow. Intent Scope, Published Enterprise Products, Projection Specifications and the Context Assembly Library identify scope, participating inputs and supporting implementation artefacts; they are not all equivalent runtime stages.

It begins with the active Intent Scope.

It selects Published Enterprise Products and Projection Specifications required by that scope.

It uses the Context Assembly Library to form Candidate Operational Understanding.

It records that assembly in an Assembly Manifest.

It then qualifies the candidate understanding against the Intent Scope.

Only after qualification does the output become Qualified Operational Understanding.

Context Sufficiency

Context Sufficiency is the minimum qualified operational understanding required for a specific enterprise intent.

Within Arqua, the objective is not to assemble all available information. It is to assemble sufficient understanding for the declared purpose under the applicable authority, policy, evidence and temporal conditions.

Context Sufficiency is a purpose-relative architectural objective. Completeness is assessed within the declared Intent Scope, not against all enterprise knowledge.

Context Qualification evaluates whether the assembled understanding meets those requirements for reliance. A satisfactory context qualification outcome does not establish that a proposed action is safe or authorised to execute.

Enterprise Registry

Runtime Context Assembly depends on an Enterprise Registry.

The Enterprise Registry is not merely a data product catalogue.

It makes published enterprise representations and capabilities discoverable for forming qualified operational understanding, including:

• source-aligned products;
• semantic services;
• reasoning services;
• policy services;
• optimisation services;
• simulation services;
• digital twins; and
• AI capabilities.

The registry enables Runtime Context Assembly to identify which accepted enterprise representations and supporting services may participate in a particular operational intent.

The Enterprise Registry does not centralise the enterprise.

It makes distributed enterprise capability discoverable, governable and composable.

Assembly Manifest

The Assembly Manifest is the record of the representations, services, authorities, policies and evidence used to assemble Candidate Operational Understanding.

It records:

• enterprise representations used;
• semantic versions;
• products and services;
• policies applied;
• authorities consulted;
• timestamps;
• evidence;
• provenance; and
• retrieval boundaries.

The Assembly Manifest is an intermediate runtime evidentiary artefact.

It provides evidence of formation, not a determination that the understanding is qualified for reliance.

It records what was assembled and under which conditions. It does not by itself establish that the assembled context is complete, fresh, semantically consistent, authoritative, policy-compliant or admissible for the requesting operational intent.

Context Qualification

Context Qualification is the evaluation of Candidate Operational Understanding against Operational Intent before that understanding may be relied upon for reasoning, coordination, decisioning or admissibility evaluation.

Qualification criteria include:

• completeness within the declared Intent Scope;
• freshness;
• semantic consistency;
• authority applicable to the intended use;
• provenance;
• policy compliance;
• confidence and acceptable uncertainty; and
• sufficiency for the intended use.

These criteria concern reliance on assembled understanding. They do not determine execution admissibility.

Qualification is Arqua’s architectural discipline for evaluating assembled operational context against the heterogeneous conditions applicable to its intended institutional use. Those conditions may include authority, policy, evidence, governance, operational state, temporal conditions, professional standards, risk and domain-specific requirements.

Qualification does not replace domain-specific rules. It provides architecture through which those rules and conditions can be applied coherently to operational context.

Formation does not establish institutional reliance.

Qualification establishes the reliance state of assembled context for the declared purpose and conditions; it is not blanket permission to rely or to execute.

This distinction is central to Version 2.0.

An enterprise may assemble context without having sufficient basis to rely upon it. Runtime Context Assembly therefore separates formation from qualification. The candidate context becomes institutionally usable only when it satisfies the requirements of the operational intent.

Qualified Context Manifest

The Qualified Context Manifest is the evidentiary record describing the operational understanding evaluated, the qualification process applied and the resulting qualification outcome. It records the basis and conditions for reliance or why reliance is withheld; it is not an execution authorisation artefact.

It supports:

• replayability;
• audit;
• governance;
• AI explainability;
• regulatory evidence; and
• operational traceability.

Context Qualification reliance states are distinct from the canonical Execution Admissibility typed outcomes. A qualification outcome concerns whether and under what conditions assembled understanding may be relied upon. It must not be interpreted as an Execution Admissibility outcome or converted into execution permission. This public paper does not define a new typed qualification-outcome enumeration.

The Qualified Context Manifest records why the operational understanding may be relied upon, under what conditions, or why reliance must be prevented, escalated or treated as unresolved.

Relationship to the Enterprise Representation Architecture

Runtime Context Assembly operates over Enterprise Representations rather than heterogeneous operational schemas.

Enterprise Representations expose operational meaning through governed semantics, identities, structures and contracts.

Enterprise Projections allow representations from different domains to participate in enterprise reasoning without requiring a centralised physical model.

The System Model Foundation provides the structural representation foundation that makes these representations intelligible and composable.

Operational Systems
↓
Source-Aligned Enterprise Representations
↓
Enterprise Projections
↓
Accepted Enterprise Representations
↓
Enterprise Product Publication
↓
Published Enterprise Products
↓
Runtime Context Assembly
↓
Qualified Operational Understanding

Runtime Context Assembly therefore depends upon the representational architecture beneath it.

It does not repair incoherent representation at runtime.

It constructs qualified operational understanding from Published Enterprise Products whose underlying representations already possess sufficient structural consistency, meaning, evidence, provenance and institutional standing.

Platform Independence

Runtime Context Assembly standardises the formation of qualified operational understanding rather than the location of enterprise information.

Technology platforms, transport mechanisms, service surfaces and storage locations may implement Runtime Context Assembly.

They do not define it.

Runtime Context Assembly is defined by the architectural responsibility to form and qualify operational understanding from accepted enterprise representations exposed through Published Enterprise Products within the active Intent Scope.

Architectural Principle

Runtime Context remains transient while institutional understanding remains persistent.

The distinction is critical.

• Institutional Memory preserves accepted institutional understanding over time.
• Runtime Context is the bounded and transient assembly of intent-scoped understanding for a specific operational intent.
• Qualified Operational Understanding is runtime context that has been evaluated against the operational intent and qualified for institutional reliance.

Runtime Context should not silently become Institutional Memory.

Qualified Operational Understanding may produce evidence, decisions, outcomes or revisions that later affect Institutional Memory through governed learning. But the runtime context itself remains purpose-specific, bounded and transient.

Strategic Implications

Runtime Context Assembly provides the architectural rationale for:

• source-aligned data products;
• Enterprise Projections;
• distributed Enterprise Intelligence;
• operational AI participation; and
• technology-independent implementation patterns.

Enterprise Intelligence no longer depends upon consolidating enterprise information into a single platform.

Instead, qualified operational understanding is formed from distributed accepted enterprise representations.

This matters for enterprises operating across multiple domains, products, services, workflows and AI capabilities.

The strategic implication is not that every implementation environment must become one system.

The implication is that every product or capability that participates in Enterprise Intelligence must expose representations, semantics, contracts, authority, evidence and policy conditions sufficient for qualified operational understanding to be formed at runtime.

Enterprise Product Publication establishes which products or capabilities may participate. Runtime Context Assembly evaluates their suitability for a specific Operational Intent.

What Runtime Context Assembly Does

Runtime Context Assembly:

• starts with Operational Intent;
• resolves identity and authority;
• derives or receives the active Intent Scope;
• identifies the accepted representations and governed enterprise capabilities required by that scope;
• selects Published Enterprise Products and Projection Specifications required by that scope;
• resolves semantics, policy and contracts;
• assembles Candidate Operational Understanding;
• records the Assembly Manifest;
• qualifies the candidate understanding against the active Intent Scope;
• records the Qualified Context Manifest; and
• delivers Qualified Operational Understanding for reasoning, coordination or action.

What Runtime Context Assembly Does Not Do

Runtime Context Assembly is not a data retrieval layer.

It is not a search interface.

It is not a data federation product.

It is not a centralised knowledge store.

It is not a replacement for Institutional Memory.

It is not a substitute for the System Model Foundation.

It does not create institutional truth.

It does not authorise execution.

It does not remove human or organisational accountability.

It does not assemble all available enterprise information.

It constructs qualified operational understanding from accepted enterprise representations for a defined Intent Scope. Different institutional uses invoke different conditions of relevance, applicability, authority, scope and temporal effect. Runtime Context Assembly provides an architectural mechanism for assembling those conditions into usable operational context.

Relationship to AI and Agents

AI systems and autonomous agents require bounded operational understanding.

If AI receives unqualified context, it may reason fluently over incomplete, stale, unauthorised or policy-invalid information.

Runtime Context Assembly provides the architectural mechanism through which AI and agents receive qualified operational understanding rather than arbitrary retrieved information.

This does not make AI accountable.

It does not grant autonomous execution authority.

It provides the qualified understanding required for AI participation to remain bounded, explainable, traceable and subject to institutional control.

Relationship to Execution Admissibility

Runtime Context Assembly forms and qualifies operational understanding.

Execution Admissibility determines whether proposed action may bind institutional consequence.

These responsibilities are related but distinct.

Qualified Operational Understanding may support an admissibility decision.

It does not itself authorise execution.

Execution Admissibility still evaluates whether sufficient authority, state, context, constraints, risk resolution and evidence exist at the point where consequence may bind.

Qualified Operational Understanding becomes one input into the Execution Admissibility Service.

SCIA Runtime consumes Qualified Operational Understanding but does not construct it.

Runtime Context Assembly is coordinated by the Enterprise Control Plane. It is not the Enterprise Control Plane itself.

Architectural Relationships

Enterprise Coherence

Runtime Context Assembly supports contextual coherence by forming and qualifying understanding for a defined Operational Intent, with authority, policy, provenance and relevant limitations made explicit. Enterprise Coherence is used here as an Arqua analytical framing, not a universal guarantee.

System Model Foundation

Runtime Context Assembly depends on the System Model Foundation because purpose-specific understanding can only be composed reliably when enterprise representations are structurally intelligible and when Intent is treated as a foundational primitive rather than an external runtime invention.

Enterprise Representation Intelligence

Enterprise Representation Intelligence forms and evolves enterprise representations and supports their governed evaluation and acceptance. Runtime Context Assembly consumes representations carrying the required acceptance and publication standing to construct qualified operational understanding for a specific runtime purpose.

Institutional Memory

Institutional Memory preserves accepted understanding and its evidentiary and revision history over time. Runtime Context Assembly draws on relevant memory projections and current accepted representations through governed Published Enterprise Products; preservation alone does not confer publication standing or suitability for the current Intent Scope.

Architecture of Record records standing, applicability and relevant boundaries. It is not the memory store or the context-assembly mechanism. Runtime Context Assembly must not silently promote a retrieved historical representation to current reliance or turn transient context into accepted Institutional Memory.

Enterprise Product Publication

Enterprise Product Publication establishes which accepted enterprise representations and enterprise capabilities are intentionally published as governed Enterprise Products for participation in Enterprise Intelligence.

Runtime Context Assembly consumes Published Enterprise Products rather than arbitrary enterprise content.

Publication establishes governed participation; it does not create authority.

Intent Scope determines which Published Enterprise Products must be assembled to produce sufficient operational understanding for a specific purpose.

Enterprise Coordination

Enterprise Coordination depends on Qualified Operational Understanding so that people, systems, workflows, services and agents coordinate through accepted meaning, valid authority and traceable context.

Enterprise Control Plane

The Enterprise Control Plane coordinates Runtime Context Assembly as one runtime responsibility among peer services, without becoming a sequential processing stage.

Runtime Context Assembly is not the Enterprise Control Plane itself.

The Enterprise Control Plane preserves continuity across Runtime Context Assembly by coordinating identity, meaning, authority, provenance, permitted use, lineage, conformance, accountability and reconstructability without absorbing Runtime Context Assembly’s responsibility.

Execution Admissibility

Execution Admissibility uses qualified operational understanding as part of the evidence base for determining whether proposed action may bind institutional consequence.

Outcome Learning

Outcome Learning receives evidence from operational action and consequence. It may challenge or revise institutional representations, but only through governed learning rather than silent runtime overwrite.

Unique Architectural Responsibility

Runtime Context Assembly owns a distinct architectural responsibility within Enterprise Intelligence Architecture:

It constructs qualified operational understanding for a defined operational intent.

It does not preserve memory.

It does not form enterprise representation.

It does not determine publication standing.

It does not govern continuity across the whole architecture.

It does not determine whether execution may bind.

It makes accepted enterprise understanding operationally available, qualified and bounded for runtime reasoning, coordination and action.

It makes accepted enterprise understanding operationally available only within the boundary of the active Intent Scope.

Implementation Patterns

Practical implementation guidance is maintained separately in the Enterprise Implementation Patterns library.

The preferred applied implementation pattern beneath Runtime Context Assembly is the Context Assembly Library. It defines reusable intent-scoped assembly definitions, projection specifications, semantic bindings and qualification templates that enable Runtime Context Assembly to consistently construct Qualified Operational Understanding from Published Enterprise Products.

The Business Domain Execution Pattern shows one way Runtime Context Assembly is realised inside a consuming Business Domain without making that domain the owner of enterprise data.

Related Reference Architectures

• Enterprise Participation Reference Architecture — Operational Context Assembly produces Qualified Operational Understanding consumed through Enterprise Participation.

Boundary Statement

This paper describes an architectural mechanism within Enterprise Intelligence Architecture.

It does not assert legal compliance, regulatory certification, operational assurance, technology implementation or automated decision authority.

Human and organisational accountability remains with the institution applying the architecture.

Conclusion

Enterprise Intelligence does not require institutional understanding to be centralised.

It requires accepted enterprise representations to be capable of forming qualified operational understanding whenever and wherever the enterprise must reason, decide or act.

Runtime Context Assembly is the architectural mechanism through which that understanding is assembled, qualified and made operationally available.

Document Status: Public Architecture Paper

Publication Date: 2026

Version: 2.0

Last Updated: 11 September 2026

Owner: Arqua Pty Ltd

Author: Mark Tovey

Portfolio: Enterprise Intelligence Architecture

Architecture role: Runtime architectural mechanism

This paper forms part of the Arqua Enterprise Intelligence Architecture portfolio. It should be read together with the current canonical and reference architecture sources referenced throughout this portfolio.

© 2025–Present Arqua Pty Ltd. All rights reserved.

This publication forms part of the Arqua Enterprise Intelligence Architecture portfolio.

No part of this publication may be reproduced, redistributed, adapted, republished or incorporated into derivative works without the prior written permission of Arqua Pty Ltd, except for brief quotations used with appropriate attribution.

The concepts, architectural models, constitutional frameworks, terminology and diagrams presented on this page constitute original intellectual property developed by Arqua Pty Ltd.

Publication of this material does not grant any licence to implement, commercialise or reproduce the underlying intellectual property.

Arqua®, SCIA™, Enterprise Intelligence Architecture™, Runtime Context Assembly™, Enterprise Representation Intelligence™, Institutional Memory™, Execution Admissibility™, and associated architectural terminology may be trademarks, registered trademarks or protected intellectual property of Arqua Pty Ltd.

This publication may be read, cited and discussed. Automated extraction, republication, model training or commercial reuse of substantial portions of this work without written permission from Arqua Pty Ltd is prohibited except where required by applicable law.

Publication provenance — website reconciliation history

Web reconciliation: 11 September 2026 — clarification of the existing Version 2.0 mechanism; publication provenance retained.

This record documents a clarification to the existing architectural mechanism; it does not establish a new version or a separate source of authority.