INV-056 — Supersession Is Sometimes the Coherent Repair

1. Definition

Some systems cannot be restored as-is.

Supersession is the coherent replacement, retirement, redesign, migration, or basin exit of a system, structure, process, regime, coupling, institution, pattern, role, interface, technology, or symbolic container when continued restoration attempts would preserve the very conditions that generate hidden debt.

A system may become non-restorable as-is when its coherence depends on:

suppressed auditability
invalid consent
boundary capture
hidden-debt export
non-repairable opacity
recurrence lock
coercive dependency
pseudo-coherent basin stability
irreversible legitimacy loss

In such cases, the coherent repair is not to patch the existing basin.

The coherent repair is to supersede it.

Therefore:

Supersession is sometimes the coherent repair.

Supersession does not mean reckless destruction.

It means transition to a higher-coherence structure when restoration-as-is would preserve incoherence.

2. Purpose

This invariant prevents UTS from assuming that every system should be restored in its current form.

Restoration is usually preferred when a system can repair debt, restore boundaries, preserve meaning, reduce recurrence, and remain coherent over time.

But some systems are built around patterns that cannot be repaired without replacing the structure itself.

The false assumption is:

Every system should be restored if enough repair is applied.

The UTS correction is:

Some systems can only be repaired by being superseded.

This matters because pseudo-coherent basins often defend themselves through repair language.

They may claim:

• reform
• modernization
• reconciliation
• optimization
• compliance
• safety improvement
• policy update
• symbolic renewal
• leadership change
• process improvement
• rebranding
• partial transparency

But if the underlying basin still depends on hidden debt, invalid consent, suppressed auditability, boundary capture, or non-repairable recurrence, then restoration language becomes basin preservation.

The purpose of this invariant is to distinguish:

repairing a system

from:

preserving the basin that produces the failure

3. Constraint Statement

Canonical Form

Supersession is sometimes the coherent repair.

Expanded Form

When a system, process, institution, technology, relationship, regime,
pattern, or symbolic structure depends on suppressed auditability, invalid
consent, non-restorable opacity, hidden-debt export, coercive dependency,
boundary capture, or recurrence lock, the coherent repair may be replacement,
migration, retirement, or basin supersession rather than restoration as-is.

Minimal Expression

Some systems cannot be restored as-is.

Restoration Form

Do not preserve a basin whose stability depends on hidden debt.

Governance Form

Institutions that cannot receive truth or repair affected nodes may require replacement, not patching.

Security Form

A compromised architecture may need rebuild, not incident closure.

AI Form

AI systems whose governance, memory, representation, or action pathways cannot be made auditable and repairable may require redesign or retirement.

Economy Form

An extraction model cannot be restored merely by improving its efficiency.

Biological Form

A recurrent burden pattern may require restructuring the load ecology, not suppressing symptoms within it.

CMS / Symbolic Form

A symbolic container that preserves inversion may need replacement, not ritual renewal.

4. Structural Logic

A pseudo-coherent basin can remain stable while exporting incoherence.

When a system’s stability depends on debt export, audit suppression, boundary capture, or coercive dependency, restoring the system “as-is” restores the failure generator.

The incoherent sequence:

system produces hidden debt
        ↓
failure becomes visible
        ↓
repair pressure appears
        ↓
system patches symptoms
        ↓
core basin remains unchanged
        ↓
debt production continues
        ↓
recurrence returns
        ↓
restoration becomes basin maintenance

The coherent sequence:

system produces recurring hidden debt
        ↓
causality and basin dependency are mapped
        ↓
non-restorable conditions are identified
        ↓
transition path is designed
        ↓
affected nodes are protected
        ↓
replacement / migration / retirement occurs
        ↓
higher-coherence attractor is stabilized
        ↓
old recurrence pathway is retired

Supersession is necessary when repair cannot change the system’s attractor.

A system may be non-restorable if:

the system cannot remain stable without suppressing truth
the system cannot function without invalid consent
the system cannot maintain legitimacy under audit
the system cannot reduce recurrence without losing its identity
the system cannot repair affected nodes without exposing its core dependency
the system cannot preserve boundaries without ceasing its current form

Core insight:

If repair requires preserving the failure basin, repair has inverted.

5. State-Vector Impact

Protected State Variables

O   — coherence
H   — hidden debt
Au  — auditability
BΣ  — boundary integrity
R   — restoration capacity
µᵢ  — meaning / agent integrity
K   — compatibility with higher-coherence structure

Primary Risk Variables

ι   — inversion when patching is mistaken for restoration
ε   — visible failures, crises, symptoms, incidents, conflicts, collapses
Φ   — continuity, stability, institutional survival, profit, compliance, or reform proxy

Healthy Supersession Pattern

recurrence mapped
basin dependency identified
non-restorable conditions acknowledged
transition path designed
affected nodes protected
higher-coherence attractor seeded
old basin retired
H↓
O↑

Violation Pattern

system patched as-is
basin dependency unchanged
Au suppressed
BΣ unrepaired
R misdirected
H continues
recurrence returns
ι↑
O↓

Basin Preservation Inversion

Φ continuity↑
reform language↑
core debt pathway unchanged
H↑
ι↑
O↓

The key inversion:

system survival is mistaken for restoration

Supersession Validation Signs

Valid supersession should show:

H↓
recurrence↓
Au↑
BΣ↑
affected-node burden↓
R no longer captured by old basin
µᵢ restored through clearer function
K improved with new structure
O↑ over time

6. U-Layer Localization

Primary Layer

U2 — Configuration / Boundaries

Supersession often requires replacing the configuration that produces boundary capture, invalid consent, dependency lock, or non-repairable coupling.

Memory Layer

U7 — Memory / Recurrence

A system requires supersession when recurrence is structurally embedded and cannot be reduced by ordinary repair.

Coherence Field Layer

U6 — Coherence Field

Meaning, legitimacy, trust, and field coherence may no longer be restorable inside the existing form.

Resource Layer

U1 — Power / Budgets

Supersession requires transition resources: time, capacity, migration support, redundancy, affected-node protection, and restoration funding.

Execution Layer

U3 — Execution

Supersession occurs through concrete replacement, retirement, migration, redesign, decommissioning, or re-platforming.

Classification Layer

U4 — Classification / Metrics

Systems often misclassify continuity, reform, patching, or survival as restoration.

Coordination Layer

U5 — Coordination / Time

Supersession must be sequenced. Abrupt collapse can create more debt; controlled transition preserves coherence.

Environment Layer

U8 — Environment / Forcing

External forcing may either delay supersession through continuity pressure or trigger chaotic replacement before transition capacity exists.

Common Failure Pattern

U7 recurrence persists
        ↓
U4 reform labels applied
        ↓
U3 patches executed
        ↓
U2 basin configuration unchanged
        ↓
U6 legitimacy continues declining
        ↓
H accumulates
        ↓
supersession becomes unavoidable but harder

Common Misdiagnosis

Supersession need is often misdiagnosed as:

• insufficient reform
• poor implementation
• isolated leadership failure
• communication problem
• lack of compliance
• lack of modernization
• need for better metrics
• need for stricter enforcement
• stakeholder resistance
• cultural problem
• temporary instability
• public relations problem

The deeper issue may be:

The system’s current structure is the recurrence pathway.

7. Violation Signatures

7.1 Reform Without Basin Change

The system changes procedures, language, leadership, or metrics while the debt-producing attractor remains intact.

reform↑
basin unchanged
H continues

7.2 Auditability Cannot Be Restored Without Threatening System Survival

The system depends on opacity.

Au↑ would destabilize system
therefore Au suppressed
H↑

This indicates non-restorable opacity.

7.3 Consent Cannot Be Made Valid Inside Current Structure

The system’s participation model depends on exit being nonviable, coercive dependency, hidden scope, or asymmetrical pressure.

