Execution Attribution Collapse

Authority Pattern Library · Architecture

AA-18 · Core Authority Failure

When process records cannot explain the executed action

Execution Attribution Collapse describes a broken evidential connection between an authorised judgement and the specific consequential action that occurred. A workflow may be logged, an approval recorded and a service account permitted to execute, while the records do not establish that the approval covered the exact action under the conditions that applied.

For example, a person may approve one version of a transaction while a later version is executed. The workflow history remains visible, but attributing that executed transaction to the earlier approval requires evidence of what changed and whether renewed authority was needed.

Reconstruct the connection

Relevant evidence can include:

The exact action, subject, version, time and execution result.
The actor or service involved and the capacity in which it acted.
The governing mandate, delegation, limits and conditions applicable at that time.
What a human participant actually reviewed, decided or approved.
Changes between judgement and execution, including any revalidation required.
The observed consequence, distinguished from the intended or reported outcome.

Technical access establishes a capability to execute. It does not necessarily establish the organisational authority for every use of that capability. Equally, a human approval is meaningful only in relation to what was reviewed and authorised.

Evidence gaps and authority defects are different findings

An incomplete record can prevent a reviewer from establishing authority. That does not, by itself, prove that authority was absent or that the action was unlawful. The investigation must distinguish an evidence gap, a broken link between records and action, and a demonstrated failure of an applicable control.

Compared with a general traceability gap, this pattern focuses on attribution to the exact executed action. Additional logs help only if they preserve the relevant connection. Existing workflow, identity, versioning and human controls may provide sufficient evidence without a separate runtime.

Related patterns

Authority Without Traceability — the broader relationship between authority and traceability.
Decision–Execution Decoupling — changes between decision and execution.
Authority Drift — authority changing over time.

Architecture and scope

The Architecture of Record (AoR) records accepted standing, applicability, obligations and boundaries. Execution Admissibility Architecture describes how authority and other applicable conditions relate to consequential action. These responsibilities may be met through existing systems, human controls or composed services; they do not require an Arqua runtime.

This is an explanatory architectural pattern, not an organisational assessment, deployment claim, assurance opinion or legal advice.