Authority Pattern Library · Architecture
AA-07 · Downstream Symptom
Escalation can reveal an unresolved authority question
Escalation may be an intentional and effective control: a case reaches a limit, requires specialist judgement or belongs with another authority. This pattern concerns escalation used repeatedly to compensate for an unclear responsibility or permission basis.
Its title is a lens for investigation, not a finding that every escalation signals missing authority.
Ask what is being escalated
Distinguish a request for more evidence, interpretation, authorisation, specialist advice or operational assistance. These are different needs and may have different responsible participants.
A senior person is not automatically the appropriate authority for every question. Preserve the exact proposal, relevant evidence, applicable conditions and decision sought through the handoff.
Keep the response bounded
An escalation needs an appropriate destination and a clear relationship between the response and subsequent operation. Changes to the proposal or material circumstances may require renewed consideration under the institution's rules.
The response may authorise a bounded action, request information, impose conditions, refuse the proposal or refer it elsewhere. Neither escalation nor refusal is universally the correct outcome.
Evidence and learning
Preserve who considered what, their authority and the resulting operation. Escalation volume alone does not diagnose architectural failure; workload, novelty, obligations and other causes must also be considered.
Where repeated unresolved questions are demonstrated, learning may improve representations, guidance, delegations or controls. It need not eliminate legitimate human review or require one runtime product.
Related patterns and contexts
- Frontline Discretion Without Machine-Expressible Authority
- Shadow Authority Formation
- Government & Sovereign AI Architecture
Architecture and scope
Architecture of Record (AoR) records accepted standing, applicability, obligations and relevant boundaries. Execution Admissibility describes a responsibility; no deployed SCIA control or mandatory additional runtime is established here.
This is an explanatory pattern, not a diagnosis of an organisation, issued Profile, legal opinion, compliance determination or implementation assurance.
© Arqua Pty Ltd. All rights reserved.