consent form exists
real exit absent
BΣ invalid

The structure may need replacement.

7.4 Boundary Capture Is Structural

The system repeatedly violates boundaries because its normal operation requires boundary erosion.

BΣ repair attempted
operation re-erodes BΣ
recurrence↑

7.5 Restoration Capacity Is Captured by the System

Repair pathways are controlled by the same structure that produces the harm.

R formally present
R captured
affected-node repair fails

7.6 Recurrence Persists Across Multiple Repair Cycles

The system has undergone repeated reforms, patches, apologies, interventions, or corrections, but the pattern returns.

repair cycles↑
recurrence unchanged
supersession signal↑

7.7 Institutional Survival Replaces Coherence

The system’s main repair priority becomes preserving itself rather than reducing debt.

institutional survival Φ↑
H unchanged
O↓

7.8 AI Architecture Cannot Be Audited or Corrected Enough

An AI memory, tool, representation, or governance architecture cannot provide sufficient auditability, appeal, correction, or recurrence reduction without redesign.

AI capability↑
Au / R structurally insufficient
redesign required

7.9 Economic Model Requires Extraction

A business or economic model depends on underpaid labor, hidden externalities, debt capture, dependency lock, or ecological burden export.

profit model depends on H export
repair threatens model identity
supersession signal↑

7.10 Symbolic Container Preserves Inversion

A symbolic, spiritual, ideological, or archetypal structure preserves rank immunity, forced forgiveness, secrecy, or authority without repair.

symbolic continuity↑
µᵢ↓
Au↓
H↑

The symbol may need to be retired, reframed, or replaced.

8. Related Failure Modes

Primary related failure modes:

• Non-Restorable Basin
• Basin Preservation as Repair
• Reform Theater
• Patch-and-Repeat Cycle
• Non-Restorable Opacity
• Structural Consent Invalidity
• Boundary Capture
• Captured Restoration Capacity
• Recurrence Lock
• Institutional Self-Preservation
• Continuity-Over-Coherence Drift
• Pseudo-Restoration
• Restoration Bypass
• Legitimacy Collapse
• Auditability Suppression
• Hidden Debt Export
• Extraction Basin
• AI Architecture Non-Repairability
• Security Rebuild Requirement
• Economic Model Incoherence
• Symbolic Container Inversion
• Relationship Coupling Non-Restorability
• Biological Burden Ecology Lock
• Collapse Through Delayed Supersession

9. Related Restoration Arcs

Primary restoration arcs:

• Basin Supersession
• Controlled Transition
• Replacement Architecture
• Retirement / Decommissioning
• Migration Pathway
• Parallel Attractor Seeding
• Basin Shallowing
• Attractor Weakening
• Affected-Node Protection
• Exit Path Creation
• Boundary Reconstitution
• Auditability Restoration
• Hidden Debt Exposure
• Legitimacy Transfer
• Restoration Capacity Liberation
• System Redesign
• Security Rebuild
• AI Architecture Refactor
• Economic Model Transition
• Symbolic Container Replacement
• Temporal Validation of New Basin

Restoration Requirement

Supersession must be coherent, not merely destructive.

Minimal sequence:

Identify recurrence lock
        ↓
Map basin dependency
        ↓
Determine non-restorable conditions
        ↓
Protect affected nodes
        ↓
Create viable exit / migration path
        ↓
Seed higher-coherence replacement
        ↓
Reduce dependence on old basin
        ↓
Retire or constrain old structure
        ↓
Validate new basin over time

Supersession requires transition design.

A collapse is not automatically supersession.

10. Domain Expressions

AI

AI systems may require supersession when their architecture cannot provide sufficient:

auditability
memory correction
appeal
traceability
rollback
user representation integrity
tool permission control
recurrence reduction
boundary preservation

Examples:

• a memory system that cannot be inspected or corrected enough
• an agent architecture with unsafe permission coupling
• a moderation pipeline that cannot provide usable appeal
• a representation system that cannot maintain user agency
• a safety layer that creates non-auditable meaning compression

