Runtime Context Assembly

Constitutional Category: Constitutional Mechanism

Forming and Qualifying Operational Understanding

Arqua Architecture Paper

Version 2.0 | July 2026

Mark Tovey, Arqua Pty Ltd

Runtime Context Assembly is the constitutional mechanism through which Enterprise Intelligence forms and qualifies purpose-specific operational understanding from accepted enterprise representations.

Executive Summary

Runtime Context Assembly is no longer defined as a retrieval pattern.

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

Runtime Context Assembly is responsible for:

• forming purpose-specific qualified 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 constitutional responsibilities.

The constitutional responsibility is not to discover information wherever it happens to sit. The responsibility is to form qualified operational understanding from accepted enterprise representations so that people, applications and artificial intelligence can reason, decide and coordinate on an institutionally admissible basis.

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 constitutional mechanism responsible for this capability.

Constitutional Definition

Runtime Context Assembly is the constitutional mechanism that discovers, assembles and qualifies Published Enterprise Products appropriate to the Operational Intent so that people, applications and artificial intelligence may reason, decide and coordinate on an institutionally admissible basis.

Accepted representations provide the authoritative basis.

Published Enterprise Products provide governed participation.

The constitutional responsibility is not to consume enterprise content wherever it happens to sit. Runtime Context Assembly discovers and assembles Published Enterprise Products appropriate to the Operational Intent.

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 constitutional responsibility.

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.

Operational Intent

Operational Intent is the explicit statement of the purpose for which qualified operational understanding is being assembled, including the reasoning, decision or action boundary within which that understanding may be used.

Runtime Context Assembly always begins with Operational Intent rather than generic information requests.

Operational Intent determines:

• scope;
• authority;
• policy;
• required representations;
• freshness;
• completeness;
• acceptable uncertainty; and
• admissibility threshold.

Operational Intent prevents context from becoming an unbounded information bundle.

It establishes why the 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.

Runtime Lifecycle

This lifecycle defines Runtime Context Assembly as a constitutional mechanism rather than a retrieval workflow.

It begins with operational need and intent.

It resolves identity, authority, capability, representation, semantics, policy and contract constraints.

It assembles a candidate operational context.

It records that assembly in an Assembly Manifest.

It then qualifies the assembled context against the operational intent.

Only after qualification does the output become Qualified Operational Understanding.

Enterprise Registry

Runtime Context Assembly depends on an Enterprise Registry.

The Enterprise Registry is not merely a data product catalogue.

It discovers constitutional capabilities required to form 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 constitutional capability discoverable, governable and composable.

Assembly Manifest

The Assembly Manifest is the complete description of the representations, services, authorities, policies and evidence used to assemble a candidate operational context.

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 constitutional artefact.

It is not yet evidence of admissible understanding.

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 assembled context against the requirements of the requesting operational intent before it becomes qualified operational understanding for reasoning, coordination or action.

Qualification criteria include:

• completeness;
• freshness;
• semantic consistency;
• authority;
• provenance;
• policy compliance;
• confidence; and
• admissibility.

Formation does not establish institutional reliance.

Qualification establishes institutional reliance.

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 immutable evidentiary record describing the qualified operational understanding, the qualification process applied, and the resulting admissibility outcome.

It supports:

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

Qualification outcomes align directly with:

• ADMISSIBLE
• WITH_CONDITIONS
• ESCALATE
• NOT_ADMISSIBLE
• INSUFFICIENT_INFORMATION

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 constitutional representation foundation that makes these representations structurally 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 constitutional responsibility to form and qualify operational understanding from accepted enterprise representations.

Runtime Context Assembly is defined by the constitutional responsibility to discover, assemble and qualify Published Enterprise Products appropriate to the Operational Intent.

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 relevant 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 constitutional 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;
• discovers relevant accepted representations and constitutional capabilities;
• discovers relevant Published Enterprise Products and constitutional capabilities;
• resolves semantics, policy and contracts;
• assembles candidate runtime context;
• records the Assembly Manifest;
• qualifies the assembled context;
• 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 constructs qualified operational understanding from accepted enterprise representations for a defined operational intent.

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 constitutional 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.

Constitutional Relationships

Enterprise Coherence

Runtime Context Assembly preserves contextual coherence. It ensures that institutional understanding is assembled for a defined operational intent rather than fragmented, generic or detached from authority and policy.

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.

Enterprise Representation Intelligence

Enterprise Representation Intelligence forms and evolves accepted enterprise representations. Runtime Context Assembly uses those accepted representations to construct qualified operational understanding for a specific runtime purpose.

Institutional Memory

Institutional Memory preserves accepted understanding over time. Runtime Context Assembly draws from that persistent memory and current accepted representations to form transient runtime context.

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.

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 constitutional runtime service among peer services.

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 Constitutional Responsibility

Runtime Context Assembly owns one constitutional responsibility within the overall Constitutional Architecture of Enterprise Intelligence:

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.

Implementation Patterns

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

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

Boundary Statement

This paper describes a constitutional 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 constitutional 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: 23 July 2026

Owner: Arqua Pty Ltd

Author: Mark Tovey

Portfolio: Enterprise Intelligence Architecture

Constitutional Category: Constitutional Mechanism

This paper forms part of the Arqua Constitutional Architecture of Enterprise Intelligence. It should be read together with the related constitutional papers 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.