Arqua in TOGAF-Aligned Enterprises

How enterprise architecture governance extends into Enterprise Intelligence Architecture and the T=0 execution boundary.

This bridge has been updated following publication of Enterprise Intelligence Architecture.

TOGAF-aligned enterprise architecture remains the enterprise architecture governance discipline.

Enterprise Intelligence Architecture is the Arqua capstone reference architecture for institutional intelligence under AI-mediated execution.

The Enterprise Control Plane preserves institutional continuity across representation, meaning, reliance, decision, execution, consequence and revision.

Execution Admissibility Architecture governs whether proposed consequence-bearing action may bind at T=0.

SCIA Runtime resolves admissibility at the runtime boundary.

This page therefore maps TOGAF-aligned architecture governance into the Arqua institutional intelligence chain, not only into execution-admissibility controls.

This page is a translation and alignment note. It is not an official TOGAF extension, certification, endorsement or representation of The Open Group.

Core thesis

TOGAF-aligned architecture governance remains necessary.

It helps enterprises structure, govern and communicate architecture change.

But enterprise architecture artefacts do not, by themselves, prove whether operational reality has been represented, whether meaning has been accepted, whether reliance has been declared, whether decision and proposed action remain within authority and permitted use, or whether a consequence-bearing action is admissible at the moment it binds the institution.

Arqua adds the Enterprise Intelligence Architecture lens and the execution-admissibility lens.

The updated bridge is:

TOGAF-aligned enterprise architecture

↓

Enterprise Intelligence Architecture

How does operational reality become governed action and revised representation?

↓

The Sovereign Boundary

What must remain institutionally governable?

↓

The Enterprise Control Plane

How does institutional continuity survive implementation, use, decision, consequence and revision?

↓

Execution Admissibility Architecture

Is this consequence-bearing action admissible at T=0?

↓

SCIA Runtime

Can admissibility be resolved and replayed at the runtime boundary?

Enterprise Intelligence Architecture as the TOGAF bridge

TOGAF-aligned enterprise architecture provides architecture governance, ADM structure, architecture domains, artefacts, viewpoints, repository discipline and transformation governance.

Enterprise Intelligence Architecture translates that work into the institutional intelligence chain.

It asks how operational reality becomes represented reality, governable understanding, accepted semantic architecture, shared institutional meaning, declared reliance, governed institutional decision, coordinated operational action, authorised consequence and revised representation.

The Enterprise Control Plane then preserves continuity across that chain.

Execution Admissibility Architecture governs the runtime consequence boundary.

SCIA Runtime resolves admissibility at T=0.

TOGAF-aligned concerns mapped to Enterprise Intelligence Architecture

TOGAF-aligned concern	EIA alignment	Arqua construct
Business Architecture	Capabilities, decisions, authority, outcomes, consequence ownership	Governed Institutional Decision, Authority Model, Consequence Formation
Data Architecture	Entities, identities, states, events, claims, evidence, lineage, data products	System Model Foundation, Domain Representation
Application Architecture	Systems that publish, transform, consume, infer, decide, recommend, coordinate or execute	Consumer Binding, Agent Control Plane, Decision / Workflow / AI Use
Technology Architecture	Runtime context, validation, policy engines, telemetry, control surfaces	Enterprise Control Plane, SCIA Runtime
Architecture Governance	Acceptance, conformance, continuity and architecture change	Semantic Governance Operating Model, Architecture of Record
Architecture Repository	Time-valid architecture, semantic versions, consumer bindings and consequence evidence	Architecture of Record, Assurance

TOGAF ADM-aligned activity mapped to Arqua

TOGAF ADM-aligned activity	EIA question	Arqua artefact
Preliminary / architecture governance	What institutional intelligence principles and continuity conditions must apply?	EIA principles, Enterprise Control Plane policy lens
Architecture vision	Which operational realities, decisions and consequences matter?	Institutional intelligence scope, high-consequence flow candidate list
Business Architecture	Who owns meaning, authority, reliance, decision and consequence?	Authority model, decision-reliance map, consequence ownership view
Data Architecture	What system is being represented?	System Model Foundation, domain representation catalogue
Application Architecture	Which systems publish, consume, decide, recommend, coordinate or execute?	Consumer Binding, agent participation map, workflow/use map
Technology Architecture	Where can continuity, policy, context and admissibility be enforced?	Control-surface map, SCIA Runtime readiness view
Opportunities and solutions	Which high-consequence flow should prove EIA first?	Minimum viable EIA candidate
Migration planning	How does the enterprise mature from governed artefacts to governed institutional intelligence?	EIA maturity roadmap
Implementation governance	Does delivery preserve representation, meaning, authority, permitted use and admissibility?	Enterprise Control Plane conformance evidence, Architecture of Record-to-delivery handoff
Architecture change management	Did outcomes revise representation without destroying continuity?	Revision record, drift register, Architecture of Record update

