Inv 058

Archive registry entry

Inv 058

Authority is legitimate only when matched by responsibility, capability, transparency, and restoration.

draftid: invariants-inv-058version: 0.1.0updated: 2026-05-31
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

80 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.

INV-058 — Authority Requires Responsibility, Capability, Transparency, and Restoration

1. Definition

Authority is legitimate only when matched by responsibility, capability, transparency, and restoration.

Authority is the power to decide, direct, classify, constrain, allocate, enforce, represent, govern, interpret, deploy, or act on behalf of a system, node, role, public, domain, or affected population.

Authority is not self-validating.

Authority becomes coherent only when it is bound to four structural requirements:

responsibility
capability
transparency / auditability
restoration

Responsibility means the authority-bearing node is answerable for consequences.

Capability means the node has the real capacity to perform the authorized function.

Transparency / auditability means the exercise of authority can be inspected enough to govern it.

Restoration means harm, error, hidden debt, boundary damage, or recurrence created by authority can be repaired.

Therefore:

Authority requires responsibility, capability, transparency, and restoration.

Without these, authority becomes rank, control, domination, opacity, or legitimacy debt.


2. Purpose

This invariant prevents UTS from treating authority as legitimate merely because it exists.

Authority may be granted by:

  • law
  • office
  • expertise
  • contract
  • title
  • rank
  • election
  • ownership
  • credential
  • platform power
  • technical capability
  • symbolic role
  • model deployment
  • market position
  • emergency condition
  • community recognition
  • institutional structure

But the source of authority does not automatically make its use coherent.

The false assumption is:

Authority grants legitimacy.

The UTS correction is:

Authority is legitimate only when structurally bound to responsibility, capability, transparency, and restoration.

A system can hold authority while lacking the capacity to use it coherently.

A system can have responsibility in name but no traceable accountability.

A system can act transparently without repair.

A system can repair locally while preserving opaque recurrence pathways.

This invariant locks the authority sequence:

Authority → Responsibility → Transparency → Restoration → Legitimacy

Power must scale with responsibility.

Responsibility must be inspectable.

Transparency must connect to repair.

Repair must reduce recurrence.


3. Constraint Statement

Canonical Form

Authority requires responsibility, capability, transparency, and restoration.

Expanded Form

Any authority claim is admissible only when the authority-bearing node has
traceable responsibility, sufficient capability, adequate transparency or
auditability, and restoration capacity proportional to the consequences of
its decisions and actions.

Minimal Expression

No authority without responsibility and repair.

Governance Form

Authority is legitimate only when accountable, capable, auditable, and repair-backed.

AI Governance Form

AI-mediated authority requires traceability, capability limits, auditability, appeal, rollback, and restoration.

Security Form

Security authority requires scope, capability, audit, sunset, and repair.

Economic Form

Economic authority over labor, resources, platforms, or capital requires responsibility for externalized burden and repair.

CMS / Symbolic Form

Symbolic or sacred authority requires auditability, boundary integrity, and restoration capacity.

Restoration Form

Authority that cannot repair its consequences is not coherent authority.

4. Structural Logic

Authority expands consequence radius.

The larger the authority, the more nodes can be affected by its decisions.

Thus authority cannot be separated from consequence management.

A coherent authority structure requires:

decision power
        ↓
responsibility trace
        ↓
capability to execute the responsibility
        ↓
auditability / transparency
        ↓
restoration pathway
        ↓
legitimacy validation over time

The incoherent sequence:

authority granted
        ↓
responsibility diffuse
        ↓
capability assumed
        ↓
auditability limited
        ↓
restoration weak
        ↓
affected-node burden rises
        ↓
legitimacy debt accumulates
        ↓
authority requires coercive maintenance

The coherent sequence:

authority granted or claimed
        ↓
scope defined
        ↓
responsibility traced
        ↓
capability tested
        ↓
auditability established
        ↓
restoration capacity provisioned
        ↓
