Authority Pattern Library · Architecture
AA-14 · Core Authority Failure
A convincing account is not itself permission
An explanation can support understanding, challenge and review. It may describe why a proposal was formed or what evidence supports a conclusion. Those contributions do not by themselves establish authority for a consequential action.
The concern is substituting persuasiveness, coherence or retrospective justification for the applicable permission basis.
Separate the propositions
What is proposed? What evidence supports it? Who may rely upon the interpretation? Who or what may authorise the selected operation, under which conditions?
An explanation may answer part of this inquiry. Its author, an AI model or a source document does not acquire decision rights simply by providing a useful account.
Preserve authority and participation
Connect the exact proposal to the relevant mandate or delegation and any required human judgement. Where the proposal or material circumstances change, establish whether renewed consideration is required.
A recorded approval is evidence of an interaction; its sufficiency depends on the person's authority, information and practical ability to influence the proposal.
Keep later judgement distinct
Later review may clarify evidence, correct records or make a new decision. Any legal effect of ratification or other retrospective process depends on the applicable authority and regime; this article makes no universal legal claim.
An account written later should not be presented as contemporaneous permission unless the evidence supports that conclusion.
Learn without rewriting
Preserve the original basis, actual operation, observed outcome and subsequent interpretation. That history supports governed learning while keeping explanation, authority and execution distinguishable.
Related patterns and contexts
- Authority Before Action as a Structural Constraint
- Authority Without Traceability
- Context Is Not Authority
Architecture and scope
Architecture of Record (AoR) records accepted standing, applicability and obligations. Execution Admissibility Architecture explains execution admissibility. Their publication is not evidence of deployed controls or a requirement for one runtime.
This is an explanatory pattern, not an organisational assessment, issued Profile, legal opinion, compliance determination or implementation assurance.
© Arqua Pty Ltd. All rights reserved.