Authority Lineage

Institutional authority is not created by a system or inferred from system access.

For consequence-bearing execution, its source, delegation, applicable context, and current resolution must be explicit and traceable at the point where institutional consequence binds.

Authority Lineage defines how institutional authority is represented through source and delegation relationships and resolved for execution.

Definition

Authority Lineage is the structural chain through which the source, delegation and applicable conditions of institutional authority are represented and resolved at runtime.

It provides the architectural basis for tracing a consequence-bearing action to a legitimate source of authority; implementation performance must be established through evidence.

The Problem

Most enterprise systems assume authority implicitly.

Authority is often:

• embedded in roles
• inferred from system access
• distributed across workflows
• disconnected from execution

As automation scales, this creates ambiguity:

• who is allowed to act
• under what conditions
• on whose authority

This ambiguity becomes visible at execution.

Authority Structure

Authority lineage is composed of:

• Source Authority

(legal mandate, regulatory authority, institutional charter)

• Delegated Authority

(roles, systems, agents, workflows)

• Contextual Authority

(conditions under which authority applies)

• Execution Authority

(resolved authority at the point of commit)

Institutional authority is distinct from its system representation.

Its applicability is resolved in the current execution context.

Authority Resolution in SCIA

The SCIA Runtime reference architecture requires applicable authority to be resolved as part of admissibility evaluation.

At the commit boundary, the evaluation addresses:

• whether a legitimate source of authority is represented
• whether the delegation remains applicable in the current context
• whether the authority applies to the proposed action

Authority is evaluated with the other public admissibility categories:

• authority
• context
• constraints
• state
• evidence

The architectural requirement is that execution proceeds only when applicable authority is validly resolved. Evidence from a specific implementation is required to establish whether that implementation satisfies the requirement.

Authority and Architecture of Record

The Architecture of Record identifies:

• where institutional consequence binds
• which systems can execute
• where authority must be enforced

Authority Lineage connects those execution surfaces to:

• the source of authority
• the delegation chain
• the conditions under which authority is valid

Without Authority Lineage, execution surfaces operate without explicit authority.

Failure Without Authority Lineage

Without explicit authority lineage:

• authority is assumed rather than verified
• delegation chains are unclear
• escalation becomes a substitute for missing authority
• automated execution can occur without legitimate mandate

This creates institutional risk at execution.

Invariant

No action may bind institutional consequence unless authority can be resolved through a valid lineage at the point of execution.

Authority as Admissibility Dimension

Authority is not evaluated in isolation.

It is evaluated together with:

• state
• constraints
• context

The SCIA Runtime reference architecture requires authority to be:

• explicit
• contextual
• enforceable
• traceable

Evidence is required to assess whether an implementation meets these requirements.

Closing statement

Institutional authority does not originate from system access.

Authority Lineage represents its source, delegation and applicable conditions so it can be resolved at execution.

SCIA Runtime defines the reference-architecture requirement; each organisation remains responsible for implementation, operation and evidence that the requirement is met.

Explore the Architecture

• Execution Admissibility Architecture
• Architectural discipline governing proposed consequence-bearing execution.
• Execution Admissibility Architecture — Canonical Definitions
• Current public domain vocabulary and admissibility categories.
• SCIA Runtime Reference Architecture
• Public runtime reference architecture for Execution Admissibility.
• Pre-Execution Pressure Test
• Diagnostic that surfaces execution risk before consequence binds.

© Arqua Pty Ltd. All rights reserved.