The coherent response may be:

redesign
deprecate feature
migrate users
rebuild permission model
replace memory architecture
retire unsafe coupling

Not every AI failure is fixed by another patch.

Sometimes the architecture is the failure pathway.

AI Governance

AI governance requires supersession when oversight mechanisms cannot govern the power they authorize.

A governance regime may need replacement if:

• appeal cannot scale
• auditability cannot be restored
• affected-node truth cannot enter
• model deployment outruns repair capacity structurally
• public cognition effects cannot be corrected
• safety claims require opacity
• representation systems cannot remain accountable to represented parties

A governance system that cannot repair public-impact AI must be redesigned, not merely rebranded.

Security

Security supersession occurs when a system is too compromised, opaque, obsolete, or structurally fragile to repair safely.

Examples:

legacy identity system cannot support least privilege
logging architecture cannot audit critical events
vendor dependency cannot be secured
network design repeatedly permits lateral movement
patching preserves a brittle architecture

Security response may require:

rebuild
rotate
replace
segment
decommission
migrate
re-architect

Incident closure is insufficient when the architecture remains the vulnerability.

Governance / JGL

Institutions may become non-restorable as-is when they cannot receive truth, repair affected nodes, preserve auditability, or reduce recurrence without losing their current identity.

Supersession may be required when:

appeal is structurally inaccessible
authority lacks responsibility trace
rank immunity is built in
truth pathways are captured
affected nodes cannot be heard
repair capacity is performative
legitimacy depends on suppressed audit

Coherent supersession may include:

• institutional redesign
• jurisdiction transfer
• replacement body
• independent review architecture
• parallel legitimacy pathway
• restorative transition process
• affected-node-centered redesign

Economy

Economic systems may require supersession when the business model or market structure depends on hidden debt.

Examples:

profit requires externality export
labor model requires depletion
platform model requires dependency lock
debt model requires asymmetry
supply chain requires unseen exploitation
growth requires ecological burden export

In such cases, incremental optimization can make the extraction basin more efficient.

Coherent repair may require:

model transition
ownership redesign
circulation repair
externality internalization
cooperative replacement
supply-chain redesign
debt restructuring

Extraction cannot be restored into coherence merely by becoming more efficient.

Biology / Medicine

Biological supersession appears when a recurrent burden ecology must be replaced, not suppressed.

Examples:

symptom treatment inside unchanged load ecology
diet changes without environment change
training plan inside unrecovered reserve
stress pattern unchanged despite interventions
medication suppresses signal while burden continues

The coherent repair may require restructuring the ecology:

load reduction
environment change
rhythm redesign
sleep architecture repair
workload transition
food ecology change
movement pattern replacement
recovery basin creation

The body may not need a stronger patch.

It may need a different attractor.

CMS / Meaning

Symbolic systems may require supersession when the container preserves inversion.

Examples:

ritual protects secrecy
doctrine suppresses audit
archetype grants rank immunity
community identity requires forced forgiveness
symbolic hierarchy blocks affected-node truth
sacred language preserves boundary violation

The coherent repair may be:

retire symbol
reframe archetype
replace ritual
create new covenant / container
restore auditability
rebuild meaning structure

A sacred container is not coherent if it preserves hidden debt.

Principles / Archetypes

Principles and archetypes may require supersession when their current expression has become structurally inverted.

Examples:

justice expression has become punishment-only
love expression has become fusion or obligation
sovereignty expression has become isolation or rank
truth expression has become weaponized disclosure
protection expression has become control
healing expression has become dependency creation

The principle itself may remain valid.

The expression may need replacement.

Supersession here means replacing the distorted embodiment with a higher-coherence form.

Relationships / Couplings

Some relationships, roles, contracts, collaborations, or couplings cannot be restored as-is.

Non-restorable signs include:

exit is not real
boundary repair repeatedly fails
trust cannot be time-validated
repair labor is structurally one-sided
recurrence persists
meaning collapses under contact
coupling depends on dependency capture