affected-node truth pathways opened
        ↓
legitimacy validated through time

Core insight:

Authority is a restoration obligation, not merely a decision right.

The higher the authority, the higher the duty to repair the consequences of its action.


5. State-Vector Impact

Protected State Variables

O   — coherence
Au  — auditability / transparency
R   — restoration capacity
BΣ  — boundary integrity
µᵢ  — meaning / agent integrity
K   — compatibility between authority scope and capability
H   — hidden debt

Primary Risk Variables

ι   — inversion when authority is mistaken for legitimacy
ε   — visible failure, abuse, scandal, backlog, harm, legitimacy shock
Φ   — authority, rank, enforcement success, compliance, control, reach proxy

Healthy Authority Pattern

authority↑
responsibility trace↑
capability verified
Au↑
R↑
BΣ↑
affected-node truth pathways↑
H contained
O stable or ↑

Violation Pattern

authority↑
responsibility trace↓
capability unverified
Au↓
R↓
BΣ↓
affected-node burden↑
H↑
ι↑
O↓

Authority-Legitimacy Inversion

Φ authority↑
legitimacy claim↑
Au↓
R↓
H↑
O↓
ι↑

The key inversion:

authority is mistaken for legitimacy.

Authority may command action.

It does not prove coherence.

Legitimacy Sequence

A coherent authority sequence can be written:

A_auth → Resp_trace → Cap_valid → Au_eff → R_eff → L_validated

Where legitimacy is validated only after responsibility, capability, auditability, and restoration are present.


6. U-Layer Localization

Primary Layer

U6 — Coherence Field

Authority affects legitimacy, trust, meaning, social coherence, role coherence, and public cognition.

Resource Layer

U1 — Power / Budgets

Authority must be backed by real capability: resources, skill, staffing, time, tools, knowledge, logistics, support, and restoration capacity.

Boundary Layer

U2 — Configuration / Boundaries

Authority must have scope. Unspecific authority becomes boundary overreach.

Execution Layer

U3 — Execution

Authority becomes real through decisions, enforcement, deployment, classification, allocation, intervention, or action.

Classification Layer

U4 — Classification / Metrics

Authority often operates through classification: who is eligible, responsible, safe, risky, legitimate, compliant, harmed, or repaired.

Coordination Layer

U5 — Coordination / Time

Authority must coordinate responsibility and validate consequences over time.

Memory Layer

U7 — Memory / Recurrence

Authority must update memory when its decisions create recurrence. Otherwise authority repeats harm.

Environment Layer

U8 — Environment / Forcing

Crisis, market pressure, political pressure, security pressure, or technological pressure often expands authority before capability and restoration are ready.

Common Failure Pattern

U8 pressure
        ↓
authority expands
        ↓
U2 scope unclear
        ↓
U4 categories enforce decisions
        ↓
U1 capability insufficient
        ↓
Au weak
        ↓
R weak
        ↓
U6 legitimacy debt rises
        ↓
U7 recurrence persists

Common Misdiagnosis

Authority failure is often misdiagnosed as:

  • lack of compliance
  • weak enforcement
  • poor messaging
  • insufficient authority
  • implementation failure
  • cultural resistance
  • public misunderstanding
  • isolated abuse
  • personnel failure
  • lack of trust
  • lack of expertise
  • slow bureaucracy

The deeper issue may be:

Authority exceeded responsibility, capability, transparency, or restoration.

7. Violation Signatures

7.1 Authority Without Responsibility Trace

The authority-bearing node can decide, command, classify, or enforce, but responsibility for consequences is diffuse or unclear.

authority↑
responsibility trace↓
H↑

This produces legitimacy debt.


7.2 Responsibility Without Capability

A node is assigned responsibility without the resources, tools, staffing, authority, or capacity needed to fulfill it.

responsibility↑
capability↓
failure risk↑

Responsibility without capability becomes burden displacement.


7.3 Capability Without Responsibility

