GL-179 — Authority Registry

Open archive search
Archive registry entry

GL-179 — Authority Registry

Authority Registry glossary registry entry.

draftid: GL-179version: 0.1.0updated: 2026-06-24
Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation
Online

The section has a stable overview route and basic reader context.

Technical Layer
Online

A deeper technical overview is available.

Registry
Current

194 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

yamlScroll
---
schema_version: "1.0"
id: "GL-251"
title: "GL-251 — Authority Registry"
slug: "gl-251-authority-registry"
type: "glossary_term"
status: "draft"
version: "0.1.0"
last_updated: "2026-06-24"
summary: "An Authority Registry is a machine-readable record of who or what holds decision authority over a system, model, policy, guardrail, dataset, interface, or governance action."
canonical_url: "/archive/glossary/registry/gl-251-authority-registry"
citation_id: "gl-251-authority-registry-v0-1-0"
canon:
  tier: "registry"
  state: "draft"
  source: "UTS Glossary Simplified Registry"
  source_id: "GL-251"
classification:
  family: "Glossary"
  module: "AI Governance Terms"
  module_group: "Reference Systems"
  density: "Reference"
  audience:
    - "UTS readers"
    - "researchers"
    - "builders"
    - "AI readers"
    - "machine readers"
tags:
  - "glossary"
  - "registry"
  - "gl-251"
  - "authority-registry"
  - "ai-governance"
  - "auditability"
aliases:
  - "Authority Registry"
  - "Decision authority registry"
  - "Governance authority registry"
  - "AI authority registry"
related:
  laws:
    - "Guardrails as Epistemic Infrastructure"
    - "Temporal Audit Asymmetry"
    - "Hidden Debt Return Law"
  invariants:
    - "O ≠ Φ"
  operators:
    - "Au"
    - "Μ"
    - "Π"
    - "Γ"
    - "ℛ"
    - "Τ"
  gates:
    - "Au-Actuation"
    - "FI-Gate"
    - "HR-Gate"
    - "BΣ Validity"
    - "Τ Validation"
  diagnostics:
    - "Au"
    - "FI"
    - "H"
    - "O"
    - "legitimacy"
    - "authority_visibility"
    - "recurrence"
  failure_modes:
    - "Authority Obscurity"
    - "Interface Capture"
    - "Procedural Theater"
    - "Paper Coherence"
    - "AI Inversion"
  restoration_arcs:
    - "Legibility Restoration"
    - "Truth Reconstruction"
    - "Repair First AI Architecture"
    - "Temporal Proof Arc"
  modules:
    - "glossary"
    - "ai-governance"
  terms:
    - "Cognitive Infrastructure Governance"
    - "Signed Decision Provenance"
    - "Tamper-Evident Audit Trail"
    - "Interface Legitimacy"
    - "Auditability"
navigation:
  order: 251
  parent: "glossary"
  visible: true
provenance:
  created_from: "glossary-simplified-continuation"
  source_thread: "GLOSSARY-REFACTOR.md"
  source_file: "glossary-raw.docx"
  notes: "Continued AI Governance Terms sequence."
entry:
  term_id: "GL-251"
  term: "Authority Registry"
  term_class:
    - "AI Governance Term"
    - "Authority Visibility Structure"
    - "Auditability Mechanism"
  symbols:
    - "Au"
    - "Π"
---

1. Short Definition

An Authority Registry is a machine-readable record of who or what holds decision authority over a system, model, policy, guardrail, dataset, interface, or governance action.


2. Canonical Definition

In UTS, an Authority Registry makes governance authority visible.

It identifies the actors, roles, policies, models, committees, tools, contracts, datasets, and automated rules that can make or modify decisions.

Canonical purpose:

textScroll
authority visible
→ decision traceable
→ audit possible
→ repair assignable

Without an Authority Registry, governance decisions can be hidden behind interfaces, policies, models, or institutional abstraction.

Authority becomes untraceable, and repair becomes difficult.


3. Functional Role in UTS

Authority Registry supports:

  • AI governance
  • cognitive infrastructure governance
  • guardrail oversight
  • model release review
  • dataset governance
  • platform accountability
  • provenance tracking
  • appeal pathways
  • incident response
  • legitimacy restoration
  • responsibility-gradient mapping

It prevents authority from disappearing into system complexity.


4. Diagnostic Signatures

Authority registry active

textScroll
authority visible
decision owner identified
scope explicit
change history available
appeal path visible
Au↑
legitimacy↑

Authority obscurity

textScroll
decision made
but authority unclear
review path hidden
repair assignment blocked
H↑

Authority visibility restored

textScroll
owners mapped
decision surfaces registered
governance changes signed
repair responsibility assignable

5. Canonical Distinctions

Authority Registry is not org chart

An org chart shows hierarchy.

An Authority Registry shows decision authority and system control surfaces.

Authority Registry is not documentation alone

It must be usable for audit, review, repair, and responsibility mapping.

Authority Registry is not surveillance

It tracks governance authority, not private user interiority.

Authority Registry is not blame assignment

It makes responsibility traceable before consequence is assigned.


6. U-Layer Mapping

TableScroll
U-LayerAuthority Registry Expression
U0Infrastructure ownership and operational authority are recorded.
U1Resource authority over data, compute, access, and budgets is visible.
U2Permission, boundary, and policy authority are recorded.
U3Runtime control and deployment authority are visible.
U4Classification, guardrail, and narrative authority are recorded.
U5Change timing and review cadence are logged.
U6Field-level governance authority is made auditable.
U7Historical authority changes are preserved.
U8External regulatory and institutional authorities are mapped.

7. Common Failure Patterns Addressed

TableScroll
Failure PatternDescription
Authority ObscurityDecision power cannot be traced.
Interface CaptureInterface controls outcomes while authority remains hidden.
Procedural TheaterProcess exists but decision authority is unclear.
Paper GovernanceGovernance is documented but not operationally traceable.
Responsibility DiffusionNo actor can be held to repair obligations.

8. Restoration Implications

Authority Registry restoration requires mapping decision power before repair assignment.

Typical sequence:

textScroll
Μ map decision surfaces
→ identify authority holders
→ register scope and permissions
→ link authority to decisions
→ require signed provenance
→ expose review and appeal path
→ assign repair responsibility
→ Τ validate registry accuracy

Authority is coherent when decision power is visible enough to audit, challenge, and repair.


9. Machine-Readable Summary

yamlScroll
glossary_entry:
  id: "GL-251"
  term: "Authority Registry"
  symbols:
    - "Au"
    - "Π"
  short_definition: "A machine-readable record of who or what holds decision authority over a system, model, policy, guardrail, dataset, interface, or governance action."
  term_family: "AI Governance Terms"
  term_class:
    - "AI Governance Term"
    - "Authority Visibility Structure"
    - "Auditability Mechanism"
  canonical_purpose:
    - "authority visible → decision traceable → audit possible → repair assignable"
  diagnostic_positive:
    - "authority visible"
    - "decision owner identified"
    - "scope explicit"
    - "change history available"
    - "appeal path visible"
    - "Au↑"
    - "legitimacy↑"
  diagnostic_negative:
    - "decision made"
    - "authority unclear"
    - "review path hidden"
    - "repair assignment blocked"
    - "H↑"
  restoration_requirements:
    - "decision surface mapping"
    - "authority holder identification"
    - "scope and permission registration"
    - "decision-authority linking"
    - "signed provenance"
    - "review and appeal path exposure"
    - "repair responsibility assignment"
    - "time validation"