Authority Pattern Library

Architecture · Applications

Recognise how authority and action can diverge

The Authority Pattern Library explains recurring relationships between understanding, authority, human participation and consequential action. Use it to recognise a possible condition, explore its architectural significance and follow a relevant operating context.

A pattern is an explanatory lens. Its presence in this library does not establish that it occurs in a particular organisation, causes an observed problem or requires an Arqua product.

Choose a reading path

• Explore a pattern: use the grouped directory below to follow an architectural concern across sectors.
• Explore an operating context: begin with a concrete setting, then follow the patterns relevant to its circumstances.
• Explore a sector: Applications provides the broader Enterprise Intelligence view.

For code names and classification definitions, use Authority Pattern Library — Code Registry.

Explore authority patterns

AA codes identify stable pattern references. The classifications organise reading; they are not canonical architecture layers, maturity levels or a mandatory failure sequence. A pattern can relate to several concerns while retaining one primary directory classification.

Foundational Authority Constraint

Conditions that keep authority applicable to consequential action.

Authority Failure Mode

Ways declared authority and operational action can diverge.

Core Authority Failure

Substitutions in which explanation, context, caution or visible process is treated as sufficient authority.

Downstream Symptom

Operating behaviours that may reveal an authority gap, while also serving legitimate purposes.

Boundary Condition

Limits of relying on retrospective governance to establish permission.

Applied Pattern

A recurring authority concern examined in a particular class of work.

Explore operating contexts

AOC codes identify bounded illustrations. A context can involve several patterns; it is not a new architecture, issued Sector Profile, client assessment or implementation claim.

Financial services

Government, sovereign and statutory environments

Infrastructure and energy

Read a pattern in context

Ask which subject, proposed action, purpose and time the description concerns. Distinguish what is represented, what may be relied upon, what is authorised, what actually occurred and what the observed result establishes.

Escalation, discretion, review and non-action can be appropriate controls. They are not evidence of failure merely because they occur. Existing human, native or composed arrangements may satisfy the relevant responsibility.

The library does not imply that every organisation requires one runtime or a fixed sequence of controls. The Architecture gateway provides the capstone and authoritative definitions.

Recommendation integrity

A recommendation may inform consequential action before an execution request exists. Examine its source evidence, assumptions, permitted reliance, AI contribution, relevant human judgement and conditions that must remain true.

A traceable recommendation is not guaranteed to be correct and does not grant permission to execute. Its standing and later use remain governed by the institution.

Continue exploring

• Banking & Financial Services — a sector reading path.
• Authority Before Action as a Structural Constraint — authority applicable to the exact action.
• Architecture of Record (AoR) — record accepted standing, applicability and obligations.
• Request a Briefing — discuss a defined operational situation.

This library is explanatory. It does not establish compliance, conformance, operational assurance, implementation or a relationship with a named organisation. Each linked page retains its own scope and standing.

© 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™, Pre-Execution Pressure Test™, Authority Pressure Test™, and associated architectural terminology may be trademarks, registered trademarks or protected intellectual property of Arqua Pty Ltd.