0. Civilization Interface Scope Note

This entry is conceptual and systems-oriented.

It does not make empirical claims about any specific civilization, institution, nation, platform, species, intelligence, contact event, or historical case. It names a UTS system pattern that may be used for modeling high-scale legitimacy, consent, representation, boundary governance, authority, and restoration dynamics.

1. Definition

Legitimacy drift across scales occurs when authority, consent, representation, responsibility, boundary rights, moral standing, mandate, jurisdiction, technical capacity, or protective role is treated as valid at one scale and then extended to another scale without renewed audit, consent, capacity, representation, or coherence validation.

A node may be legitimate in one domain.

It may be valid for one community, one interface, one territory, one function, one emergency, one contract, one species-layer, one technical layer, or one time window.

But that legitimacy does not automatically transfer to every adjacent scale.

The core failure is:

legitimacy valid at scale A
authority extends to scale B
consent / audit / representation not revalidated
H↑

Legitimacy drift is not ordinary scaling of governance.

It becomes a failure when the scope of action expands faster than the legitimacy conditions that made action valid.

In UTS terms, legitimacy is scale-bound unless revalidated.

Authority that crosses scale without revalidation becomes hidden debt.

2. Core Pattern

The core pattern is:

1. A system, institution, intelligence, platform, civilization, or governance node possesses legitimacy in a specific context.
2. That legitimacy arises from some combination of consent, competence, mandate, representation, trust, capacity, history, protection, contribution, or necessity.
3. The node begins acting at a larger, different, adjacent, or more abstract scale.
4. It treats the prior legitimacy as sufficient for the new scale.
5. The affected scope expands.
6. Consent, representation, auditability, repair capacity, and boundary governance do not expand proportionally.
7. Affected nodes become subject to authority they did not validate at the new scale.
8. Hidden debt accumulates as mandate inflation, representation gap, consent drift, boundary violation, or legitimacy shock risk.
9. The acting node may cite its prior legitimacy as evidence that expansion is valid.
10. Restoration requires scale-specific legitimacy revalidation.

This failure mode often appears when a system says:

we are already legitimate here

while the affected field asks:

who made that legitimacy valid over us, at this scale?

The issue is not legitimacy itself.

The issue is legitimacy being moved without its source conditions.

3. Failure Signature

Typical signature:

authority scope↑
scale fit↓
consent revalidation↓
representation gap↑
Au↓
repair capacity lag↑
H↑
legitimacy debt↑

Extended signature:

local mandate becomes global mandate
technical capacity becomes moral authority
emergency authority becomes standing authority
representation at one scale is claimed at another
affected nodes are added after authority is asserted
repair capacity does not scale with consequence
legitimacy claims become broader than legitimacy evidence

Common forms:

a local institution acts as if it represents a wider civilization
a platform treats user agreement as species-scale consent
technical access is mistaken for governance legitimacy
emergency permission becomes permanent authority
a protective mandate expands into control rights
a mediator becomes a ruler of the interface
a proxy claims standing for systems it cannot represent
repair obligations remain local while consequences become global

The key diagnostic is whether legitimacy conditions were revalidated at the scale where authority is now exercised.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: Capacity, leverage, infrastructure, or access expands faster than legitimacy.
• U2 — Configuration / Boundaries: Authority crosses jurisdictional, species-level, civilizational, platform, or interface boundaries without renewed governance.
• U3 — Execution: Decisions, enforcement, contact, representation, or intervention occur at the expanded scale.
• U4 — Information / Truth: Prior legitimacy is misrepresented as current cross-scale legitimacy.
• U5 — Coordination / Time: Temporary, emergency, or provisional authority persists beyond its valid window.
• U6 — Coherence Field: Trust and legitimacy degrade as scope expands without validation.
• U7 — Memory / Recurrence: Scale drift becomes precedent, doctrine, or institutional habit.

Common manifestation layers:

• U2 — Configuration / Boundaries: Scope boundaries blur.
• U4 — Information / Truth: Legitimacy claims outrun legitimacy evidence.
• U5 — Coordination / Time: Temporary legitimacy becomes permanent or scale-expanded.
• U6 — Coherence Field: Legitimacy debt destabilizes the wider field.

Legitimacy drift across scales is primarily a U4 / U6 legitimacy-scope failure.

The legitimacy story expands faster than the legitimacy reality.

5. Typical Development Sequence

A common development sequence is:

1. A node gains legitimate authority within a bounded scope.
2. The node succeeds, stabilizes, protects, mediates, governs, or coordinates within that scope.
3. The node encounters a larger-scale problem or opportunity.
4. It extends its authority outward.
5. The expansion is framed as natural, efficient, necessary, protective, technical, or inevitable.
6. Affected nodes at the new scale are not fully represented or consulted.
7. Audit mechanisms remain designed for the old scale.
8. Repair capacity remains insufficient for the expanded consequences.
9. The system normalizes expanded authority.
10. Hidden legitimacy debt accumulates.
11. A later challenge exposes that legitimacy did not scale.
12. Restoration requires mapping scope drift and revalidating authority with affected systems.

This sequence often creates the loop:

local legitimacy → scale expansion → affected-scope mismatch → legitimacy challenge → authority defends expansion

Another common loop is:

temporary authority → successful stabilization → permanent mandate claim → representation gap grows

The original legitimacy becomes a seed for illegitimate expansion.

6. Diagnostic Markers

Diagnostic markers include:

• Authority is exercised over a broader scope than the original consent or mandate covered.
• Affected nodes were not included in legitimacy formation.
• Technical capacity is used as evidence of governance authority.
• Emergency or temporary power becomes standing authority.
• Representation claims extend beyond actual representation mechanisms.
• Repair capacity is smaller than consequence scope.
• Audit mechanisms remain local while impact becomes cross-scale.
• Legitimacy claims rely on success at a different scale.
• Affected parties recognize the function but not the authority.
• Boundary violations are justified by prior mandate.
• The legitimacy claim becomes more abstract as affected scope widens.
• Challenges are treated as ignorance of necessity rather than evidence of drift.
• Time validation reveals growing legitimacy debt.

Useful diagnostics:

• Legitimacy Baseline: Measures what authority was actually recognized and by whom.
• Scale Fit: Tests whether authority matches the scale of consequence.
• Consent Integrity: Determines whether consent applies to the new scope.
• Representation Integrity: Tests whether affected systems are actually represented.
• Affected-Scope Mapping: Identifies all nodes affected by the expanded authority.
• Auditability: Determines whether authority can be inspected at the new scale.
• Authority / Capacity Ratio: Compares scope of authority to capacity for accountability and repair.
• Repair Capacity: Tests whether harm can be addressed at the expanded scale.
• Hidden Debt: Tracks unrepresented burden and legitimacy cost.
• Time Validation: Confirms whether legitimacy improves or degrades after expansion.

7. Related Gates

Relevant gates include:

• Legitimacy Gate: Fails when authority crosses scale without revalidation.
• Scale Gate: Fails when mandate, consent, audit, or repair capacity does not match scope.
• Consent Gate: Fails when consent valid at one scale is used at another.
• Representation Gate: Fails when affected systems are not represented at the scale of action.
• Auditability Gate: Fails when oversight remains smaller than consequence.
• Boundary Gate: Fails when scope boundaries are crossed without reciprocal governance.
• Restoration Gate: Fails when repair obligations do not scale with authority.

The first common gate failure is usually the Legitimacy Gate.

The action claims authority before authority has been made valid at the operating scale.

8. Related Operators

Relevant operators include:

• Au — Auditability: Determines whether cross-scale authority can be inspected.
• BΣ — Boundary Integrity: Governs scope boundaries and affected-system sovereignty.
• Γ — Selection: Selects which scale the actor treats as its mandate domain.
• Ψ — Observation / Interface: Determines which affected nodes are visible during legitimacy formation.
• O — Coherence: Declines when authority outruns recognition and repair.
• H — Hidden Debt: Accumulates as unrepresented consequence and consent debt.
• K — Constraint / Load: Rises on affected nodes subject to unvalidated authority.
• R — Restoration Capacity: Must scale with expanded consequence.
• Τ — Trajectory / Time: Reveals whether legitimacy stabilizes or drifts further.
• µᵢ — Memory / Identity: Stores the node’s self-understanding as legitimate across scale.
• ℛ — Restoration: Requires scale-specific legitimacy repair.

Legitimacy drift across scales often follows this operator pattern:

authority valid in bounded scope
Γ selects expanded scope
BΣ scope boundary crossed
Au / consent not scaled
affected nodes underrepresented
H legitimacy debt accumulates
O degrades across field
Τ reveals shock risk

9. Related Laws and Invariants

Related Laws