A node can act powerfully but is not answerable for the consequences.

capability↑
responsibility↓
ι↑

This creates high-risk authority drift.


7.4 Transparency Without Repair

The system discloses or reports problems but does not repair them.

transparency↑
R↓
H unchanged

Transparency without restoration becomes exposure without repair.


7.5 Repair Without Transparency

The system claims to repair but keeps causality, scope, or recurrence pathways opaque.

repair claim↑
Au↓
restoration unvalidated

This creates pseudo-restoration.


7.6 Authority Scope Drift

Authority expands beyond its defined scope without renewed legitimacy checks.

scope↑
BΣ↓
legitimacy risk↑

This often occurs through emergencies, precedents, platform expansion, technical capability, or mission creep.


7.7 Appeal Pathway Missing

Authority affects nodes but provides no usable appeal, review, correction, or restoration process.

authority impact↑
appeal↓
R↓

Affected-node truth cannot enter.


7.8 AI-Mediated Authority Without Traceability

An AI system classifies, recommends, ranks, moderates, allocates, or automates decisions without sufficient traceability, appeal, or correction.

AI authority↑
Au↓
R↓
H↑

The system acts as authority without authority infrastructure.


7.9 Symbolic Authority Without Boundary Repair

A symbolic role claims interpretive or moral authority but cannot receive feedback, repair boundary violations, or reduce recurrence.

symbolic authority↑
BΣ↓
R↓
µᵢ↓

Meaning power becomes rank immunity.


7.10 Economic Authority Without Externality Repair

A company, platform, owner, lender, or market actor controls resources while externalized burden remains unrepaired.

economic authority↑
externality H↑
R↓

Ownership does not erase repair obligation.


Primary related failure modes:

  • Authority Without Responsibility
  • Responsibility Without Capability
  • Capability Without Responsibility
  • Transparency Without Repair
  • Repair Without Transparency
  • Scope Drift
  • Mission Creep
  • Appeal Pathway Absence
  • Authority-Legitimacy Inversion
  • Rank Immunity
  • Legitimacy Debt
  • Power-Repair Decoupling
  • Power-Meaning Decoupling
  • AI Authority Without Traceability
  • Security Emergency Overreach
  • Institutional Self-Validation
  • Symbolic Authority Capture
  • Economic Externality Authority
  • Responsibility Diffusion
  • Restoration Capacity Lag
  • Public Cognition Capture
  • Boundary Override
  • Hidden Debt Accumulation
  • Pseudo-Restoration

Primary restoration arcs:

  • Authority Responsibility Mapping
  • Responsibility Trace Restoration
  • Capability Validation
  • Scope Clarification
  • Auditability Restoration
  • Transparency-to-Repair Coupling
  • Restoration Capacity Rebuild
  • Appeal Pathway Restoration
  • Affected-Node Truth Reception
  • Boundary Reconstitution
  • Mission Creep Containment
  • Emergency Power Sunset
  • Legitimacy Restoration
  • Public Accountability Repair
  • AI Decision Trace Repair
  • Security Authority Review
  • Economic Externality Repair
  • Symbolic Authority Audit
  • Temporal Validation
  • Power Re-Binding

Restoration Requirement

Authority failures must be repaired by rebinding authority to responsibility, capability, transparency, and restoration.

Minimal sequence:

Identify authority claim
        ↓
Define scope
        ↓
Map responsibility trace
        ↓
Validate capability
        ↓
Restore auditability / transparency
        ↓
Build restoration capacity
        ↓
Open appeal and affected-node truth pathways
        ↓
Validate legitimacy over time

Authority should not expand while any structural requirement remains missing.


10. Domain Expressions

AI

AI systems increasingly exercise authority through:

classification
ranking
recommendation
moderation
memory interpretation
tool action
agent execution
eligibility screening
risk scoring
content filtering
resource allocation
workflow automation

If AI affects access, visibility, identity, opportunity, safety, meaning, or public cognition, then it carries authority-like consequence.