Coherent repair may be:

decoupling
role redesign
boundary reset
new contract
reduced access
parallel path
non-reintegration

Ending or restructuring a coupling can be restoration when continued coupling preserves hidden debt.

Project / Knowledge Systems

Knowledge systems may require supersession when a template, category, term, registry, or module structure repeatedly produces drift.

Examples:

a category creates recurring classification confusion
a term carries too much ambiguity
a template forces concepts into wrong slots
a module boundary hides cross-links
a registry structure causes duplication

Coherent repair may require:

rename
split
merge
deprecate
create crosswalk
replace template
move concept to law / scaling rule / gate

For UTS-style work:

deprecation can be canon-preserving.

Supersession protects coherence when older structure becomes a drift generator.

11. Scaling Behavior

As systems scale, supersession becomes harder but sometimes more necessary.

Scale increases:

dependency
sunk cost
identity attachment
institutional inertia
migration burden
affected-node count
continuity pressure
transition risk
political resistance
economic exposure

Therefore:

Scale↑ ⇒ supersession cost↑

But if the basin is non-restorable:

Scale↑ ⇒ delayed supersession debt↑↑

Scaling Risk Pattern

non-restorable basin persists
        ↓
scale increases
        ↓
dependency deepens
        ↓
transition becomes harder
        ↓
hidden debt compounds
        ↓
eventual collapse becomes more costly

Valid Scaling Pattern

non-restorable basin identified early
        ↓
replacement attractor seeded
        ↓
migration capacity built
        ↓
affected nodes protected
        ↓
old basin dependence reduced
        ↓
supersession occurs before collapse

Relation to Prior Restoration Invariants

INV-049:

Restoration is debt reduction, not closure.

INV-050:

Restoration requires truth, material repair, and prevention.

INV-051:

Restoration is sequenced.

INV-052:

Restoration requires capacity before demand.

INV-053:

No substitute may replace repair.

INV-054:

Reintegration must be conditional, auditable, and reversible.

INV-055:

Restoration capacity must scale with load.

INV-056 adds:

When the basin itself prevents these conditions, supersession is the repair.

Together:

restore when restoration is possible
supersede when restoration preserves the failure generator

12. Canonical Examples

Example 1 — Legacy Security Architecture

A company repeatedly patches a legacy access-control system, but it cannot support audit logs, least privilege, or reliable revocation.

patch cycles↑
Au insufficient
recurrence persists

The coherent repair is replacement architecture.

Example 2 — AI Memory System Without User Audit

An AI memory layer stores user-relevant meaning but cannot be reliably inspected, corrected, scoped, or rolled back.

memory utility↑
user Au↓
µᵢ risk↑

If auditability cannot be restored, the memory architecture must be redesigned or retired.

Example 3 — Institution With Captured Appeals

An institution offers appeals, but appeals are reviewed by the same structure that produced the original harm, with no meaningful independence.

formal appeal↑
real Au↓
R captured

The appeal system may require supersession.

Example 4 — Economic Model Based on Externalities

A business is profitable only because environmental, labor, or community costs are exported.

profit Φ↑
H exported
O↓

The model cannot be restored through efficiency alone.

It requires transition.

Example 5 — Biological Load Ecology

A person repeatedly treats symptoms while remaining in the same sleep, stress, workload, and environmental pattern that produces recurrence.

symptom treatment↑
burden ecology unchanged
recurrence↑

The repair is ecological restructuring.

Example 6 — Symbolic Container With Rank Immunity

A symbolic community claims humility and truth but grants certain roles audit immunity.

symbolic authority↑
Au↓
rank immunity↑

The container may need redesign or replacement.

Example 7 — UTS Category Drift

A construct repeatedly gets misclassified as an invariant when it functions better as a law or scaling rule.

classification recurrence↑
canon ambiguity↑

The coherent repair is category supersession: reassign, crosswalk, and deprecate the old placement.

