Architecture Papers
Architecture Papers are supporting constitutional specifications behind the Enterprise Intelligence Framework.
They are not the primary entry point for the website. New readers should begin with the Framework, which explains why Enterprise Intelligence exists, how the architecture is organised, how the constitutional capabilities relate, how the complete architecture operates and how organisations adopt it.
Each paper expands the Enterprise Intelligence Framework by defining one constitutional responsibility in detail. The papers preserve technical depth while supporting a single architectural narrative.
Enterprise Coherence is the governing property of Enterprise Intelligence.
The Constitutional Architecture of Enterprise Intelligence is the constitutional meta-architecture and portfolio map for the Arqua architecture portfolio.
Enterprise Intelligence Architecture is the complete enterprise-facing operating architecture.
Arqua Canonical Architecture is the integrated operational expression of the constitutional capabilities working together.
Canonical hierarchy
Enterprise Coherence
Governing property
↓
The Constitutional Architecture of Enterprise Intelligence
Constitutional meta-architecture and portfolio map
↓
Enterprise Intelligence Architecture
Complete enterprise-facing operating architecture
↓
Arqua Canonical Architecture
Authoritative canonical model, vocabulary and domain structureCanonical runtime chain
The Enterprise Control Plane is cross-cutting. It is not a sequential stage.
Architecture of Record is an institutional acceptance and authority mechanism. It establishes which architecture and representations possess standing and where consequence boundaries apply. It is not a runtime processing stage between Enterprise Representation Intelligence and Institutional Memory.
Institutional Memory preserves accepted understanding.
Enterprise Product Publication establishes governed participation by producing Published Enterprise Products.
Runtime Context Assembly consumes Published Enterprise Products and produces Qualified Operational Understanding through Context Qualification.
Constitutional Foundation
- The Constitutional Architecture of Enterprise Intelligence — The constitutional meta-architecture and portfolio map.
- Enterprise Coherence — The governing property of Enterprise Intelligence.
Capstone Architecture
- Enterprise Intelligence Architecture — The complete enterprise-facing operating architecture.
- Arqua Canonical Architecture — The authoritative canonical model, vocabulary and domain structure within the constitutional architecture.
Enterprise Intelligence Reference Architectures
Reference Architectures demonstrate how Constitutional Architecture is composed into complete Enterprise Intelligence operating architectures.
Unlike Constitutional Architecture, Reference Architectures describe the interaction between multiple constitutional capabilities.
Unlike Implementation Patterns, they describe complete enterprise operating models rather than individual implementation approaches.
Every Reference Architecture must answer one enterprise question that no single Constitutional Architecture paper can answer.
- RA001 — Enterprise Intelligence Platform Reference Architecture — Purpose: How institutions continuously produce Qualified Operational Understanding.
- RA002 — Enterprise Participation Reference Architecture — Purpose: How institutions consistently operationalise Qualified Operational Understanding across authorised enterprise participants.
Platform Realisation Reference Architectures
Each platform participates in one or both enterprise reference architectures. Platforms implement selected responsibilities; they do not define the enterprise capabilities.
- Microsoft Fabric
- Microsoft Power Platform
- AWS
- Databricks
- Salesforce
- ServiceNow
- SAP
Foundational Capabilities
- System Model Foundation — Establishes the representation foundation through which operational reality may be structurally represented.
- Enterprise Representation Intelligence — Forms, validates, governs and evolves institutional representations.
- Architecture of Record — Establishes accepted architecture, representation standing, authority, applicability, implementation obligations and consequence boundaries.
- Enterprise Reality Representation Framework — Defines how operational evidence becomes governed institutional representation.
- AI-Ready Enterprise Semantics — Preserves semantic coherence for people, systems and AI.
- Institutional Memory — Preserves accepted institutional understanding and its evolution across time.
- Institutional Memory — Preserves accepted institutional understanding and its evolution across time.
- Enterprise Participation — Establishes which accepted enterprise representations and enterprise capabilities are intentionally published as governed Enterprise Products for participation in Enterprise Intelligence.
Runtime Coordination
- Runtime Context Assembly — Forms Candidate Operational Understanding from Published Enterprise Products within an active Intent Scope and produces Qualified Operational Understanding through Context Qualification.
- Enterprise Coordination — Coordinates people, systems, workflows, services and agents through Qualified Operational Understanding, accepted meaning, valid authority and traceable context to produce Enterprise Outcomes.
- The Enterprise Control Plane — Preserves governance continuity across the complete architecture.
- Agent Control Plane — Preserves actor coherence by ensuring AI-enabled runtime actors remain bound to identity, authority, permitted use and evidence.
- Execution Admissibility Architecture — Determines whether proposed consequence-bearing action may bind.
- SCIA Runtime — Resolves authority, state, context, constraints and evidence at T=0.
Applied Architecture
- Architectural Survivability — Preserves continuity under change.
- The Alignment Architecture — Preserves alignment between meaning, execution and admissibility.
- The Sovereign Boundary — Preserves institutional sovereignty when capability is delegated.
- The Desynchronization of Authority — Identifies authority-coherence failure when point-in-time authority is treated as continuously valid.
- Enterprise Bridges — Preserves coherence across enterprise insertion points and organisational boundaries.
- Enterprise Insertion Patterns — Defines how the architecture enters existing enterprise environments.
- Semantic Contract Surface — Preserves meaning across organisational, technical, analytical, AI and operational boundaries.
Portfolio discipline
Every Arqua paper should state:
- Constitutional category
- Constitutional responsibility
- Dimension of Enterprise Coherence preserved
- Primary constitutional input
- Primary constitutional output
- Constitutional boundary
- Human and organisational accountability
What kind of architectural responsibility is this?
What responsibility does this paper define?
What condition does this responsibility continuously protect?
What does this responsibility operate on?
What does this responsibility produce?
What does this responsibility not govern?
Where does accountability remain?
Constitutional taxonomy fields
The Architecture Papers database should expose the constitutional taxonomy directly.
Field | Example |
Constitutional Category | Constitutional Mechanism |
Constitutional Responsibility | Form and qualify purpose-specific operational understanding |
Governing Property Preserved | Contextual coherence |
Primary Constitutional Input | Operational Intent |
Primary Constitutional Output | Qualified Operational Understanding |
Constitutional Boundary | Does not authorise execution |
Canonical Parent | Constitutional Architecture of Enterprise Intelligence |
Coherence dimensions and constitutional categories
Constitutional category and coherence dimension are separate classifications.
Constitutional category states what kind of architectural responsibility the paper defines.
Dimension of Enterprise Coherence preserved states what condition the responsibility protects.
For Runtime Context Assembly:
- Constitutional category: Constitutional Mechanism
- Responsibility: Form and qualify purpose-specific operational understanding
- Coherence dimension: Contextual coherence
For Institutional Memory:
- Constitutional category: Constitutional Asset
- Responsibility: Preserve accepted institutional understanding and its evolution
- Coherence dimension: Temporal coherence
Related public signals
These are supporting external signals. They are not Arqua Architecture Papers.
- Public Signals of Execution Governance
- Public Signals of Execution Attribution Collapse
- Agentic AI: proposal is not permission
Boundary statement
This portfolio describes architectural concepts, reference architectures and applied patterns.
It does not assert legal compliance, regulatory certification, assurance, system operation or implementation.
Accountability for decisions, execution and consequence remains with the organisation.
Document Status: Public Website Page
Publication Date: 2026
Version: 1.0
Last Updated: 23 July 2026
Permanent URL: https://app.notion.com/p/6624aa5244b646f7b974142a2396ad8a
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.
Final CTA
Start with one high-consequence decision.
Identify which constitutional responsibility is missing, implicit or weak: representation, acceptance, memory, context qualification, coordination, continuity governance, admissibility or learning.
The Sovereign BoundaryThe Desynchronization of AuthorityThe Alignment ArchitecturePaper Title | Status | Priority | Category | Theme | Audience | Publication State | Architectural Research Theme | Related Concepts | Subtitle | Paper Role | Stream | Transformation | Constitutional Category | Constitutional Responsibility | Governing Property Preserved | Primary Constitutional Input | Primary Constitutional Output | Constitutional Boundary | Canonical Parent | Abstract | Core Questions | Key Concepts | Purpose | Related Arqua Papers | Architectural Survivability Contribution |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Published | Highest | Enterprise Architecture | Governed Representation | Enterprise ArchitectureData ArchitectureSemantic ArchitectureAI ArchitectureRisk | Published | Institutional Representation Under AI-Mediated Execution | The Constitutional Model of Enterprise Representation | Representation Architecture | Reference Architectures and Control Mechanisms | Operational reality → constitutional enterprise representation | Representation Foundation | Define how enterprise reality may be structurally represented | Operational Reality | Structurally consistent Enterprise Representations | Does not define meaning, preserve memory or authorise execution | Constitutional Architecture of Enterprise Intelligence | The System Model Foundation defines the constitutional model through which operational reality becomes structurally representable across the enterprise. It establishes the enduring representational substrate beneath information models, ontologies, data products and technology bindings. | Defines the constitutional model through which operational reality becomes structurally representable across the enterprise. | Preserves representational identity across technologies and time. | ||||||
Working Draft | Enterprise Intelligence ArchitectureAI-Ready Enterprise SemanticsSemantic Governance Operating ModelSemantic Contract SurfaceEnterprise Control PlaneData Products | How Operational Reality Becomes Governed Institutional Representation | Representation Architecture | Reference Architectures and Control Mechanisms | Operational reality → governed institutional representation | Representation Foundation | Defines how System Model Foundation primitives combine into coherent source, domain, cross-domain, enterprise and purpose-specific representations, and how those representations become sufficiently governed to support institutional reliance. | Preserves representational coherence by defining how operational evidence becomes governed institutional understanding. | |||||||||||||||||
Published | High | CIOCTOChief ArchitectCDAOAI GovernanceRiskPlatform Leaders | Published | Institutional Continuity Under AI-Mediated Execution | From AI Features to Governed Runtime Actors | Reference Architectures and Control Mechanisms | Accepted Agent Architecture → Agent Control Contract → Conformant Operational Agent Runtime | Constitutional Governance Mechanism | The Enterprise Control Plane; Execution Admissibility Architecture; AI-Ready Enterprise Semantics; The Semantic Contract Surface; Architecture of Record; Assurance; Patterns | Preserves governable AI participation by binding agent identity, authority, permitted use, evidence and lifecycle controls. | |||||||||||||||
Published | High | Chief ArchitectAI GovernancePlatform LeadersRisk | Published | Institutional Continuity Under AI-Mediated Execution | Implementation Controls for Governed Runtime Actors | Reference Architectures and Control Mechanisms | Accepted Agent Architecture → Runtime Enforcement → Evidence and Lifecycle Control | Constitutional Governance Mechanism | Agent Architecture and the Enterprise Control Plane; The Enterprise Control Plane; Execution Admissibility Architecture; Architecture of Record; Assurance; Patterns | Preserves runtime agent control through identity, authority, permitted use, enforcement, evidence, lifecycle control and offboarding. | |||||||||||||||
Future Research | Medium | Institutional Governance | Consequence Feedback | Enterprise ArchitectureInstitutional GovernanceRiskBoards | Research Backlog | Recursive Sovereignty Under Operational Consequence | Sovereign BoundaryConsequence OwnershipOutcome FeedbackArchitectural SurvivabilityEnterprise Control Plane | How Consequence Revises Institutional Representation Without Breaking Agency | Feedback Architecture | Doctrine and Failure Modes | Consequence → revised institutional representation | Constitutional Function | Preserves institutional sovereignty through recursive renewal of meaning, authority, consequence and learning. | ||||||||||||
Planned | High | Enterprise Architecture | Semantic Boundaries | Enterprise ArchitectureData Product OwnersAPI OwnersAI GovernanceData GovernanceRisk | Concept Approved | Institutional Meaning Across Boundaries | Semantic ContractsData Product ContractsAPI ContractsAI Context ContractsPermitted UseContext Collapse | How Accepted Meaning Survives Across Organisational, Technical and AI Boundaries | Boundary Architecture | Reference Architectures and Control Mechanisms | Accepted semantic architecture → shared institutional meaning | Constitutional Mechanism | Preserves accepted meaning as it crosses organisational, technical, analytical, AI and operational boundaries. | ||||||||||||
Planned | High | Enterprise Architecture | Architecture Conformance | Chief ArchitectsArchitecture Review BoardsEngineering LeadersPlatform LeadersRisk | Concept Approved | Institutional Continuity Through Implementation | Enterprise Control PlaneArchitecture AuthorityDecision RegisterDerivation PackageEngineering SchemasBuild GuidesConformance Review | How Accepted Architecture Becomes Conformant Engineering | Implementation Pattern | Reference Architectures and Control Mechanisms | Architecture authority → engineering conformance | Constitutional Governance Mechanism | Preserves architecture authority as a control-plane function linking accepted design, governance and operational consequence. | ||||||||||||
Planned | High | Enterprise Architecture | Continuity Under Change | Enterprise ArchitectureInstitutional GovernanceAI GovernanceRiskBoards | Concept Approved | Institutional Survivability Under Change | Constitutive PropertiesContinuity CarriersRecursive ReconstructionEnterprise Control PlaneSovereign Boundary | Constitutive Properties, Continuity Carriers and Recursive Reconstruction | Survivability Doctrine | Doctrine and Failure Modes | Change → continuity-preserving reconstruction | Governing Property | Defines the constitutional objective that explains why institutions preserve identity, meaning, authority and legitimate action through change. | ||||||||||||
Planned | High | Institutional Governance | Semantic Authority | Enterprise ArchitectureData GovernanceDomain OwnersRiskBoards | Concept Approved | Institutional Meaning Under AI-Mediated Execution | Semantic AuthorityDomain OwnershipArchitecture AuthoritySemantic ReviewApprovalSupersession | How Governable Understanding Becomes Accepted Architecture | Semantic Architecture | Reference Architectures and Control Mechanisms | Governable understanding → accepted semantic architecture | Constitutional Governance Mechanism | Preserves accepted meaning by defining how semantic authority is owned, versioned, revised and retired through institutional governance. | ||||||||||||
Planned | High | Enterprise Architecture | Operational Intelligence | Enterprise ArchitectureOperationsAI GovernanceWorkflow OwnersRisk | Concept Approved | Institutional Intelligence Under AI-Mediated Execution | Enterprise Intelligence ArchitectureExecution Admissibility ArchitectureAI AgentsWorkflowsDecision ServicesOutcome Capture | How Shared Meaning Becomes Coordinated Operational Action | Runtime Architecture | Reference Architectures and Control Mechanisms | Shared institutional meaning → coordinated operational action | Constitutional Function | Coordinates accepted institutional meaning into operational work while preserving legitimate authority and consequence boundaries. | ||||||||||||
Planned | High | Enterprise Architecture | Institutional Meaning | Enterprise ArchitectureSemantic ArchitectureData GovernanceAI GovernanceDomain Owners | Concept Approved | Institutional Meaning Under AI-Mediated Execution | System FoundationAI-Ready Enterprise SemanticsSemantic Governance Operating ModelSemantic Contract Surface | How Governed Representations Become Institutional Meaning | Semantic Architecture | Reference Architectures and Control Mechanisms | Governed representation → governable understanding | Constitutional Function | Turns represented reality into governable understanding so institutional meaning can survive interpretation, AI use and operational change. | ||||||||||||
Published | Highest | Enterprise Architecture | Institutional Continuity | CIOCTOChief ArchitectCDAOAI GovernanceData GovernancePlatform LeadersRisk | Published | Institutional Continuity Under AI-Mediated Execution | Enterprise Intelligence ArchitectureSystem FoundationSemantic Contract SurfaceExecution Admissibility ArchitectureAI-Ready Enterprise SemanticsArchitecture AuthorityArchitectural SurvivabilityAI Agents | From Information Transport to Institutional Continuity | Category-defining control architecture | Reference Architectures and Control Mechanisms | Accepted Architecture → Conformant Operational Implementation | Constitutional Governance Mechanism | Preserve governance continuity across the complete architecture | Continuity coherence | Accepted architecture and runtime participation | Continuity proof across the chain | Does not replace the chain or execute actions | Constitutional Architecture of Enterprise Intelligence | Preserves continuity of identity, meaning, authority, permitted use, lineage and accountability across operational change. | ||||||
Future Research | Authority Continuity, Runtime Context Change and the Erosion of Admissible Execution | Failure Mode | Doctrine and Failure Modes | Runtime context change → legitimacy erosion | Constitutional Constraint | Identifies drift between execution and legitimacy so institutions can preserve authority and accountability as conditions change. | |||||||||||||||||||
Published | Highest | Enterprise Architecture | Institutional Intelligence | CIOCTOChief ArchitectCDAOAI GovernanceRiskBoardsEnterprise ArchitectureData GovernanceAI Architecture | Published | Institutional Intelligence Under AI-Mediated Execution | Enterprise Control PlaneExecution Admissibility ArchitectureArchitecture of RecordSCIA RuntimeAI AgentsAuthorityPermitted UseProvenanceLineageDecisionOutcome | From Operational Reality to Governed Action and Revised Representation | Capstone Reference Architecture | Reference Architectures and Control Mechanisms | Operational Reality → Governed Action → Revised Representation | Capstone Architecture | Define the complete enterprise-facing operating architecture | Enterprise coherence | Operational Reality | Governed Action and Revised Representation | Does not replace subordinate constitutional responsibilities | Constitutional Architecture of Enterprise Intelligence | Enterprise Intelligence Architecture defines how operational reality becomes represented reality, accepted meaning, declared reliance, governed decision, authorised consequence and revised representation without losing institutional continuity. | Capstone enterprise-facing reference architecture for representing, governing, coordinating, executing, evidencing and revising institutional intelligence under AI-mediated execution. | Defines the constitutional operating model through which Architectural Survivability is realised across representation, memory, context, coordination, governance and legitimate execution. | ||||
Future Research | How Legitimacy Propagates Beyond the Original Control Boundary | Failure Mode | Doctrine and Failure Modes | Local admissibility → downstream consequence propagation failure | Constitutional Constraint | Identifies how consequence escapes institutional control, helping preserve legitimate action and accountability at execution boundaries. | |||||||||||||||||||
Published | Delegated Meaning and the Architecture of Institutional Sovereignty | Doctrine | Doctrine and Failure Modes | Delegated capability → preserved institutional sovereignty | Constitutional Constraint | Preserves institutional governability by defining what must remain under legitimate authority when capability is delegated. | |||||||||||||||||||
Published | High | Enterprise Architecture | Execution Admissibility | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Ready to Publish | Institutional Legitimacy Under Distributed AI-Mediated Cognition | Execution Admissibility ArchitectureSCIARuntime GovernanceInstitutional Legitimacy | Alignment as the Foundation of Coherent Action in AI-Mediated Systems | Doctrine | Doctrine and Failure Modes | Meaning → execution → admissibility | Constitutional Function | Defines the Alignment Architecture as a three-layer model connecting Meaning, Execution, and Admissibility to preserve coherence in AI-mediated systems, and positions admissibility as the control boundary where consequence-bearing action must be permitted before it binds. | • How does meaning become action without losing coherence? • What architectural boundary prevents automation from binding consequence without admissibility? • How do meaning, execution intent, authority, and evidence remain connected at T=0? • How does alignment drift become execution risk? | Position Alignment Architecture as the bridge between Codex Resonance research lineage (coherence, meaning, lineage, trust, constraint) and Arqua’s execution-admissibility architecture, clarifying why admissibility is necessary in AI-mediated execution environments. | • Execution Admissibility Architecture • Architecture of Record • SCIA Runtime • Execution Passports • The Desynchronization of Authority • From Codex Resonance to Arqua | Preserves alignment between meaning, purpose, execution and admissibility as institutional action moves toward consequence. | ||||||||
Published | High | Institutional Governance | Execution Admissibility | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Ready to Publish | Institutional Legitimacy Under Distributed AI-Mediated Cognition | SCIAExecution Admissibility ArchitectureAuthority ContinuityRuntime GovernanceInstitutional Legitimacy | Why AI-mediated execution requires Execution Admissibility at T=0 | Failure Mode | Doctrine and Failure Modes | Point-in-time authority → runtime admissibility requirement | Constitutional Constraint | Explains why AI-mediated execution widens the gap between point-in-time authority and consequence-binding action, and introduces Execution Attribution Collapse and the Execution Passport pattern as part of Execution Admissibility Architecture at T=0. | • Execution Attribution Collapse • Execution Passports • Architecture of Record • SCIA Runtime | Identifies how authority can desynchronise from execution, helping preserve legitimate action through operational change. | ||||||||||
Planned | High | Enterprise Architecture | AI-Mediated Cognition | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | Execution Admissibility ArchitectureRuntime GovernanceInstitutional LegitimacyEnterprise Intelligence ArchitectureEnterprise Control Plane | When enterprise meaning becomes operational in AI-mediated systems | Semantic Architecture | Reference Architectures and Control Mechanisms | Enterprise meaning → AI-mediated operational context | Representation Foundation | This paper argues that in AI-mediated enterprise systems, ‘meaning’ becomes operational: semantic models participate directly in orchestration, recommendations, and execution pathways. It connects semantic drift and abstraction compression to legitimacy failures at the moment consequence binds, and frames AI-ready semantics as a prerequisite for execution admissibility architecture. | • How does semantic abstraction become an execution surface? • How do institutions prevent semantic drift from becoming authority drift? • What semantic controls are required for admissible execution? • How do data products, ontologies, and runtime context models participate in governance at T=0? | Explain how semantic structures (definitions, ontologies, metadata, and context models) become execution-participating components in AI-mediated workflows, shaping admissibility decisions and institutional legitimacy. | • The Desynchronization of Authority • Execution Attribution Collapse • From Data Governance to Execution Admissibility | Preserves AI-ready institutional meaning by grounding data access, semantics and use in accepted enterprise representation. | ||||||||
Planned | High | Institutional Governance | Institutional Legitimacy | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | Authority ContinuityRuntime GovernanceInstitutional LegitimacyExecution Admissibility ArchitectureEnterprise Intelligence ArchitectureEnterprise Control Plane | Preserving authority coherence before irreversible execution | Failure Mode | Doctrine and Failure Modes | Authority lifecycle → integrity requirement | Constitutional Governance Mechanism | This paper introduces Authority Lifecycle Integrity as the structural discipline of ensuring that authority remains valid, scoped, reconstructable, and enforceable across organisational time and distributed system execution. It connects authority drift, stale approvals, and AI-mediated temporal compression to the need for runtime admissibility validation at the commit boundary. | • How does authority decay across time and system boundaries? • What are the dominant authority drift patterns? • What controls preserve authority coherence without slowing execution to a halt? • How should organisations model authority capacity, scope, and expiry? • How is authority continuity enforced in distributed AI-mediated systems? | Define Authority Lifecycle Integrity as the discipline of keeping authority coherent across time, transformations, delegation, and system boundaries until execution admissibility is resolved at T=0. | • The Desynchronization of Authority • Execution Attribution Collapse • Governance Survivability and the Limits of Institutional Recomputation | Preserves authority continuity by ensuring authority remains valid, traceable and lifecycle-aware through operational change. | ||||||||
Planned | High | Runtime Governance | Execution Admissibility | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | SCIAExecution Admissibility ArchitectureRuntime GovernanceAuthority ContinuityInstitutional LegitimacyEnterprise Intelligence ArchitectureEnterprise Control Plane | Runtime control point for execution admissibility at T=0 | Runtime Architecture | Reference Architectures and Control Mechanisms | Runtime context → admissibility decision at T=0 | Constitutional Constraint | This paper frames SCIA Runtime as the non-bypassable evaluation point that determines whether a specific consequence-bearing action is admissible at T=0 given current authority, evidence, context, constraints, and state. It argues that future governance must be expressed as runtime architecture, not only as meetings, policies, and retrospective oversight. | • What does SCIA Runtime validate at T=0? • What are the typed outcomes and escalation paths? • How does SCIA Runtime differ from workflow approvals and policy engines? • What evidence and context are required to make admissibility defensible? • How is auditability preserved without reducing the model to paperwork? | Describe SCIA Runtime as the admissibility evaluator at the commit boundary, including typed outcomes (admit, admit-with-conditions, escalate, refuse, unresolved) and the governance implications of runtime validation. | • The Desynchronization of Authority • Execution Passports • Architecture of Record | Preserves the legitimacy of consequential institutional action at the runtime moment consequence may bind. | ||||||||
Planned | High | Enterprise Architecture | Execution Admissibility | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | Execution Admissibility ArchitectureAuthority ContinuityRuntime GovernanceInstitutional LegitimacyEnterprise Intelligence ArchitectureEnterprise Control Plane | Mapping where institutional consequence binds | Runtime Architecture | Reference Architectures and Control Mechanisms | Institutional systems → consequence map | Constitutional Governance Mechanism | Describe accepted architecture, authority, applicability and execution boundaries | Authority and standing coherence | Proposed architecture, models, representations and consequence boundaries | Accepted architecture, authority, applicability and execution boundaries | Does not assemble runtime context or preserve institutional memory | Constitutional Architecture of Enterprise Intelligence | This paper formalises Architecture of Record (AoR) as the structural map of where institutional consequence binds and where execution control must exist. It shows how AoR turns governance intent into an explicit boundary architecture that supports admissibility evaluation, escalation, refusal, and reconstructability at the moment execution becomes consequence-bearing. | • How do institutions identify where consequence binds? • What are the recurring commit boundary types across enterprise systems? • How do AoR boundaries map to authority, evidence, context, constraints, and state requirements? • How does AoR prevent ‘approval drift’ across downstream execution? | Define Architecture of Record (AoR) as the map of consequence-binding boundaries and the locations where admissibility must be resolved, so governance can be operationalised at execution surfaces rather than only in meetings. | • The Desynchronization of Authority • Execution Passports • From Data Governance to Execution Admissibility | Preserves accepted architectural standing, authority and consequence boundaries as institutional conditions change. | ||
Planned | High | Institutional Governance | Authority-State | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | SCIAExecution Admissibility ArchitectureAuthority ContinuityRuntime GovernanceInstitutional LegitimacyEnterprise Intelligence ArchitectureEnterprise Control Plane | How authority-state travels to the commit boundary | Evidence Pattern | Reference Architectures and Control Mechanisms | Authority-state → evidence at the commit boundary | Constitutional Mechanism | This paper develops the Execution Passport pattern as the minimal portable authority-state bundle that accompanies consequence-binding actions to the commit boundary (T=0) for SCIA Runtime validation. It explains why approvals and permissions are insufficient when authority decays under changing evidence, context, and state, and proposes passport-based admissibility as a reconstructable, expirable, and enforceable authority continuity mechanism. | • What must an Execution Passport carry to enable admissibility at T=0? • How does an Execution Passport differ from approval tokens, IAM permissions, and audit logs? • How is expiry, revocation, scope, and escalation represented? • How does the passport remain reconstructable after execution? • How do institutions govern passport issuance and validation? | Define the Execution Passport pattern as the portable authority-state bundle that must survive from decision to execution, and specify the minimum admissibility-carrying payload required for runtime validation at T=0. | • The Desynchronization of Authority • Execution Attribution Collapse • Governance Survivability and the Limits of Institutional Recomputation | Preserves execution legitimacy by carrying authority, context, evidence and permitted-use conditions toward action. | ||||||||
Research Backlog | High | Institutional Governance | AI-Mediated Cognition | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | SCIAExecution Admissibility ArchitectureAuthority ContinuityRuntime GovernanceInstitutional Legitimacy | Distributed Cognition, AI-Mediated Judgment, and the Emerging Legitimacy Crisis | Failure Mode | Doctrine and Failure Modes | Distributed cognition → attribution failure | Constitutional Constraint | Traditional institutional governance assumes that the entity authorized to act is also the entity meaningfully performing judgment. AI-mediated execution architectures increasingly dissolve this coupling, distributing cognition across retrieval systems, orchestration layers, reasoning agents, semantic abstractions, and machine-generated summaries. This paper introduces Execution Attribution Collapse as an emerging governance failure mode in which procedural legitimacy remains visible while substantive cognitive ownership fragments beneath operational execution. The paper argues that future governance architectures must evolve from retrospective oversight toward continuously maintained execution legitimacy attached to operational reality at the moment consequence binds. | • Where does meaningful judgment originate in distributed AI systems? • Can authoritative judgment still be reliably located? • How does distributed cognition weaken traditional accountability assumptions? • Why is explainability insufficient for institutional legitimacy? • What is Execution Attribution Collapse? • What governance capabilities are required to preserve cognitive ownership at T=0? | Distributed CognitionExecution Attribution CollapseCognitive CeremonialismRuntime LegitimacyAuthority ContinuityInstitutional AdmissibilityAI-Mediated ExecutionCognitive Ownership | Investigate how AI-mediated execution architectures fragment meaningful judgment across retrieval systems, orchestration layers, reasoning agents, memory architectures, semantic abstractions, and partial human review, creating conditions where institutions can no longer reliably determine where authoritative judgment originated. | • The Collapse of Traditional Institutional Authority Assumptions Under Distributed AI-Mediated Cognition • From Data Governance to Execution Admissibility • The Desynchronization of Authority | Identifies attribution collapse so accountability remains reconstructable when AI-mediated execution distributes action across actors and systems. | |||||||
Research Backlog | High | Institutional Governance | AI-Mediated Cognition | Enterprise ArchitectureRiskGovernanceRegulatorsBoards | Concept Approved | Institutional Legitimacy Under Distributed AI-Mediated Cognition | SCIAExecution Admissibility ArchitectureAuthority ContinuityRuntime GovernanceInstitutional Legitimacy | Decision-Condition Recoverability, Complexity Compression and Institutional Legitimacy | Survivability Doctrine | Doctrine and Failure Modes | Operational pressure → legitimacy recomputation failure | Constitutional Function | As institutions become increasingly dependent on AI-mediated cognition and distributed decision architectures, they face a previously underexplored failure mode: the gradual erosion of their ability to recompute legitimacy itself. This paper introduces Governance Survivability, Decision-Condition Recoverability, and Legitimacy Constructability as concepts describing the conditions required to continuously reconstruct valid authority, evidence, context, and accountability under changing operational realities. It argues that future governance architectures must preserve not only admissibility itself, but also the institutional capacity to re-establish admissibility under increasing complexity and compression. The ultimate governance challenge may become not controlling execution, but retaining the ability to determine what legitimate execution means at all. | • Can institutions always recompute legitimacy? • What happens when admissibility cannot be reconstructed in time? • What is Governance Survivability? • What is Decision-Condition Recoverability? • How do institutions preserve legitimacy-generating capacity? • What are the limits of institutional recomputation? | Governance SurvivabilityDecision-Condition RecoverabilityLegitimacy ConstructabilityInstitutional Recomputation CollapseConstructability FailureCompression ThresholdsRuntime AdmissibilityOperational Legitimacy | Explore how institutions may eventually lose the capacity to reconstruct legitimacy under conditions of increasing complexity, AI-mediated cognition, temporal compression, and distributed operational reasoning. | • Execution Attribution Collapse • The Collapse of Traditional Institutional Authority Assumptions Under Distributed AI-Mediated Cognition • Semantic Authority Collapse • The Desynchronization of Authority | Preserves governance continuity by showing where institutional recomputation fails under operational change. |