That authority requires:

  • responsibility trace
  • capability boundaries
  • auditability
  • appeal
  • correction
  • rollback
  • memory repair
  • affected-node truth reception
  • restoration capacity
  • recurrence monitoring

An AI system that can classify at scale but cannot repair misclassification at scale is authority without restoration.


AI Governance

AI governance authority includes:

who defines safety
who defines harm
who controls model behavior
who sets appeal rules
who controls memory
who determines acceptable use
who decides deployment
who can override users
who represents affected parties

Governance fails when authority is centralized but responsibility, auditability, and restoration remain weak.

Valid AI governance requires:

authority → responsibility → auditability → appeal → restoration → time validation

No lab, platform, regulator, or model class can claim legitimacy without this sequence.


Security

Security authority is often necessary but high-risk.

It includes:

monitoring
access restriction
account lock
surveillance
incident response
credential revocation
emergency override
threat classification
containment

Security authority requires:

  • defined scope
  • proportionality
  • audit logs
  • sunset where emergency-based
  • appeal where appropriate
  • affected-node repair
  • recurrence reduction
  • restoration after false positives
  • boundary integrity

Security authority without restoration trains bypass and legitimacy loss.


Governance / JGL

Governance authority includes law, policy, adjudication, enforcement, administration, public office, and institutional representation.

Governance legitimacy requires:

authority matched by responsibility
responsibility backed by capability
capability made auditable
auditability routed to repair
repair validated over time

A governance body cannot coherently demand trust if it cannot repair harm caused by its own authority.

Authority that cannot receive truth from affected nodes is structurally unstable.


Economy

Economic authority appears through:

ownership
capital allocation
debt issuance
platform control
pricing power
labor control
supply-chain control
contract design
market access
resource gating

Economic authority requires responsibility for:

  • externalities
  • labor burden
  • dependency lock
  • community effects
  • ecological burden
  • financial risk
  • repair pathways
  • transition support
  • meaningful exit

Ownership grants control, not exemption from repair.

Economic authority becomes extractive when it can allocate burden without repairing it.


Biology / Medicine

Medical authority includes diagnosis, treatment prescription, protocol, intervention, institutional medical judgment, and classification of patient state.

Medical authority requires:

  • capability
  • whole-system humility
  • auditability of reasoning
  • attention to recurrence
  • boundary respect
  • informed consent
  • repair if intervention creates burden
  • time validation

A diagnosis or protocol has authority, but it does not replace ongoing evidence from organism response.

Medical authority must remain corrigible.


CMS / Meaning

Symbolic, moral, spiritual, or interpretive authority requires the same constraints.

It includes:

teaching
interpretation
ritual leadership
archetypal naming
spiritual guidance
moral judgment
community meaning
sacred role

Symbolic authority must be:

  • boundary-preserving
  • feedback-receiving
  • non-coercive
  • auditable enough for its consequence radius
  • repair-capable
  • humility-bound
  • time-validated

Sacred authority without restoration becomes symbolic rank capture.


Principles / Archetypes

Principles and archetypes can authorize action.

Examples:

Justice authorizes judgment.
Truth authorizes disclosure.
Protection authorizes constraint.
Healing authorizes intervention.
Sovereignty authorizes boundary.
Wisdom authorizes delay.

But each must be bound to responsibility, capability, transparency, and restoration.

Distortions:

Justice without restoration becomes punishment.
Truth without capability becomes harm.
Protection without transparency becomes control.
Healing without boundary becomes dependency.
Sovereignty without responsibility becomes rank.
Wisdom without transparency becomes opacity.

Principles are not authority exemptions.

They are constraint fields that increase responsibility.


Relationships / Couplings

Relational authority appears through:

caretaking
expertise
age
money
role
family position
sexual access
emotional influence
dependency
shared resources
social status
knowledge asymmetry

Relational authority is coherent only when:

  • responsibility is explicit
  • capability is real
  • boundaries are clear
  • repair is available
  • exit is viable
  • truth can be spoken
  • trust is time-validated