What TOGAF-aligned architecture contributes

TOGAF-aligned enterprise architecture remains valuable.

It contributes architecture governance, domain structure, viewpoints, architecture artefacts, architecture repositories, roadmap discipline and implementation governance.

Arqua does not replace that discipline.

Arqua asks what must be added when architecture moves toward AI-mediated execution, agent participation, runtime decisioning and consequence-bearing action.

The added Arqua questions are:

What operational reality is represented?
Which System Model Foundation applies?
Which meaning has been accepted?
Which Semantic Contract Surface carries that meaning?
Which Consumer Binding records reliance?
Which decision, workflow, model or agent uses it?
Which authority and permitted-use conditions apply?
Where does proposed action become consequence?
Can Execution Admissibility be resolved at T=0?
Can the admissibility decision be replayed?
Did the consequence revise future representation without destroying continuity?

What changes after Enterprise Intelligence Architecture

Before Enterprise Intelligence Architecture, the TOGAF bridge could be read primarily as a path from architecture governance to Execution Admissibility.

That remains valid, but it is incomplete.

Enterprise Intelligence Architecture now provides the capstone reference architecture into which the TOGAF bridge fits.

The updated bridge is not only:

architecture governance

→ execution boundary

It is:

architecture governance

→ institutional intelligence architecture

→ continuity control

→ runtime admissibility

→ replayable consequence

→ revised representation

This makes the TOGAF alignment more complete.

It preserves TOGAF-aligned architecture governance while making clear where Arqua adds institutional intelligence, control-plane continuity, agent governance, execution admissibility, SCIA runtime resolution and assurance.

Control-plane terminology

Arqua uses three related but distinct control-plane concepts in this bridge.

Enterprise Control Plane

Continuity across the institutional intelligence system.

It preserves identity, meaning, authority, provenance, permitted use, lineage, conformance, accountability and reconstructability as accepted architecture becomes implementation, use, decision, consequence and revision.

Agent Control Plane

Governance of AI runtime actors.

It governs AI-enabled runtime actors through identity, authority source, permitted use, enforcement, evidence, lifecycle control and offboarding.

Enterprise Execution Control Plane

Execution-boundary control at T=0.

It governs the execution boundary inside Execution Admissibility Architecture, where authority, state, context, constraints, risk and evidence are resolved before consequence-bearing action may bind.

Canonical relationship statement:

Enterprise Intelligence Architecture defines the institutional intelligence system.

The Enterprise Control Plane preserves the continuity of that system as it operates and changes.

The Agent Control Plane governs AI runtime actors inside that system.

Execution Admissibility Architecture governs whether proposed consequence-bearing action may bind.

Sovereign Boundary extension

The Sovereign Boundary remains important.

It is the doctrine that defines what must remain institutionally governable when capability is delegated.

In the updated TOGAF bridge, it is no longer the only intermediary between TOGAF-aligned enterprise architecture and Execution Admissibility.

Enterprise Intelligence Architecture provides the capstone reference architecture.

The Sovereign Boundary identifies what must remain institutionally governable inside that architecture when capability, interpretation, stewardship, platforms, AI systems, workflow platforms or execution pathways are delegated.

Its central distinction remains:

Capability may be delegated.

Legitimacy must remain governed.

The institutional-intelligence and execution-admissibility gap

TOGAF-aligned architecture can show what the enterprise intends to design, change, govern and transition.

Arqua asks a broader institutional-intelligence question and a narrower execution question:

Has operational reality been represented through a governed System Model Foundation?
Has meaning been accepted for a defined scope, version, authority context and use context?
Has reliance been declared through a Consumer Binding to a specific Semantic Contract Surface?
Does a decision, workflow, model or agent use that meaning within authority and permitted-use conditions?
When proposed action becomes consequence-bearing, is execution admissible at T=0?

The doctrine is explicit:

Representation is not meaning.
Meaning is not acceptance.
Acceptance is not authority.
Authority is not execution.
Semantic correctness is necessary but insufficient.
A semantic contract may support a decision or AI use, but it does not authorise action.
AI output is not institutional meaning.
Agent recommendation is not decision.
Decision is not execution.
Execution Admissibility governs the transition from proposed action to consequence-bearing execution.
At the consequence boundary, admissibility must be re-held, not merely remembered.
Consequence-binding transitions require evidence, validation, freshness, authority continuity, state continuity, policy continuity, semantic integrity, non-bypassability, replayability and accountability.
Revision must not destroy reconstructability.

Updated boundary statement

Arqua does not replace TOGAF-aligned enterprise architecture.

It adds a complementary institutional intelligence and execution-admissibility lens.

TOGAF-aligned enterprise architecture can define target states, architecture views, principles, capabilities, processes, systems, data, standards, roadmaps and governance.

Enterprise Intelligence Architecture asks whether those artefacts preserve representation, accepted meaning, declared reliance, authority, permitted use, evidence and reconstructability as architecture becomes operational action and consequence.

