Connect enterprise architecture with operational understanding and action
Organisations using TOGAF-aligned practices can use Arqua’s Enterprise Intelligence Architecture to examine how architecture intent remains connected to accepted representations, institutional memory, purpose-specific understanding, coordinated action and learning.
This is an Arqua alignment perspective. It does not prescribe a TOGAF extension or establish a formal equivalence between frameworks.
Work with the architecture you already govern
Existing architecture views, repositories, standards, delivery reviews and operational controls provide an important starting point. The review should identify which responsibilities they already fulfil and where evidence, ownership or continuity needs attention.
Enterprise Intelligence Architecture is Arqua’s integrated reference architecture. It complements enterprise architecture practice; the relationship is not a hierarchy in which TOGAF must progress through Arqua constructs to a SCIA deployment.
Map responsibilities and evidence
Existing architecture concern | Arqua alignment question | Evidence to examine |
Business purpose and operating model | Which decisions, services, outcomes and responsibilities matter within the chosen scope? | Capabilities, processes, decision ownership, delegations and service obligations. |
Representations and meaning | Which models describe the operational reality, which meanings have accepted standing, and where do representations differ? | Model scope, provenance, semantic mappings, acceptance decisions and recorded non-equivalences. |
Repositories and change history | Can current applicability and earlier decisions be reconstructed? | Architecture of Record, version history, obligations, decision records and Institutional Memory. |
Applications, data and integration | Which representations and Published Enterprise Products support a declared Operational Intent? | Publication scope, contract versions, consumer dependencies and permitted use. |
Operational understanding | How is context formed, and on what basis is it qualified for reliance? | Formation inputs, qualification criteria, limitations and handling of unsupported reliance. |
People, workflows and agents | Who contributes judgement, makes decisions, coordinates activity and acts under which authority? | Role boundaries, reviewed evidence, delegated scope, actor identity and operational controls. |
Execution and change | Do applicable conditions remain satisfied where action creates consequence? | Existing approvals, protected state, proportionate revalidation, execution evidence and exception handling. |
Outcomes and revision | What actually occurred, and how are proposed corrections reviewed and accepted? | Observed outcomes, uncertainty, revision decisions and preserved historical evidence. |
These are review prompts, not an official mapping of TOGAF phases or a mandatory artefact set. Existing records may fulfil the responsibilities without adopting Arqua-specific document formats.
Example: a payment workflow
For an illustrative payment workflow, begin with the purpose and relevant representations of customers, obligations, accounts and payment state. Trace which accepted meanings and enterprise products support the decision, which context is qualified for reliance and which person or delegated system exercises authority.
Then examine the release boundary: which approvals remain valid, what changes require revalidation, what the system actually executed and what settlement or exception outcome was observed. A permitted release does not prove successful settlement. Hold, refusal, escalation and non-action also have consequences and accountable owners.
The same approach can be adapted to other operational settings through Applications. The example does not demonstrate a deployment or determine that a particular payment is admissible.
Preserve distinct responsibilities
Architecture of Record records standing and applicability; it does not create institutional authority. Context qualification supports reliance for a purpose; it does not grant execution permission. Human participation should make the evidence reviewed, judgement contributed and authority exercised explicit.
The Enterprise Control Plane addresses continuity across the architecture. Execution Admissibility addresses proposed consequence-bearing execution. Where AI agents participate, actor governance remains connected to identity, delegated scope, lifecycle and evidence. Deterministic replay is a separate capability and should not be presumed from ordinary records or logs.
Architecture and implementation
These are architectural alignment patterns. Existing governance, native platform controls, composed services and meaningful human participation may fulfil the responsibilities. Their suitability and effectiveness require evidence for the defined scope. SCIA Runtime is a reference architecture for evaluating execution admissibility. It does not establish a deployed Arqua runtime or require its adoption.
Decisions, implementation, operations and compliance remain with the organisation and its delivery partners. This material does not establish certification, endorsement, affiliation, official framework extension or operational assurance.
Continue from here
- Enterprise Bridges — other enterprise bridges.
- Architecture — the architecture gateway.
- Work with Arqua — current engagement routes.
- Request a Briefing — discuss one architecture question and its operational scope.
Any follow-on review depends on the organisation’s situation and evidence. A workshop, diagnostic or runtime design is not an automatic next step.
© 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™, Pre-Execution Pressure Test™, Authority Pressure Test™, and associated architectural terminology may be trademarks, registered trademarks or protected intellectual property of Arqua Pty Ltd.