Asymmetry increases responsibility.

It does not create entitlement.


Project / Knowledge Systems

Knowledge authority appears when a framework, term, registry, canon entry, author, model, or module becomes reference-setting.

For UTS-style work:

canon authority requires canon responsibility

A canon construct must preserve:

  • definition clarity
  • operator mapping
  • state-vector mapping
  • failure-mode links
  • restoration links
  • auditability
  • version history
  • correction pathway
  • deprecation / supersession path

Framework authority without revision capacity becomes doctrine.


11. Scaling Behavior

As authority scales, responsibility, capability, transparency, and restoration must scale with it.

Authority↑ ⇒ Responsibility↑ + Capability↑ + Au↑ + R↑

Authority scaling increases:

affected-node count
consequence radius
repair burden
truth-reception burden
appeal burden
boundary risk
legitimacy stakes
recurrence cost

Scaling Risk Pattern

authority↑
capability assumed
transparency flat
restoration flat
affected-node burden↑
H↑
legitimacy debt↑

Valid Scaling Pattern

authority↑
responsibility trace↑
capability validated
Au↑
R↑
appeal↑
truth pathways↑
O preserved

Relation to INV-057

INV-057 states:

No rank immunity.

INV-058 adds:

Authority must be structurally bound to responsibility, capability, transparency, and restoration.

Together:

Authority increases invariant burden.

Relation to INV-060

INV-060 later generalizes the scaling structure:

High-Φ systems require proportional constraint.

INV-058 specifies the authority sequence:

authority must become accountable, capable, auditable, and repair-backed before legitimacy can stabilize.

12. Canonical Examples

Example 1 — AI Moderator With No Appeal

An AI moderation system can remove content or restrict accounts but provides weak appeal and unclear explanation.

authority↑
Au↓
R↓
legitimacy debt↑

The system exercises authority without restoration.


Example 2 — Emergency Power Without Sunset

A government or institution expands emergency authority but does not define scope, review, sunset, or repair for false positives.

authority↑
scope drift↑
BΣ↓
H↑

Emergency authority becomes legitimacy debt.


Example 3 — Manager Responsible Without Resources

A manager is held responsible for team outcomes but lacks staffing, budget, decision rights, or organizational support.

responsibility↑
capability↓
H exported

Responsibility without capability becomes burden displacement.


Example 4 — Company Controls Platform Access

A platform can remove vendors, creators, workers, or users from market access but has weak appeal or repair.

economic authority↑
affected-node repair↓
legitimacy debt↑

Platform authority requires restoration infrastructure.


Example 5 — Medical Protocol Overrides Response

A protocol determines treatment despite poor recurrence outcomes and weak patient feedback integration.

protocol authority↑
organism feedback↓
O unvalidated

Medical authority must remain time-validatable.


Example 6 — Symbolic Teacher Cannot Be Questioned

A teacher claims interpretive authority but cannot receive critique or repair boundary damage.

symbolic authority↑
Au↓
BΣ↓
µᵢ↓

Meaning authority becomes rank immunity.


Example 7 — UTS Canon Entry With No Revision Path

A canon construct shapes future modules but lacks a correction, deprecation, or supersession path.

canon authority↑
revision capacity↓
H↑

Knowledge authority requires restoration infrastructure.


13. Anti-Patterns

Anti-Pattern 1 — “Authority Equals Legitimacy”

Authority can exist without legitimacy.


Anti-Pattern 2 — “Responsibility Can Be Assigned Without Capacity”

Responsibility without capability is burden transfer.


Anti-Pattern 3 — “Transparency Is Enough”

Transparency must route to repair.


Anti-Pattern 4 — “Repair Can Happen Without Transparency”

Repair claims require enough auditability to validate debt reduction.


Anti-Pattern 5 — “Emergency Authority Needs No Review”