• Legitimacy Shock Cascade: Hidden legitimacy debt can surface suddenly when affected nodes reject authority.
• Hidden Debt Accumulation: Unrepresented scope creates deferred repair cost.
• Auditability Collapse: Oversight fails when action scale exceeds audit scale.
• Consent Drift: Consent valid in one context becomes invalid when scope changes.
• Success Proxy Substitution: Success at one scale is used as proof of authority at another.
• Boundary Collapse: Scope boundaries are crossed without coherent governance.
• Temporal Audit Asymmetry: Temporary authority may become normalized before debt is visible.

Related Invariants

• Legitimacy Does Not Automatically Transfer Across Scale: Mandate must be revalidated.
• Consent Must Be Revalidated When Scale Changes: Affected scope changes consent requirements.
• Authority Must Scale With Auditability: More consequence requires more inspection.
• Representation Must Match Affected Scope: Those affected must have standing.
• Cross-Scale Action Requires Cross-Scale Repair Capacity: Authority without repair capacity creates debt.
• Legitimacy Must Be Time-Validated After Expansion: Recognition must hold beyond initial justification.

10. Common False Positives

Not every authority expansion is legitimacy drift.

Common false positives include:

• Explicitly delegated authority with scale-valid consent.
• Federated representation that includes affected scope.
• Emergency authority that remains time-bound, audited, and repairable.
• Technical coordination without governance claims.
• Voluntary expansion with informed participation and exit.
• Scale transition accompanied by proportional audit and repair capacity.
• A mandate that was designed from the start for the larger scope.
• Provisional action that triggers immediate revalidation rather than permanent authority.

Clarifying rule:

This is not legitimacy drift across scales unless authority, consent, representation, responsibility, or boundary rights are extended to a new scale without sufficient renewed consent, auditability, affected-scope mapping, or repair capacity.

11. Common False Repairs

Common false repairs include:

• publishing a broader legitimacy statement without affected-scope consent
• adding advisory representation without decision power
• increasing communication while authority remains unvalidated
• treating success at the new scale as retroactive legitimacy
• using emergency justification after the emergency window closes
• offering opt-out where exit is structurally costly
• performing local repair for cross-scale harm
• expanding oversight but keeping it under the same authority
• redefining affected nodes as beneficiaries
• treating lack of resistance as consent
• relying on technical competence as moral mandate
• asserting inevitability instead of revalidating authority

False repair often produces the loop:

legitimacy challenged → authority publishes justification → affected scope still excluded → debt grows

Another common loop is:

scale drift exposed → advisory layer added → power unchanged → legitimacy debt persists

The system appears to respond while preserving the drift.

12. Restoration Direction

Restoration requires mapping the legitimacy source, identifying where scale drift occurred, revalidating consent and representation at the expanded scope, and scaling audit and repair capacity.

Primary restoration direction:

map legitimacy scope,
revalidate authority at the affected scale,
restore representation and auditability,
and scale repair capacity

A fuller restoration path includes:

1. Map original legitimacy. Identify where authority came from and what scale it validly covered.
2. Map the expanded action. Identify the new scope, affected nodes, consequences, and boundary crossings.
3. Identify the drift point. Locate where legitimacy was extended without revalidation.
4. Restore affected-scope mapping. Name all systems now impacted.
5. Revalidate consent. Seek scale-valid, informed, revocable, and context-rich consent.
6. Restore representation. Give affected nodes standing in governance, contestation, and revision.
7. Scale auditability. Make authority inspectable at the level where consequences occur.
8. Scale repair capacity. Ensure harm can be repaired at the same scale as action.
9. Reduce mandate inflation. Roll back claims that exceed validated authority.
10. Validate across time. Confirm legitimacy holds beyond initial justification, crisis, or success narrative.

A valid restoration path should reduce:

mandate inflation
representation gap
consent drift
scope opacity
authority / capacity mismatch
audit lag
repair insufficiency
boundary violation
legitimacy debt
shock risk

Legitimacy drift is not repaired by making expanded authority more eloquent.

It is repaired when authority returns to the scale where it is actually valid, or becomes valid at the scale where it acts.

13. Cross-Module Links

