Arqua in TOGAF-Aligned Enterprises
Extending enterprise architecture governance to the execution boundary
ARQUA · Enterprise Bridges Request a Briefing
Bridge note
This is an Enterprise Bridges practice note for enterprise architecture audiences. It is not a canonical definition page.
Core thesis
TOGAF helps govern architecture change. Arqua defines where consequence binds and where execution admissibility must be resolved at T=0.
Opening
TOGAF-aligned organisations already invest heavily in architecture governance: capability planning, standards, roadmaps, target-state design, and transformation control. These disciplines remain necessary.
As enterprises become more automated and AI-enabled, a further architectural question becomes decisive at the point of action: whether a proposed consequential action is allowed to execute at the moment consequence binds.
Arqua does not replace TOGAF. It extends the governance conversation to the institutional commit boundary.
Most organisations govern decisions. Very few govern execution.
The execution question
Traditional enterprise architecture can describe what should exist, how systems should align, and how change should be governed. Arqua asks a narrower but increasingly critical question: when the enterprise is about to act, is execution admissible?
Comparison (governance focus)
Aspect | TOGAF-aligned enterprise architecture | Arqua |
Primary focus | Architecture development, governance, target states, standards, roadmaps, and transformation | Execution admissibility at the moment consequence binds |
Primary question | What architecture should the enterprise design, govern, and transform toward? | Is this consequential action allowed to execute now? |
Operating moment | Architecture lifecycle, planning, governance, migration, and change | T=0 — the execution commit boundary |
Governance focus | Architecture governance, stakeholder alignment, standards, capability planning | Execution admissibility at T=0 across authority, state, context, constraints, and evidence |
Semantic treatment | Supports data architecture, metadata, conceptual models, and semantic governance | Makes execution-relevant meaning explicit enough to evaluate admissibility at the commit boundary (without prescribing implementation) |
AI relevance | Can guide AI operating models and enterprise governance | Governs AI-participating execution pathways at the moment consequence binds (T=0) |
Evidence model | Architecture documentation, governance records, compliance artefacts | Evidence-at-execution showing why an action was permitted, refused, escalated, or held |
Best used for | Enterprise transformation and architecture governance | High-consequence workflows where execution must not bind without admissibility |
Where Arqua fits
From Architecture Governance to Execution Admissibility
Enterprise architecture governance
Arqua is complementary to TOGAF-aligned enterprise architecture: it does not replace TOGAF and is not an official TOGAF extension. It focuses on execution-bound admissibility at T=0, where consequential actions are permitted, refused, escalated, or held before consequence binds.
→ AI-ready enterprise semantics
→ Execution admissibility at T=0
- Enterprise architecture governance structures the broader architecture environment.
- AI-ready enterprise semantics prepares meaning for operational and machine-checkable use.
- Architecture of Record maps where consequence binds and where control must exist.
- SCIA Runtime (Stateful Contextual Integrity Architecture) resolves admissibility at the commit boundary (T=0), as an architectural runtime layer (not a product claim).
- Execution admissibility at T=0 is the resolved condition that determines whether consequence may bind.
Section ladder: Trusted architecture governance is a necessary foundation. The Architecture of Record identifies where consequence binds. SCIA Runtime resolves admissibility at T=0. Execution proceeds only when admissibility is resolved.
Complementary, not competitive
TOGAF helps govern the architecture journey. Arqua focuses on execution admissibility at the consequence-binding boundary (T=0), as a complementary discipline.
Start with one high-consequence workflow
Choose one workflow where approval, automation, or AI-supported decisioning can lead to consequential execution. Trace it to the moment consequence binds. Identify where authority, evidence, context, constraints, and state are currently assumed rather than proven.
Boundary note
This page describes how Arqua may complement TOGAF-aligned enterprise architecture environments. It does not define, modify, certify, or represent TOGAF. Arqua does not claim endorsement, certification, or affiliation with The Open Group unless expressly stated. All trademarks remain the property of their respective owners.
© Arqua Pty Ltd. All rights reserved.