ARQUA • No access • Structural Context Library • Request a Briefing
Context Classification
Context Code: AA-11
Pattern Name: Decision–Execution Decoupling
Layer: Foundational Authority Constraint
Structural Pattern: Decision–Execution Decoupling
Primary Condition: Decision outputs detached from execution surfaces
Institutional Behaviour: Triggers execute without authority verification
Execution Question: Is an upstream decision artefact being treated as permission to execute downstream?
Canonical Parent: Structural Context Library
Related Patterns: AA-01 Authority Before Action as a Structural Constraint; AA-02 Execution Sovereignty Failure; AA-10 Authority Drift; AA-07 Escalation as a Symptom of Missing Authority
Status: Foundational Authority Constraint
Boundary: This page is descriptive only. It is not an assessment, recommendation, case study, maturity model, assurance opinion, or claim about any organisation.
Required links
- Structural Context Library: Structural Context Library
- Canonical Definitions: Canonical Definitions — Execution Admissibility Architecture
- Execution Admissibility Architecture: Execution Admissibility Architecture
- Architecture of Record (AoR): Architecture of Record (AoR)
Context
Modern automated institutions frequently separate decision generation from execution systems. Decisions are produced as recommendations, scores, classifications, or triggers, and are then acted on by separate operational systems that can bind institutional consequence.
AI models, decision engines, and workflow automation often operate upstream of payments, contract management, entitlement disbursement, infrastructure automation, or other execution surfaces. The output may look advisory in one system while functioning as an execution precondition in another.
This separation creates a structural condition where authority is rarely defined at the point where institutional consequence actually binds. Authority may be described in policy, delegations, or governance artefacts, but the execution surface evaluates only whether a trigger is present, not whether the institution is authorised to commit in the specific context.
Without architectural control at this boundary, automated decisions can trigger execution without explicit authority verification. The institution then compensates through escalation, manual overrides, exception handling, and post-hoc review to reconstruct whether a commitment should have been permitted.
Related Contexts
- Authority Before Action as a Structural Constraint
- Execution Sovereignty Failure
- Audit and Review as Post-Hoc Authority Reconstruction
- Frontline Discretion Without Machine-Expressible Authority
- Escalation as a Symptom of Missing Authority
- Authority Drift
- Structural Context Library
© Arqua Pty Ltd. All rights reserved.