The Enterprise Control Plane preserves the continuity of that system as it operates and changes.

Execution Admissibility Architecture determines whether proposed consequence-bearing action may bind at T=0.

SCIA Runtime resolves admissibility at the runtime boundary.

Assurance proves and reviews what occurred.

Common failure signals

Architecture governance approves a target state, but no one knows which operational reality is being represented.
A semantic model exists, but accepted meaning is not scoped, versioned, authority-bound or use-bound.
A semantic contract is treated as permission to act.
Consumer reliance is implicit rather than declared through a Consumer Binding.
AI output is treated as institutional meaning.
Agent recommendation is treated as decision.
Decision is treated as execution.
Processes are mapped, but execution surfaces are not.
Systems are classified by application domain, but not by whether they publish, consume, infer, decide, recommend, coordinate or execute.
Controls exist in design documents, but not at the commit boundary.
Authority is assumed from workflow state rather than re-resolved at execution.
Architecture review happens before delivery, but no admissibility evidence exists at runtime.
Audit reconstructs authority after execution has already occurred.
Revision updates future representation but destroys reconstructability of past reliance, decision, execution or consequence.

Example workflow

A payment workflow appears in the enterprise architecture as a process, application integration, data flow and control path.

TOGAF-aligned artefacts can describe the target state and governance model.

Enterprise Intelligence Architecture asks:

What operational reality is being represented?
Which System Model Foundation defines the relevant parties, accounts, states, events, claims and evidence?
Which accepted meaning applies to the payment context?
Which Semantic Contract Surface carries that meaning?
Which Consumer Binding records reliance by the payment workflow?
Which decision, workflow, model or agent uses it?

Execution Admissibility Architecture then asks:

Where does the payment become consequence-binding?
Which system executes the payment?
Is authority still valid at that moment?
What evidence is required before release?
What prevents release if authority, evidence, context, constraints, policy or state has changed?
Can the admissibility decision be replayed?

The architecture is not complete until the institutional intelligence chain and the execution boundary are both visible.

Engagement pathway

Run an Enterprise Bridge Workshop.
Identify which enterprise governance discipline the organisation is entering from.
Scope the relevant operational reality, decision and consequence.
Establish the System Model Foundation.
Identify accepted meaning, Semantic Contract Surface and Consumer Binding.
Apply the Sovereign Boundary lens to classify delegated systems, stewards, platforms, models and workflows.
Select one high-consequence workflow or delegated semantic platform.
Map the execution topology.
Identify execution surfaces and consequence systems.
Locate T=0 commit boundaries.
Define authority, evidence, context, constraints, policy, semantic integrity and state requirements.
Produce an Architecture of Record baseline.
Assess SCIA Runtime readiness for runtime admissibility resolution and replayability.
Define assurance, review and reconstruction expectations.
Hand off architecture guardrails to delivery partners.

Key links

Source basis

This bridge note is informed by Arqua’s Enterprise Intelligence Architecture, Enterprise Control Plane, Agent Architecture, Agent Control Plane, Execution Admissibility Architecture, Architecture of Record, SCIA Runtime, Pre-Execution Pressure Test and Sovereign Boundary materials, and by public TOGAF Standard materials from The Open Group.

This page is a translation and alignment note. It does not assert endorsement, certification, affiliation, or official extension of TOGAF or The Open Group.

Boundary note

“This page describes architectural alignment patterns. It does not assert certification, endorsement, partnership, affiliation, official framework extension, legal assurance, regulatory compliance, system operation, or implementation. Arqua operates at the architecture and governance layer. Runtime behaviour, system execution, regulatory compliance, and operational responsibility remain with the deploying organisation and its chosen delivery partners.”

References to TOGAF are used only to describe alignment patterns for TOGAF-aligned enterprise architecture practices. Arqua does not assert TOGAF certification, endorsement, partnership, affiliation, official framework extension, or representation of The Open Group.

CTA

Primary: Run an Enterprise Bridge Workshop

Use the workshop to translate TOGAF-aligned architecture governance into Enterprise Intelligence Architecture, continuity-control, execution-admissibility and first workflow questions.

Secondary: Build an Architecture of Record Baseline

Map representation, semantic acceptance, reliance, execution surfaces, consequence systems, authority boundaries, admissibility control points and replayability requirements for one high-consequence workflow.

Document Status: Public Website Page

Publication Date: 2026

Version: 1.0

Last Updated: 23 July 2026

Permanent URL: https://app.notion.com/p/f24b143e680b4c4f949a8da45f8765b4

Owner: Arqua Pty Ltd

Author: Mark Tovey

Portfolio: Enterprise Intelligence Architecture

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™, Pre-Execution Pressure Test™, Authority Pressure Test™, and associated architectural terminology may be trademarks, registered trademarks or protected intellectual property of Arqua Pty Ltd.