13. Anti-Patterns

Anti-Pattern 1 — “Everything Can Be Reformed”

Some structures preserve the recurrence pathway.

Anti-Pattern 2 — “Continuity Is Always Coherent”

Continuity can preserve hidden debt.

Anti-Pattern 3 — “Patching Is Safer Than Replacing”

Patching can be riskier when it preserves an unrepairable basin.

Anti-Pattern 4 — “The System Is Too Important to Replace”

The more important the system, the more dangerous non-restorable incoherence becomes.

Anti-Pattern 5 — “Auditability Would Destroy Trust”

If auditability destroys trust, trust was already unstable.

Anti-Pattern 6 — “Consent Exists Because Participation Continues”

Participation under dependency lock is not valid consent.

Anti-Pattern 7 — “The Old System Is Stable”

Stability may be basin capture, not coherence.

Anti-Pattern 8 — “Replacement Is Destruction”

Coherent supersession is transition, not reckless destruction.

Anti-Pattern 9 — “We Can Restore Legitimacy With Better Messaging”

Messaging cannot repair a non-restorable legitimacy basin.

Anti-Pattern 10 — “The Symbol Must Be Preserved”

A symbol that preserves inversion may need retirement or replacement.

14. Related Laws

This invariant connects strongly to:

• Basin Supersession Law
• Pseudo-Coherent Basin Law
• Hidden Debt Return Law
• Recurrence Lock Law
• Non-Restorable Opacity Law
• Auditability Suppression Law
• Boundary Capture Law
• Invalid Consent Law
• Reform Theater Law
• Patch-and-Repeat Law
• Legitimacy Collapse Law
• Extraction Basin Law
• Scale Accelerates Dominant Trajectory Law
• Time Validates Law
• Restoration Capacity Scaling Law

15. Related Scaling Rules

Related scaling rules:

• Supersession Cost Increases With Dependency
• Delayed Supersession Compounds Hidden Debt
• Replacement Attractor Must Be Seeded Before Old Basin Collapse
• Migration Capacity Must Scale With Affected-Node Count
• Exit Pathways Must Precede Basin Retirement
• Auditability Must Be Restored or the System Must Be Replaced
• Boundary Capture Requires Structural Redesign
• Captured Restoration Capacity Requires Independent Pathway
• Non-Restorable Consent Requires Interface Replacement
• Patch Cycles Must Trigger Supersession Review
• Replacement Must Preserve Critical Functions During Transition
• Transition Support Must Scale With Dependency Depth

16. Related Gates

Relevant gates:

• Supersession Gate
• Non-Restorable Basin Gate
• Auditability Gate
• Consent Validity Gate
• Boundary Integrity Gate
• Recurrence Lock Gate
• Restoration Capacity Gate
• Captured Repair Gate
• Legitimacy Gate
• Exit Viability Gate
• Migration Capacity Gate
• Replacement Attractor Gate
• Controlled Transition Gate
• Security Rebuild Gate
• AI Architecture Redesign Gate
• Economic Model Transition Gate
• Symbolic Container Integrity Gate
• Relationship Re-Coupling Gate
• High Risk Gate
• Temporal Validation Gate

Gate Logic

A system enters supersession review when:

recurrence persists across multiple repair cycles

or when:

auditability cannot be restored without destabilizing system identity

or when:

valid consent cannot exist under current dependency structure

or when:

boundary repair fails because boundary erosion is operationally required

or when:

restoration capacity is captured by the debt-producing structure

or when:

system survival requires hidden debt export

Gate failure for restoration-as-is returns:

∅

Meaning:

restoration as-is is not admissible

The coherent response may be:

design supersession
seed replacement
protect affected nodes
create exit path
migrate functions
retire old basin
validate new structure over time

17. Related Operators

18. Machine-Readable Summary

id: UTS-INV-056
name: Supersession Is Sometimes the Coherent Repair
registry: UTS Invariants Registry
category: Restoration Invariant / Basin Invariant / Supersession Invariant / Structural Repair Invariant
status: Draft-Integrated
version: 0.1