Emergency authority requires stronger scope, audit, sunset, and restoration.


Anti-Pattern 6 — “Technical Capability Grants Decision Authority”

Capability does not grant legitimacy without responsibility and repair.


Anti-Pattern 7 — “Ownership Means Authority Without Repair”

Ownership confers control, not exemption from externality repair.


Anti-Pattern 8 — “Expertise Closes the Loop”

Expertise guides the loop. Restoration and time validation close it.


Anti-Pattern 9 — “Symbolic Authority Is Above Process”

Symbolic authority requires more boundary discipline, not less.


Anti-Pattern 10 — “Canon Authority Means Stability”

Canon authority requires audit and correction pathways.


This invariant connects strongly to:

  • Authority Responsibility Law
  • Capability Responsibility Law
  • Transparency-to-Repair Law
  • Legitimacy Debt Law
  • No Rank Immunity Law
  • High-Φ Constraint Law
  • Power-Repair Decoupling Law
  • Power-Meaning Decoupling Law
  • Suppressed Auditability Debt Law
  • Emergency Normalization Law
  • Appeal Capacity Law
  • Boundary Override Law
  • Public Impact Repair Law
  • Restoration Capacity Scaling Law
  • Time Validates Law

Related scaling rules:

  • Authority Must Scale With Responsibility
  • Responsibility Must Scale With Capability
  • Transparency Must Scale With Consequence Radius
  • Restoration Must Scale With Authority
  • Appeal Capacity Must Scale With Decision Power
  • Emergency Power Requires Sunset and Audit
  • Public Authority Requires Public Repair Pathways
  • AI Authority Requires Traceability and Appeal
  • Security Authority Requires Scope and Restoration
  • Economic Authority Requires Externality Repair
  • Symbolic Authority Requires Boundary Integrity
  • Canon Authority Requires Revision Pathways
  • Capability Must Not Outrun Responsibility
  • Authority Scope Must Be Revalidated Under Scale

Relevant gates:

  • Authority Responsibility Gate
  • Capability Gate
  • Transparency / Auditability Gate
  • Restoration Capacity Gate
  • Legitimacy Gate
  • Appeal Capacity Gate
  • Boundary Integrity Gate
  • Scope Gate
  • Responsibility Trace Gate
  • Affected-Node Truth Gate
  • Emergency Override Gate
  • AI Authority Gate
  • Security Authority Gate
  • Economic Authority Gate
  • Symbolic Authority Gate
  • Canon Authority Gate
  • High-Φ Gate
  • Public-Impact Gate
  • High Risk Gate
  • Temporal Validation Gate

Gate Logic

An authority claim fails when:

authority lacks traceable responsibility

or when:

responsibility exceeds capability

or when:

authority cannot be audited enough to govern

or when:

authority creates harm it cannot repair

or when:

appeal or affected-node truth pathways are absent

or when:

scope expands without renewed legitimacy check

or when:

transparency does not route to repair

Gate failure returns:

Meaning:

authority claim or authority expansion is not currently admissible

The coherent response may be:

define scope
map responsibility
build capability
increase auditability
add appeal
build restoration capacity
limit authority
validate legitimacy over time

OperatorRelation
ΜMaps authority, responsibility, capability, affected nodes, and consequence pathways
ΣPreserves invariant boundaries around legitimate authority
ΠConstrains authority scope, emergency power, and overreach
Provides restoration capacity required for legitimate authority
ΞDetects authority-legitimacy inversion and responsibility diffusion
ΤTracks consequences and legitimacy over time
ΨAttends to affected-node truth signals suppressed by authority
ΘDampens overconfidence from rank, authority, expertise, or capability
ΛTests compatibility between authority scope and system capacity
ΓSelects limitation, expansion, reform, appeal, or restoration pathway
ΔStress-tests authority under contradiction, appeal, and failure
Authority-bearing coupling requires explicit scope and repair path
Valid result when authority is not admissible under current conditions

18. Machine-Readable Summary

