Context Assembly Library

STATUS: EXTERNAL — share-safe, bounded, regulator-visible.

Apply External / Share-Safe Codex AI rules.

ARQUA · Enterprise Intelligence Framework · Runtime Context Assembly · Enterprise Implementation Patterns · Request a Briefing

Purpose

The Context Assembly Library is an applied architectural pattern that contains reusable assembly definitions derived from Intent Scopes.

Each assembly definition specifies:

• participating Published Enterprise Products;
• Projection Specifications;
• semantic bindings;
• qualification policies; and
• admissibility constraints.

The library stores reusable architectural definitions, not operational information.

These definitions enable Runtime Context Assembly to consistently construct Qualified Operational Understanding from Published Enterprise Products.

Runtime Context Assembly does not discover context from scratch.

Instead, it assembles operational understanding using reusable architectural definitions.

The Context Assembly Library contains those reusable definitions.

Rather than storing operational data, it stores the structures used to assemble context consistently across the enterprise.

Every assembly definition is derived from an Intent Scope, which is itself derived from Intent as a constitutional primitive of the System Model Foundation.

The library does not organise information by systems or domains.

It organises reusable assembly definitions by enterprise intent.

Architectural Position

The Context Assembly Library sits within Enterprise Intelligence Architecture.

It is not part of the constitutional authority pattern catalogue. It does not describe how institutional authority emerges, degrades or recovers. That responsibility belongs to the Authority Pattern Library.

The Context Assembly Library describes reusable runtime assembly definitions used to construct Qualified Operational Understanding from Published Enterprise Products.

Enterprise Representation Intelligence
↓
Published Enterprise Products
↓
Intent Scope
↓
Context Assembly Library
↓
Runtime Context Assembly
↓
Qualified Operational Understanding
↓
Enterprise Coordination

This relationship keeps the constitutional capability and the applied implementation pattern separate.

Library Contents

The library contains reusable architectural definitions rather than enterprise data.

It includes:

• Intent Scope Definitions — purpose-specific statements of the operational intent, actor, decision, workflow or proposed action for which context is assembled.
• Context Assembly Templates — reusable structures describing the minimum authoritative context required for a defined operational purpose.
• Projection Specifications — definitions of which Published Enterprise Products and projections may participate in the assembly.
• Semantic Bindings — mappings between accepted enterprise representations, semantic definitions, product contracts and the intent scope.
• Qualification Templates — reusable qualification structures for evaluating whether candidate operational understanding is sufficient for reliance.
• Context Qualification Rules — completeness, freshness, provenance, semantic consistency, authority, policy and confidence conditions that must be evaluated.
• Enterprise Product Dependencies — declared dependencies on specific Published Enterprise Products or product classes required by the intent scope.
• Admissibility Constraints — constraints that preserve the boundary between qualified understanding and consequence-bearing execution.

These contents are not datasets, operational records or centralised enterprise memory.

They are reusable structures that guide how runtime context is assembled and qualified.

The organising principle is enterprise intent.

Systems, domains and platforms may supply Published Enterprise Products, but they do not determine the shape of the assembly.

The active Intent Scope determines which products, projections, semantic relationships and qualification rules are required.

Runtime Relationship

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

The Context Assembly Library provides reusable assembly definitions.

Runtime Context Assembly performs the dynamic assembly.

The library defines what must be assembled for each Intent Scope, which products may participate, how projections are bound, and how the candidate understanding should be qualified. Runtime Context Assembly uses those definitions at runtime to form Candidate Operational Understanding and then qualify it before institutional reliance.

Context Sufficiency

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

The enterprise never assembles all available information.

It assembles only what is necessary to perform the intended operation safely and coherently.

Context Sufficiency becomes the optimisation objective for Enterprise Intelligence.

Each library definition therefore records what is sufficient for a defined Intent Scope rather than attempting to describe complete enterprise context.

Example Assembly Definitions

Example 1 — Customer Service Restoration

Intent Scope

Customer Service Restoration

Required Enterprise Products:

• Customer
• Service
• Fault
• Network
• Appointment
• Technician
• Serviceability

This is not a dataset.

It is a reusable structural definition describing the minimum authoritative context required for restoration.

The definition identifies which Published Enterprise Products must participate before the enterprise can construct sufficient operational understanding for service restoration coordination.

Example 2 — Credit Assessment

Intent Scope

Credit Assessment

Required Enterprise Products:

• Customer
• Account
• Income
• Liability
• Credit History
• Policy
• Affordability

This definition does not store credit data.

It describes the reusable assembly structure required to construct purpose-specific operational understanding for a credit assessment workflow. The participating products, evidence thresholds and qualification rules may vary by institution, jurisdiction and policy context.

Example 3 — Asset Inspection

Intent Scope

Asset Inspection

Required Enterprise Products:

• Asset
• Location
• Maintenance
• Work Order
• Risk
• Field Workforce
• Compliance Obligation

This definition describes the minimum authoritative context required to plan, qualify or coordinate an asset inspection.

It is reusable across domains because the assembly structure is intent-scoped rather than tied to a single system, database or platform.

Example 4 — Workforce Scheduling

Intent Scope

Workforce Scheduling

Required Enterprise Products:

• Workforce
• Skill
• Availability
• Location
• Work Order
• Service Commitment
• Travel Constraint

This definition describes the minimum authoritative context required to allocate people, skills and work within operational constraints.

It is different from service restoration or asset inspection because the intent is scheduling rather than diagnosis, restoration or inspection.

Example 5 — Outage Coordination

Intent Scope

Outage Coordination

Required Enterprise Products:

• Network
• Fault
• Impacted Customer
• Service
• Field Crew
• Communication
• Restoration Plan

This definition describes the minimum authoritative context required to coordinate outage response.

It demonstrates that different intents require different context, even when some underlying enterprise products overlap.

Relationship to Runtime Context Assembly

Runtime Context Assembly is the constitutional capability.

The Context Assembly Library is one technical implementation pattern.

Other technologies could implement the same constitutional function.

This keeps Arqua technology independent.

Runtime Context Assembly owns the constitutional responsibility to form and qualify operational understanding for a defined operational intent. The Context Assembly Library provides one applied pattern for making that responsibility repeatable by defining the reusable structures that guide assembly and qualification.

The library does not authorise execution.

Qualified Operational Understanding may support coordination, decisioning, AI participation or admissibility evaluation. Execution Admissibility still determines whether a proposed action may bind institutional consequence.

Architectural Separation

Constitutional Architecture

Contains:

• Constitutive Properties
• Authority Pattern Library
• Architecture of Record
• SCIA Runtime
• Authority Lifecycle Integrity
• Execution Admissibility

Purpose:

Explains how enterprises establish and preserve legitimate institutional authority.

Enterprise Intelligence Architecture

Contains:

• Enterprise Representation Intelligence
• Enterprise Product Publication
• Published Enterprise Products
• Context Assembly Library
• Runtime Context Assembly
• Qualified Operational Understanding
• Enterprise Coordination
• Outcome Learning

Purpose:

Explains how enterprises continuously construct coherent operational understanding from authoritative enterprise representations.

Boundary

The Context Assembly Library defines reusable runtime context assembly structures.

It does not store operational data, replace Institutional Memory, create institutional truth, authorise execution, assert regulatory compliance, operate customer systems or remove human and organisational accountability.

Accountability for decisions, implementation and execution remains with the organisation applying the architecture.

Document Status: Public Website Page

Publication Date: 2026

Version: 1.0

Last Updated: 1 August 2026

Owner: Arqua Pty Ltd

Author: Mark Tovey

Portfolio: Enterprise Intelligence Architecture

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