definition: >
  Some systems cannot be restored as-is. Supersession is the coherent
  replacement, retirement, redesign, migration, or basin exit of a system,
  structure, process, regime, coupling, institution, pattern, role, interface,
  technology, or symbolic container when continued restoration attempts would
  preserve the very conditions that generate hidden debt.

constraint: >
  When a system, process, institution, technology, relationship, regime,
  pattern, or symbolic structure depends on suppressed auditability, invalid
  consent, non-restorable opacity, hidden-debt export, coercive dependency,
  boundary capture, or recurrence lock, the coherent repair may be replacement,
  migration, retirement, or basin supersession rather than restoration as-is.

canonical_form:
  - "Supersession is sometimes the coherent repair"
  - "Some systems cannot be restored as-is"
  - "Do not preserve a basin whose stability depends on hidden debt"
  - "If repair preserves the failure basin, repair has inverted"
  - "Restore when restoration is possible; supersede when restoration preserves the failure generator"
  - "Continuity is not coherence"

protects:
  - coherence_recovery
  - hidden_debt_reduction
  - auditability
  - consent_validity
  - boundary_integrity
  - recurrence_reduction
  - affected_node_protection
  - restoration_capacity
  - legitimacy
  - transition_integrity

state_vector_effects_when_preserved:
  O: "increases_or_stabilizes_through_higher_coherence_replacement"
  H: "decreases_as_old_basin_debt_pathway_is_retired"
  ε: "recurrence_failures_decline_after_transition"
  ι: "decreases_because_reform_theater_is_not_misclassified_as_restoration"
  Au: "increases_if_opacity_dependent_structure_is_replaced"
  µᵢ: "restored_through_clearer_function_and_meaning"
  BΣ: "restored_through_new_boundary_configuration"
  K: "improves_between_system_function_and_coherent_structure"
  R: "liberated_from_captured_or_failed_repair_pathway"
  Φ: "continuity_stability_survival_or_reform_not_misread_as_coherence"

state_vector_effects_when_violated:
  O: "decreases_as_non_restorable_basin_persists"
  H: "increases_through_repeated_patch_cycles_and_debt_export"
  ε: "recurs_as_same_failure_pattern_returns"
  ι: "increases_when_patching_or_reform_is_misread_as_restoration"
  Au: "decreases_or_remains_suppressed"
  µᵢ: "degrades_as_meaning_and_function_are_preserved_in_inverted_form"
  BΣ: "remains_damaged_if_boundary_capture_persists"
  K: "degrades_between_system_purpose_and_actual_structure"
  R: "captured_or_wasted_by_old_basin"
  Φ: "may_rise_through_continuity_reform_language_or_system_survival"

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

violation_signatures:
  - reform_without_basin_change
  - auditability_cannot_be_restored_without_threatening_system_survival
  - consent_cannot_be_made_valid_inside_current_structure
  - boundary_capture_is_structural
  - restoration_capacity_is_captured_by_the_system
  - recurrence_persists_across_multiple_repair_cycles
  - institutional_survival_replaces_coherence
  - ai_architecture_cannot_be_audited_or_corrected_enough
  - economic_model_requires_extraction
  - symbolic_container_preserves_inversion

related_failure_modes:
  - Non Restorable Basin
  - Basin Preservation As Repair
  - Reform Theater
  - Patch And Repeat Cycle
  - Non Restorable Opacity
  - Structural Consent Invalidity
  - Boundary Capture
  - Captured Restoration Capacity
  - Recurrence Lock
  - Institutional Self Preservation
  - Continuity Over Coherence Drift
  - Pseudo Restoration
  - Restoration Bypass
  - Legitimacy Collapse
  - Auditability Suppression
  - Hidden Debt Export
  - Extraction Basin
  - AI Architecture Non Repairability
  - Security Rebuild Requirement
  - Economic Model Incoherence
  - Symbolic Container Inversion
  - Relationship Coupling Non Restorability
  - Biological Burden Ecology Lock
  - Collapse Through Delayed Supersession