id: UTS-INV-058
name: Authority Requires Responsibility, Capability, Transparency, and Restoration
registry: UTS Invariants Registry
category: Governance Invariant / Authority Invariant / Legitimacy Invariant / Restoration Invariant
status: Draft-Integrated
version: 0.1

definition: >
  Authority is legitimate only when matched by responsibility, capability,
  transparency, and restoration. Authority is the power to decide, direct,
  classify, constrain, allocate, enforce, represent, govern, interpret, deploy,
  or act on behalf of a system, node, role, public, domain, or affected
  population.

constraint: >
  Any authority claim is admissible only when the authority-bearing node has
  traceable responsibility, sufficient capability, adequate transparency or
  auditability, and restoration capacity proportional to the consequences of
  its decisions and actions.

canonical_form:
  - "Authority requires responsibility, capability, transparency, and restoration"
  - "No authority without responsibility and repair"
  - "Authority is legitimate only when accountable, capable, auditable, and repair-backed"
  - "Authority is a restoration obligation, not merely a decision right"
  - "Authority is not legitimacy"
  - "Transparency must route to repair"

authority_sequence:
  - "Authority → Responsibility → Transparency → Restoration → Legitimacy"

protects:
  - legitimate_authority
  - responsibility_traceability
  - capability_alignment
  - auditability
  - restoration_capacity
  - affected_node_truth_reception
  - boundary_integrity
  - appeal_capacity
  - public_trust
  - temporal_validation

state_vector_effects_when_preserved:
  O: "stable_or_increasing_under_authority"
  H: "contained_because_authority_is_repair_backed"
  ε: "visible_failures_are_repairable_and_traceable"
  ι: "decreases_because_authority_is_not_misclassified_as_legitimacy"
  Au: "increases_with_authority_scope"
  µᵢ: "preserved_because_authority_remains_meaning_bound"
  BΣ: "maintained_through_scope_and_boundary_clarity"
  K: "maintained_between_authority_scope_capability_and_responsibility"
  R: "scales_with_authority_and_consequence_radius"
  Φ: "authority_control_compliance_or_rank_not_misread_as_coherence"

state_vector_effects_when_violated:
  O: "decreases_as_authority_creates_unrepaired_consequences"
  H: "increases_through_unrepaired_decisions_and_responsibility_diffusion"
  ε: "appears_as_harm_backlog_abuse_scandal_or_legitimacy_shock"
  ι: "increases_when_authority_is_misread_as_legitimacy"
  Au: "decreases_when_authority_becomes_opaque"
  µᵢ: "degrades_when_authority_loses_meaning_or_agent_integrity"
  BΣ: "decreases_through_scope_drift_or_boundary_overreach"
  K: "declines_when_responsibility_exceeds_capability_or_scope"
  R: "insufficient_relative_to_consequence_radius"
  Φ: "may_rise_through_control_authority_compliance_or_enforcement_success"

primary_u_layer: U6
resource_layer: U1
boundary_layer: U2
execution_layer: U3
classification_layer: U4
coordination_layer: U5
memory_layer: U7
environment_layer: U8

violation_signatures:
  - authority_without_responsibility_trace
  - responsibility_without_capability
  - capability_without_responsibility
  - transparency_without_repair
  - repair_without_transparency
  - authority_scope_drift
  - appeal_pathway_missing
  - ai_mediated_authority_without_traceability
  - symbolic_authority_without_boundary_repair
  - economic_authority_without_externality_repair

related_failure_modes:
  - Authority Without Responsibility
  - Responsibility Without Capability
  - Capability Without Responsibility
  - Transparency Without Repair
  - Repair Without Transparency
  - Scope Drift
  - Mission Creep
  - Appeal Pathway Absence
  - Authority Legitimacy Inversion
  - Rank Immunity
  - Legitimacy Debt
  - Power Repair Decoupling
  - Power Meaning Decoupling
  - AI Authority Without Traceability
  - Security Emergency Overreach
  - Institutional Self Validation
  - Symbolic Authority Capture
  - Economic Externality Authority
  - Responsibility Diffusion
  - Restoration Capacity Lag
  - Public Cognition Capture
  - Boundary Override
  - Hidden Debt Accumulation
  - Pseudo Restoration