• Civilization Interface: Standalone expression of cross-scale legitimacy drift and mandate inflation.
• Security: Related to emergency normalization, interface capture, proxy abuse, and invalid authorization.
• Justice / Contracts: Related to manufactured consent, enforcement capture, amnesty without repair, and post-signing incoherence.
• Restoration: Requires legitimacy restoration, consent repair, representation repair, and repair capacity scaling.
• Governance: Shows how valid authority becomes invalid when its scale changes without revalidation.
• Coherence: Demonstrates that legitimacy is a coherence relation between authority, affected scope, and repair capacity.
• Diagnostics: Requires scale fit, consent integrity, representation integrity, and legitimacy baseline tracking.
• Meta Theory: Demonstrates that scale changes alter the truth conditions of authority.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• Legitimacy Shock Cascade
• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-004 — Auditability Collapse
• FM-CORE-005 — Boundary Collapse
• Consent Drift

Sibling or related Civilization Interface modes include:

• FM-CIF-001 — Unilateral Interface Capture
• FM-CIF-002 — Attribution Hijack
• FM-CIF-003 — Shielded Aggression Loop
• FM-CIF-004 — Awareness Radius Suppression
• FM-CIF-006 — Ethical Externalization
• FM-CIF-007 — Interface Goodhart Collapse
• FM-CIF-008 — Containment Backfire
• FM-CIF-009 — Restoration Window Closure
• FM-CIF-010 — Species-Level Σ Violation

Related Security / Justice / Interface modes include:

• FM-SEC-004 — Consent Theater / Invalid Authorization
• FM-SEC-010 — Emergency Normalization
• FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
• FM-JC-006 — Emergency Normalization
• FM-JC-007 — Manufactured Consent
• FM-JC-008 — Post-Signing Environmental Incoherence
• FM-JC-011 — Locked-In Renegotiation Failure

Aliases preserved from source material:

• Legitimacy Drift Across Scales
• Cross-Scale Legitimacy Drift
• Scale-Transferred Legitimacy
• Legitimacy Scale Error
• Authority Drift Across Scales
• Consent Scale Drift
• Representation Scale Drift
• Cross-Scale Mandate Inflation
• Scale-Jumped Legitimacy
• Civilization Legitimacy Drift

15. Minimal Entry Version

Definition: Legitimacy drift across scales occurs when authority, consent, representation, responsibility, boundary rights, or moral standing is treated as valid at one scale and then extended to another scale without renewed audit, consent, capacity, or coherence validation.

Signature:

authority scope↑
scale fit↓
consent revalidation↓
representation gap↑
Au↓
repair capacity lag↑
H↑
legitimacy debt↑

Restoration direction:

• map original legitimacy
• map the expanded action
• identify the drift point
• restore affected-scope mapping
• revalidate consent
• restore representation
• scale auditability
• scale repair capacity
• reduce mandate inflation
• validate across time

16. Machine-Readable Summary

failure_mode:
  id: "FM-CIF-005"
  name: "Legitimacy Drift Across Scales"
  family: "Civilization Interface"
  production_treatment: "Standalone Entry"
  primary_failure: "Authority, consent, representation, responsibility, or boundary rights are extended to a new scale without sufficient renewed consent, auditability, affected-scope mapping, or repair capacity."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-CIF-005"
  scope_note: "Conceptual and systems-oriented; does not make empirical claims about specific civilizations, institutions, nations, platforms, species, intelligences, contact events, or historical cases."
  aliases:
    - "Legitimacy Drift Across Scales"
    - "Cross-Scale Legitimacy Drift"
    - "Scale-Transferred Legitimacy"
    - "Legitimacy Scale Error"
    - "Authority Drift Across Scales"
    - "Consent Scale Drift"
    - "Representation Scale Drift"
    - "Cross-Scale Mandate Inflation"
    - "Scale-Jumped Legitimacy"
    - "Civilization Legitimacy Drift"
  signature:
    - "authority scope↑"
    - "scale fit↓"
    - "consent revalidation↓"
    - "representation gap↑"
    - "Au↓"
    - "repair capacity lag↑"
    - "H↑"
    - "legitimacy debt↑"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
    manifestation:
      - "U2 — Configuration / Boundaries"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
  state_variables:
    - "Au"
    - "BΣ"
    - "Γ"
    - "Ψ"
    - "O"
    - "H"
    - "K"
    - "R"
    - "Τ"
    - "µᵢ"
  first_gate_failure: "Legitimacy Gate"
  restoration:
    - "Legitimacy Restoration"
    - "Scale Revalidation"
    - "Consent Restoration"
    - "Representation Repair"
    - "Affected-Scope Mapping"
    - "Auditability Restoration"
    - "Boundary Governance Restoration"
    - "Repair Capacity Rebuild"
    - "Time-Validated Restoration"