related_restoration_arcs:
  - Basin Supersession
  - Controlled Transition
  - Replacement Architecture
  - Retirement Decommissioning
  - Migration Pathway
  - Parallel Attractor Seeding
  - Basin Shallowing
  - Attractor Weakening
  - Affected Node Protection
  - Exit Path Creation
  - Boundary Reconstitution
  - Auditability Restoration
  - Hidden Debt Exposure
  - Legitimacy Transfer
  - Restoration Capacity Liberation
  - System Redesign
  - Security Rebuild
  - AI Architecture Refactor
  - Economic Model Transition
  - Symbolic Container Replacement
  - Temporal Validation Of New Basin

related_laws:
  - Basin Supersession Law
  - Pseudo Coherent Basin Law
  - Hidden Debt Return Law
  - Recurrence Lock Law
  - Non Restorable Opacity Law
  - Auditability Suppression Law
  - Boundary Capture Law
  - Invalid Consent Law
  - Reform Theater Law
  - Patch And Repeat Law
  - Legitimacy Collapse Law
  - Extraction Basin Law
  - Scale Accelerates Dominant Trajectory Law
  - Time Validates Law
  - Restoration Capacity Scaling Law

related_scaling_rules:
  - Supersession Cost Increases With Dependency
  - Delayed Supersession Compounds Hidden Debt
  - Replacement Attractor Must Be Seeded Before Old Basin Collapse
  - Migration Capacity Must Scale With Affected Node Count
  - Exit Pathways Must Precede Basin Retirement
  - Auditability Must Be Restored Or The System Must Be Replaced
  - Boundary Capture Requires Structural Redesign
  - Captured Restoration Capacity Requires Independent Pathway
  - Non Restorable Consent Requires Interface Replacement
  - Patch Cycles Must Trigger Supersession Review
  - Replacement Must Preserve Critical Functions During Transition
  - Transition Support Must Scale With Dependency Depth

related_gates:
  - Supersession Gate
  - Non Restorable Basin Gate
  - Auditability Gate
  - Consent Validity Gate
  - Boundary Integrity Gate
  - Recurrence Lock Gate
  - Restoration Capacity Gate
  - Captured Repair Gate
  - Legitimacy Gate
  - Exit Viability Gate
  - Migration Capacity Gate
  - Replacement Attractor Gate
  - Controlled Transition Gate
  - Security Rebuild Gate
  - AI Architecture Redesign Gate
  - Economic Model Transition Gate
  - Symbolic Container Integrity Gate
  - Relationship Re Coupling Gate
  - High Risk Gate
  - Temporal Validation Gate

19. Compact Canon Statement

UTS-INV-056 states that supersession is sometimes the coherent repair. Some systems cannot be restored as-is because their stability depends on suppressed auditability, invalid consent, boundary capture, hidden-debt export, non-restorable opacity, captured repair capacity, or recurrence lock. In such cases, continued patching preserves the failure basin. Coherent repair may require replacement, redesign, migration, retirement, or controlled transition into a higher-coherence structure. Continuity is not coherence.

20. Short Reference Version

UTS-INV-056 — Supersession Is Sometimes the Coherent Repair

Some systems cannot be restored as-is.

Supersession is coherent when the existing system depends on:

suppressed auditability
invalid consent
boundary capture
hidden-debt export
non-restorable opacity
captured repair capacity
recurrence lock
coercive dependency
pseudo-coherent basin stability

Core rule:

Do not preserve a basin whose stability depends on hidden debt.

If repair preserves the failure generator,
repair has inverted.

The coherent path may be:

map recurrence
identify basin dependency
protect affected nodes
create exit / migration path
seed higher-coherence replacement
retire or constrain old structure
validate the new basin over time

Continuity is not coherence.
Replacement can be restoration when restoration-as-is preserves the debt source.