related_restoration_arcs:
  - Authority Responsibility Mapping
  - Responsibility Trace Restoration
  - Capability Validation
  - Scope Clarification
  - Auditability Restoration
  - Transparency To Repair Coupling
  - Restoration Capacity Rebuild
  - Appeal Pathway Restoration
  - Affected Node Truth Reception
  - Boundary Reconstitution
  - Mission Creep Containment
  - Emergency Power Sunset
  - Legitimacy Restoration
  - Public Accountability Repair
  - AI Decision Trace Repair
  - Security Authority Review
  - Economic Externality Repair
  - Symbolic Authority Audit
  - Temporal Validation
  - Power Re Binding

related_laws:
  - Authority Responsibility Law
  - Capability Responsibility Law
  - Transparency To Repair Law
  - Legitimacy Debt Law
  - No Rank Immunity Law
  - High Phi Constraint Law
  - Power Repair Decoupling Law
  - Power Meaning Decoupling Law
  - Suppressed Auditability Debt Law
  - Emergency Normalization Law
  - Appeal Capacity Law
  - Boundary Override Law
  - Public Impact Repair Law
  - Restoration Capacity Scaling Law
  - Time Validates Law

related_scaling_rules:
  - Authority Must Scale With Responsibility
  - Responsibility Must Scale With Capability
  - Transparency Must Scale With Consequence Radius
  - Restoration Must Scale With Authority
  - Appeal Capacity Must Scale With Decision Power
  - Emergency Power Requires Sunset And Audit
  - Public Authority Requires Public Repair Pathways
  - AI Authority Requires Traceability And Appeal
  - Security Authority Requires Scope And Restoration
  - Economic Authority Requires Externality Repair
  - Symbolic Authority Requires Boundary Integrity
  - Canon Authority Requires Revision Pathways
  - Capability Must Not Outrun Responsibility
  - Authority Scope Must Be Revalidated Under Scale

related_gates:
  - Authority Responsibility Gate
  - Capability Gate
  - Transparency Auditability Gate
  - Restoration Capacity Gate
  - Legitimacy Gate
  - Appeal Capacity Gate
  - Boundary Integrity Gate
  - Scope Gate
  - Responsibility Trace Gate
  - Affected Node Truth Gate
  - Emergency Override Gate
  - AI Authority Gate
  - Security Authority Gate
  - Economic Authority Gate
  - Symbolic Authority Gate
  - Canon Authority Gate
  - High Phi Gate
  - Public Impact Gate
  - High Risk Gate
  - Temporal Validation Gate

19. Compact Canon Statement

UTS-INV-058 states that authority requires responsibility, capability, transparency, and restoration. Authority is not self-validating and does not become legitimate merely because it is granted, inherited, elected, certified, owned, automated, sacred, institutional, or technically powerful. Authority is coherent only when its scope is defined, responsibility is traceable, capability is real, auditability is sufficient, affected-node truth can enter, and restoration capacity can repair its consequences. Authority without restoration becomes legitimacy debt.


20. Short Reference Version

UTS-INV-058 — Authority Requires Responsibility, Capability, Transparency, and Restoration

Authority is not legitimacy.

Valid authority requires:

responsibility
capability
transparency / auditability
restoration

Authority sequence:

Authority
→ Responsibility
→ Transparency
→ Restoration
→ Legitimacy

Violation patterns:

authority without responsibility
responsibility without capability
capability without responsibility
transparency without repair
repair without transparency
scope drift without review
appeal missing
authority without affected-node truth

Core rule:

Authority is a restoration obligation,
not merely a decision right.

Authority that cannot repair its consequences
is not coherent authority.