1. Short Definition

Supersession Threshold occurs when a system’s core structure depends on suppressed auditability, invalid consent, hidden debt export, non-restorable obfuscation, or recurring failure so deeply that patching preserves the problem.

Some systems cannot be restored as-is.

They must be superseded.

2. Canonical Pattern

suppressed auditability + invalid consent + non-restorable obfuscation ⇒ supersession required

Expanded:

core structure depends on incoherent conditions
+
patches preserve those conditions
⇒ restoration-as-is fails
⇒ higher-coherence replacement required

Plain form:

A system that depends on its own incoherence cannot be repaired by preserving its structure.

3. Mechanic Description

SCALE-062 defines the point where restoration shifts from repair to supersession.

Most systems should not be discarded prematurely. Many can be repaired through auditability restoration, boundary repair, hidden debt reduction, slack regeneration, role restructuring, and recurrence validation.

But some systems become non-restorable in their current form.

This happens when the system’s core operation depends on:

• hidden causality
• invalid consent
• suppressed auditability
• permanent opacity
• non-reversible extraction
• debt export
• coercive dependency
• irreparable legitimacy collapse
• recurring failure despite repair attempts
• inability to distinguish Φ from O
• capture of appeal or correction pathways
• boundary violation as a business or governance model
• restoration language used to preserve the basin

At that point, more patching may increase hidden debt.

Patches may become part of the pseudo-coherent basin.

Supersession does not mean reckless destruction.

It means forming a higher-coherence replacement attractor and transitioning away from the structure that cannot be made coherent.

Supersession should preserve dignity, agency, material continuity, and repair wherever possible.

4. UTS Variable Mapping

5. Diagnostic Questions

1. Can the system be repaired without preserving the problem?
2. Does the system depend on suppressed auditability?
3. Does it require invalid consent or coercive dependency?
4. Does it export hidden debt as part of its core operation?
5. Do patches reduce recurrence or preserve the basin?
6. Are appeal and correction pathways captured?
7. Is opacity necessary for the system to continue?
8. Does the system distinguish Φ from O?
9. Has legitimacy collapsed beyond internal repair?
10. Is a higher-coherence replacement attractor available or buildable?

6. Failure Signatures

1. Patch Preserves Incoherence

patch↑ while H_origin persists

Repairs improve appearance while preserving the source failure.

2. Suppressed Auditability Dependency

system viability depends on Au↓

The system can only continue if key causes remain hidden.

3. Invalid Consent Dependency

operation requires exit failure / coercive dependency / hidden scope

The system depends on invalid coupling.

4. Recurrence Despite Repair

repair attempts↑ while τ_m↑

Repeated repair does not reduce recurrence.

5. Restoration Capture

restoration language used to preserve basin geometry

Repair vocabulary becomes a defense mechanism.

7. Related Failure Modes

• non-restorable system
• failed patching
• restoration capture
• pseudo-restoration
• suppressed auditability dependency
• invalid consent dependency
• basin preservation
• recurring repair failure
• legitimacy collapse
• hidden debt export
• structural obfuscation

8. Related Diagnostics

9. Restoration Implications

If SCALE-062 is active, restoration shifts from patching to supersession design.

Required actions:

1. Stop assuming the system can be repaired as-is.
2. Identify structural dependencies on incoherence.
3. Preserve evidence and auditability.
4. Protect affected nodes.
5. Build or identify higher-coherence replacement attractor.
6. Design transition pathways.
7. Preserve dignity, agency, and material continuity where possible.
8. Reduce dependency on the old system.
9. Prevent restoration language from becoming basin defense.
10. Validate the replacement through stress, recurrence, and hidden debt reduction.

Core restoration rule:

When repair preserves the failure, supersession becomes restoration.

10. Compact Registry Entry

id: SCALE-062
name: "Supersession Threshold"
family: "SCALE-K — Transition and Restoration Scaling Mechanics"
type: "replacement-non-restorable-system-threshold"
status: "draft-ready"
short_definition: "A system reaches supersession threshold when its core structure depends on suppressed auditability, invalid consent, hidden debt export, non-restorable obfuscation, or recurring failure so deeply that patching preserves the problem."
canonical_pattern: "suppressed auditability + invalid consent + non-restorable obfuscation ⇒ supersession required"
failure_signature: "core structure depends on incoherent conditions + patches preserve those conditions ⇒ restoration-as-is fails + higher-coherence replacement required"
primary_variables:
  - O
  - H
  - ε
  - ι
  - Au
  - µᵢ
  - BΣ
  - K
  - R
  - Φ
primary_diagnostics:
  - repair_attempt_count
  - τ_m
  - H_origin
  - Au_structural
  - consent_validity
  - exit_viability
  - appeal_capture_index
  - legitimacy_baseline
  - replacement_viability
  - transition_risk
related_failure_modes:
  - non_restorable_system
  - failed_patching
  - restoration_capture
  - pseudo_restoration
  - suppressed_auditability_dependency
  - invalid_consent_dependency
  - basin_preservation
  - recurring_repair_failure
  - legitimacy_collapse
restoration_implication: "Shift from patching to supersession design: protect affected nodes, preserve auditability, build a higher-coherence replacement, design transition pathways, and validate replacement through recurrence and debt reduction."

11. One-Line Canon

When repairing the system preserves the failure, replacing the attractor becomes the repair.