Archive registry entry

LAW-076 — Supersession Threshold Law

Archive registry entry

LAW-076 — Supersession Threshold Law

Systems dependent on suppressed auditability, invalid consent, non-restorable obfuscation, or recurring pseudo-restoration may require replacement rather than patching.

draftid: LAW-076version: 1.0.0updated: 2026-06-16

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

171 registry entries are available.

Cross-links

Curating

Related concepts are being connected conservatively for accuracy.

Jump Through This Page

LAW-075 — Capacity Before Demand Law

Registry

LAW-077 — Pseudo-Coherent Basin Law

0. Plain Statement

Some systems cannot be restored as-is. They must be superseded.

Plain-language version:

A system may reach a point where patching no longer restores coherence. If it depends on suppressed auditability, invalid consent, non-restorable obfuscation, recurring pseudo-restoration, or structural inability to reduce hidden debt, it may require replacement, redesign, or supersession rather than another repair attempt.

1. Formal Definition

The Supersession Threshold Law states that systems dependent on non-restorable incoherence cannot be repaired merely by patching their visible failures.

Some systems contain failures that are not peripheral. The failure is not a bug at the edge of the system. It is part of how the system operates, protects itself, generates value, maintains authority, preserves stability, or prevents audit.

A system approaches the supersession threshold when it repeatedly requires one or more of the following to continue:

suppressed auditability;
invalid or coerced consent;
non-restorable obfuscation;
recurring pseudo-restoration;
quiet minimization;
unrepaired boundary violations;
hidden debt export;
repair pathways that harm damaged nodes;
symbolic closure without material repair;
governance claims that cannot survive audit;
scaling before restoration;
restoration processes captured by the failure basin itself.

At that point, additional patching may only reinforce the basin. Restoration may require creating a higher-coherence replacement path rather than trying to preserve the current form.

Supersession is not destruction for its own sake. It is replacement of a non-restorable operating geometry with a more coherent attractor.

2. Canonical Form

Core form:

textScroll

non-restorable dependency ⇒ supersession required

Expanded form:

textScroll

(Au suppressed ∨ consent invalid ∨ obfuscation non-restorable ∨ pseudo-restoration recurring)
∧ H not reducible as-is
⇒ patching fails; supersession threshold reached

Patch-trap form:

textScroll

patching system that preserves failure geometry ⇒ H↑ + ι↑ + recurrence↑

Supersession-valid form:

textScroll

higher-coherence attractor viable + transition capacity sufficient ⇒ supersession admissible

Related variables:

textScroll

O, H, ε, ι, Au, R, R_eff, BΣ, K, σ, µᵢ, Φ, Λ, ⊗, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, FI, L

Where:

TableScroll

Variable	Meaning in this law
`Au`	Auditability; if structurally suppressed, repair cannot be verified
`H`	Hidden debt; if not reducible in the current form, restoration fails
`ι / Ξ`	Inversion; rises when patching preserves the failure geometry
`BΣ`	Boundary integrity; persistent boundary failure may require redesign
`R / R_eff`	Restoration capacity; if insufficient by design, the system may be non-restorable
`O`	Coherence; should improve under real restoration, but declines under patch traps
`L`	Legitimacy; collapses when the system cannot survive audit or repair
`K / σ`	Slack / sovereignty; often depleted or structurally denied in non-restorable systems
`FI`	Feedback integrity; if corrupted by design, repair claims cannot be trusted
`µᵢ`	Meaning / agent integrity degraded when system narratives contradict system effects
`Φ`	Visible success proxy; may remain high while the system becomes non-restorable
`Γ`	Classifies whether the system is patchable, restorable, transitional, or supersession-bound
`Π`	Patches, controls, restrictions, enforcement, or containment; may become debt-generating
`ℛ`	Restoration action; may need to shift from patching to replacement design
`Θ`	Humility / uncertainty required to avoid preserving a system merely because it exists
`Σ`	Scope of what must be repaired, replaced, decoupled, or carried forward
`Ψ`	Field and affected-node feedback reveals whether patching is working or failing
`Τ`	Time validation reveals recurring pseudo-restoration and patch failure
`Λ`	Compatibility; current system may be incompatible with coherent restoration
`⊗`	Coupling may need reduction before supersession transition can occur

3. Core Mechanism

The law unfolds when repair attempts repeatedly preserve the geometry that produces failure.

Patch-trap pathway

textScroll

system failure appears
→ patch is applied
→ visible pressure decreases
→ core failure geometry remains
→ auditability / consent / boundary / debt failure persists
→ recurrence returns
→ another patch is applied
→ H↑ + ι↑
→ supersession threshold approaches

Supersession pathway

textScroll

recurring patch failure detected
→ restorability is assessed
→ non-restorable dependencies are identified
→ unsafe coupling is reduced
→ higher-coherence attractor is designed
→ transition path is seeded
→ old basin is phased out
→ new system is time-validated

The core mechanism is:

textScroll

when the system depends on the condition restoration must remove, patching cannot restore it

Detailed mechanism:

A system develops recurring failure.

The same harms, debts, legitimacy failures, audit failures, boundary failures, or pseudo-restoration patterns return after repair.

Patches reduce visible pressure.

The system updates policy, adds controls, modifies language, settles quietly, improves dashboards, increases enforcement, or makes symbolic repairs.

The failure geometry remains intact.

The system still depends on opacity, coerced consent, debt export, weak feedback, boundary asymmetry, or pseudo-restoration to function.

Each patch adds complexity and debt.

The system becomes harder to audit, more brittle, more legitimacy-sensitive, and more dependent on further patching.

Restoration capacity becomes trapped.

Repair resources are consumed maintaining the old basin instead of creating a coherent alternative.

Supersession becomes the coherent restoration path.

The task shifts from patching the existing system to building and transitioning toward a higher-coherence attractor.

4. When This Law Applies

This law applies when a system repeatedly fails restoration despite repair attempts, or when its operating model depends on conditions that restoration would need to remove.

It is especially important when:

auditability cannot be restored without threatening the system’s operation;
consent cannot become valid within the current structure;
obfuscation is necessary for the system to maintain legitimacy or profit;
pseudo-restoration recurs after each repair attempt;
quiet minimization is built into the repair pathway;
hidden debt cannot be reduced without redesigning the system;
boundary violations are structurally repeated;
harmed nodes must carry impossible repair burdens;
scaling depends on unrepaired debt;
governance claims cannot survive symmetrical audit;
patches increase complexity faster than coherence;
compliance improves while legitimacy declines;
each repair cycle produces the same failure pattern;
restoration capacity is captured maintaining the old basin.

The law applies strongly when:

textScroll

patches preserve the failure geometry they claim to repair

or when:

textScroll

the system depends on suppressed auditability, invalid consent, or recurring pseudo-restoration

Typical domains:

TableScroll

Domain	Supersession Threshold Expression
AI systems	AI systems dependent on suppressed auditability, opaque representation, invalid consent, or non-correctable appeal failure may require redesign or replacement.
Security	Security systems built on unobservable trust, permanent exceptions, or irreparable boundary assumptions may require architecture replacement.
Institutions	Institutions that preserve legitimacy through quiet minimization, asymmetric consequence, or pseudo-restoration may require structural redesign.
Medicine / biology	A degraded chronic basin may require a new adaptive regime rather than repeated symptom patches.
Economy	Economic systems dependent on coercive contracts, forced profit, exit traps, or hidden debt export may require attractor redesign.
Governance	Governance systems that cannot restore auditability, consequence, repair, and prevention may require supersession.
Culture	Cultural basins that normalize harm and convert repair into suppression may need higher-order attractor formation.
Restoration	When repair as-is preserves failure, restoration becomes supersession.

5. When This Law Does Not Apply

This law should not be used to abandon repair too early.

Many systems are restorable. A system may need better sequencing, deeper origin-layer repair, more capacity, more auditability, boundary repair, or time validation before supersession is justified.

Supersession should not be used as a bypass for difficult repair, accountability, or continuity responsibilities.

False-positive cases:

TableScroll

Case	Why it is not yet supersession
A system has failed once but has not been given origin-layer repair	Repair depth has not been tested
Repair capacity was insufficient but can be rebuilt	LAW-066 applies before supersession
Auditability is weak but restorable	Auditability restoration may be enough
Consent structures are damaged but can be redesigned within the system	Boundary / contract repair may work
Pseudo-restoration occurred once but is not structurally required	Correcting the restoration pathway may suffice
Temporary containment is mistaken for permanent failure	More temporal proof is needed

Important distinction:

Supersession is not the first repair move. It becomes necessary when the current form cannot reduce debt, restore auditability, validate consent, or prevent recurring pseudo-restoration.

6. Diagnostic Signature

Canonical diagnostic:

textScroll

non-restorable dependency ⇒ supersession required

Warning signature:

textScroll

patch cycles repeat
Au remains suppressed
consent remains invalid
H does not decrease
pseudo-restoration recurs
BΣ remains unstable
L declines
⇒ supersession threshold approaching

Common indicators:

TableScroll

Diagnostic	Expected movement	Interpretation
`Au`	persistently ↓ / suppressed	Repair cannot be verified
`H`	unchanged / ↑	Hidden debt cannot be reduced in current form
`ι / Ξ`	↑	Patching increasingly protects the failure pattern
`BΣ`	unstable / repeatedly failing	Boundaries cannot hold under the existing design
`R_eff`	structurally insufficient	Restoration capacity cannot be built inside current geometry
`FI`	degraded by design	Feedback cannot correct the system
`recurrence`	persistent / ↑	The same failure returns after repair
`L`	↓	Legitimacy decays as patch failure becomes visible
`O`	↓ / brittle	Coherence declines despite local patches
`K / σ`	↓	Slack and sovereignty are consumed maintaining the old basin
`µᵢ`	↓	Meaning integrity decays as claims diverge from effects
`Φ`	misleading / ↑	Visible success may persist while restorability declines
`Τ`	failed proof	Repair does not hold over time

Additional diagnostics:

TableScroll

Diagnostic	Use
Supersession Threshold	Tests whether patching has become non-restorative
Restorability Assessment	Determines whether current form can still reduce debt
Effective Auditability	Tests whether repair can be verified
Consent Validity	Tests whether participation or contract can become valid
Obfuscation Density	Detects whether opacity is structurally required
Pseudo-Restoration Recurrence	Detects repeated false repair cycles
Hidden Debt	Tracks whether debt can be reduced as-is
Inversion	Detects repair language preserving failure geometry
Legitimacy Baseline	Measures trust and authority decay
Temporal Proof	Tests whether patches hold or fail repeatedly

7. Failure Pattern

If ignored, this law produces patch traps and eventual collapse.

General failure pathway:

textScroll

non-restorable dependency exists
→ patch is applied
→ visible pressure decreases
→ failure geometry remains
→ H and ι rise
→ recurrence returns
→ patch complexity increases
→ Au decreases
→ legitimacy decays
→ collapse or forced supersession

Common failure modes:

Non-Restorable System — the current form cannot reduce debt or restore auditability.
Patch Trap — each repair preserves or deepens the failure geometry.
Recurring Pseudo-Restoration — false repair cycles repeat.
Suppressed Auditability Dependency — the system requires opacity to function.
Invalid Consent Dependency — participation depends on coerced, uninformed, or non-exitable consent.
Obfuscation Lock — the system cannot become legible without destabilizing itself.
Wrong-Solution Basin — repair attempts strengthen the basin that creates failure.
Restoration Capture — repair processes are captured by the system they should correct.
Patch-Induced Debt — patches add complexity, burden, or hidden debt.
Legitimacy Collapse — trust fails when patching no longer convinces the field.
Hidden Debt Persistence — debt cannot be cleared within the current form.
Boundary Failure Persistence — boundaries repeatedly fail under the existing design.
Delayed Collapse — the system appears functional until accumulated patch debt returns.

Compact failure signature:

textScroll

patching preserves failure geometry ⇒ H↑ + ι↑ + recurrence↑

8. Restoration Implications

Restoration may require replacement, redesign, or higher-order attractor formation.

The first supersession question is not:

textScroll

How do we patch this again?

The first supersession question is:

textScroll

Can this system reduce hidden debt, restore auditability, validate consent, and prevent recurrence in its current form?

Restoration priorities:

Assess restorability honestly.
Identify non-restorable dependencies.
Stop scaling the unrepaired system.
Reduce unsafe coupling where possible.
Preserve what is coherent and portable.
Seed a higher-coherence attractor.
Design transition paths that do not strand dependent nodes.
Maintain auditability through transition.
Retire or phase out the non-restorable geometry.
Time-validate the replacement system.

Relevant restoration arcs:

TableScroll

Restoration Arc	Why it applies
Supersession Assessment	Determines whether the system is still restorable
Controlled Decoupling	Reduces unsafe dependence on the failing system
Basin Supersession	Replaces the old attractor rather than patching it
Higher-Order Attractor Formation	Creates a viable alternative geometry
Auditability Restoration	Ensures transition remains visible and accountable
Consent Restoration	Repairs participation, exit, and scope conditions
Boundary Reconstitution	Prevents old boundary failures from entering the new form
Hidden Debt Reduction	Clears or carries debt transparently through transition
Transition Stabilization	Protects dependent nodes during replacement
Parallel Attractor Seeding	Allows the new system to become viable before full cutover
Temporal Validation	Proves the replacement holds over time
Closure Stack Completion	Prevents old system closure from becoming quiet minimization

Minimal restoration sequence:

textScroll

assess restorability
→ identify non-restorable dependencies
→ stop scale / reduce unsafe coupling
→ preserve coherent components
→ seed higher-coherence attractor
→ transition with audit / consent / boundary repair
→ time-validate replacement

Temporal validation requirement:

textScroll

old failure recurrence↓
H not transferred invisibly
Au↑
consent valid
BΣ stable or rising
R_eff sufficient
dependent-node burden↓
L stable or rising
O stable or rising
replacement does not reproduce old failure geometry

9. Design Rule

Do not keep patching a system whose operating geometry requires the failure that restoration must remove.

Operational design requirements:

Track repeated patch cycles.
Test whether hidden debt decreases after each repair.
Test whether auditability can be restored.
Test whether consent can become structurally valid.
Test whether obfuscation is removable.
Test whether pseudo-restoration recurs.
Stop scaling systems that fail restorability assessment.
Preserve coherent components before replacement.
Design transition pathways before collapse.
Seed viable alternatives before forced cutover.
Maintain repair obligations during supersession.
Validate the replacement over time.

Avoid:

patching as ritual;
preserving the system merely because it exists;
scaling non-restorable systems;
treating compliance complexity as repair;
treating opacity as necessary legitimacy;
treating coerced consent as acceptance;
treating recurring pseudo-restoration as progress;
destroying without transition;
replacing without carrying repair obligations;
abandoning dependent nodes;
hiding old debt inside the new system;
reproducing the same basin under new language.

10. Cross-Scale Expressions

TableScroll

Scale / Layer	Expression of the Law
U0 — Substrate	Hardware, biological, infrastructural, or physical systems may need replacement when substrate damage is non-restorable.
U1 — Energy / capacity	Systems that cannot sustain restoration capacity may need redesign around lower load or better circulation.
U2 — Boundary / interface	Persistent consent, access, contract, or membrane failure may require new boundary architecture.
U3 — Process / execution	Processes that require impossible burden or recurring exception patches may need replacement.
U4 — Classification / claim	Claims of repair become incoherent when the system cannot classify its own failure truthfully.
U5 — Time / delay	Repeated failure across time reveals the supersession threshold.
U6 — Field effect	Affected-node outcomes reveal when patching no longer restores coherence.
U7 — Recurrence / memory	Recurring pseudo-restoration shows the failure basin remains encoded.
U8 — Environment / forcing	External pressures may make the current form non-restorable unless environment or system geometry changes.

11. Examples

Example A — AI System With Non-Patchable Audit Failure

Scenario:

An AI platform repeatedly harms users through opaque classification, provides appeals that cannot explain decisions, patches output behavior, but cannot expose the causal path without undermining the system’s claims.

Law expression:

textScroll

Au structurally suppressed + pseudo-restoration recurring ⇒ supersession threshold

Interpretation:

More policy patches may not restore coherence. The system may require redesign around auditability, representation scope, appeal repair, and user-controllable boundaries.

Example B — Institution Dependent on Quiet Minimization

Scenario:

An institution repeatedly handles harm through private settlements, internal reviews, symbolic apologies, and narrative management while boundary failures recur.

Law expression:

textScroll

quiet minimization dependency + recurrence↑ ⇒ patching fails

Interpretation:

The repair process is part of the failure geometry. Supersession may require new accountability structures, independent audit, and boundary redesign.

Example C — Economic Contract Model

Scenario:

A business model depends on exit-cost traps, opaque terms, survival coercion, and burden transfer. Each reform improves wording but preserves the economic state-space.

Law expression:

textScroll

invalid consent dependency + H not reducible as-is ⇒ economic supersession

Interpretation:

The issue is not a bad clause. It is the contract geometry. Restoration may require replacing the model.

Example D — Security Architecture Patch Trap

Scenario:

A system repeatedly suffers breaches because its architecture assumes trust boundaries that cannot be reliably enforced. Each patch adds complexity but not real boundary integrity.

Law expression:

textScroll

BΣ repeatedly fails + patch complexity↑ ⇒ architecture replacement threshold

Interpretation:

At some point, redesigning the trust model is safer than adding another patch.

Example E — Biological Chronic Basin

Scenario:

A biological system repeatedly suppresses symptoms but returns to the same degraded basin because the load, circulation, barrier, energy, and recurrence conditions remain unchanged.

Law expression:

textScroll

symptom patching + chronic recurrence ⇒ basin redesign needed

Interpretation:

The current regime may not be restorable through symptom-level patches. Restoration may require a new adaptive basin.

Example F — Cultural Basin With Normalized Harm

Scenario:

A culture repeatedly acknowledges harm, adopts new language, and symbolically repairs itself, but the same normalized hierarchy, extraction, and boundary failures return.

Law expression:

textScroll

normalization shield + recurring pseudo-restoration ⇒ higher-order attractor required

Interpretation:

The existing basin protects itself through repair language. Restoration requires a higher-coherence cultural attractor.

12. Relationship to Nearby Laws

TableScroll

Related Law	Relationship
LAW-006 — Time Validation Law	Supersession threshold is revealed by repeated time-validation failure
LAW-007 — Ring-Down Truth Law	Non-restorable systems fail to improve damping
LAW-008 — Recurrence Validation Law	Persistent recurrence signals patch failure
LAW-010 — Hidden Debt Accumulation Law	Non-restorable systems keep accumulating debt
LAW-011 — Hidden Debt Return Law	Debt returns after each patch
LAW-013 — Auditability-Debt Law	Suppressed auditability is a major supersession trigger
LAW-015 — Suppressed Auditability Debt Law	Structural audit suppression creates non-restorability risk
LAW-016 — Inversion Formation Law	Patches become inversion when they preserve the failure
LAW-017 — Silent Extraction Law	Systems dependent on silent extraction may require replacement
LAW-021 — Coherence-Preserving Scaling Law	Non-restorable systems should not scale
LAW-030 — Slack Sovereignty Law	Systems that structurally consume slack may be non-restorable
LAW-031 — Observability Collapse Law	Observability collapse can make restoration impossible as-is
LAW-032 — Hidden Debt Migration Law	Debt migration may reveal non-restorable geometry
LAW-041 — Boundary Membrane Law	Persistent membrane failure may require boundary architecture replacement
LAW-042 — Consent Structurality Law	Invalid consent dependency is a supersession trigger
LAW-046 — Contract Validity Law	Contracts that cannot become valid may need replacement
LAW-047 — Controlled Decoupling Law	Decoupling may precede supersession
LAW-050 — Control-Restoration Separation Law	More control cannot restore a non-restorable system
LAW-052 — Stability Proof Law	Patch failures under perturbation reveal threshold
LAW-053 — Wrong-Solution Basin Law	Patching may preserve the wrong-solution basin
LAW-061 — Restoration Sequencing Law	Supersession follows failed or impossible restoration sequencing
LAW-062 — Restoration Is Not the Inverse of Failure Law	Supersession may be needed because reversal cannot restore the altered system
LAW-063 — Origin-Layer Repair Law	If origin-layer repair is impossible as-is, replacement may be required
LAW-064 — Restoration Debt Reduction Law	Failure to reduce debt indicates possible supersession
LAW-065 — Pseudo-Restoration Law	Recurring pseudo-restoration is a key threshold sign
LAW-066 — Restoration Capacity Sufficiency Law	Systems unable to build sufficient capacity may need redesign
LAW-067 — Temporal Proof Law	Repeated temporal proof failure supports supersession
LAW-068 — Boundary-First Restoration Law	Persistent boundary failure may require new membrane architecture
LAW-069 — Closure Stack Law	Systems unable to complete closure stack may be non-restorable
LAW-070 — Reintegration Membrane Law	Systems that cannot reintegrate safely may require redesign
LAW-071 — No Forced Forgiveness Law	Systems relying on forced forgiveness may be non-restorable as-is
LAW-072 — Quiet Minimization Debt Law	Repeated minimization may indicate supersession threshold
LAW-073 — Restoration Before Scaling Law	Non-restorable systems must not scale
LAW-074 — Restoration Before Exploration Law	Non-restorable systems should not explore beyond containment
LAW-075 — Capacity Before Demand Law	Systems depending on impossible demand may require replacement
LAW-081 — Higher-Order Attractor Law	Supersession requires a viable higher-order attractor
LAW-082 — Basin Supersession Law	LAW-082 gives the basin-level method for supersession
LAW-102 — Legitimacy Audit Law	Loss of audit-survivable legitimacy can trigger supersession
LAW-105 — Repair Before Enforcement Law	Enforcement cannot save a non-restorable system
LAW-126 — AI Non-Patchable Audit Law	AI-specific expression of non-patchable audit failure
LAW-150 — Economic Restoration Geometry Law	Economic supersession requires geometry redesign rather than destructive replacement alone

Aliases folded into this law:

Supersession Threshold Law
Replacement Before Patch Law
Non-Restorable System Law
Restoration Limit Law
Patch Failure Threshold Law
System Supersession Law
Repair-to-Replacement Threshold Law

Deduplication note:

This law should remain the root restoration-to-supersession threshold law. LAW-081 defines the need for a higher-order attractor, LAW-082 defines basin supersession mechanics, LAW-126 specializes the non-patchable audit pattern for AI systems, and LAW-150 specializes economic restoration geometry.

13. Operator Mapping

TableScroll

Operator	Role in this law
`Γ`	Classifies whether the system is patchable, restorable, transitional, or supersession-bound
`Π`	May patch, contain, throttle, or enforce, but cannot restore non-restorable geometry
`Ξ`	Captures inversion when patching preserves the failure pattern
`⊗`	Coupling may need reduction before transition or replacement
`ℛ`	Restoration may shift from patching to supersession design
`Τ`	Reveals repeated patch failure and validates replacement
`Θ`	Prevents overconfidence in preservation or destruction
`Σ`	Defines what must be repaired, carried forward, replaced, or retired
`Ψ`	Field and affected-node feedback reveals whether patching still works
`Λ`	Compatibility determines whether the current form can still support coherence

Coherent operator sequence:

textScroll

Γ(restorability assessment) → Θ(non-preservation caution) → Σ(scope preserve / replace / transition) → Π(stop scale + contain risk) → ⊗↓ where unsafe → seed higher-order attractor → ℛ(transition repair) → Ψ(validate field effects) → Τ(validate replacement O stable/↑)

Inverted operator sequence:

textScroll

recurrence visible → Π(patch) → Φ_stability↑ → Au remains suppressed → H remains → pseudo-restoration recurs → Ξ / ι↑ → L↓ → forced supersession / collapse

14. Machine-Readable Summary

yamlScroll

id: "LAW-076"
name: "Supersession Threshold Law"
type: "law"
status: "draft"
family:
  - "Restoration Laws"
summary: "Systems dependent on suppressed auditability, invalid consent, non-restorable obfuscation, or recurring pseudo-restoration may require replacement rather than patching."
canonical_statement: "Some systems cannot be restored as-is. They must be superseded."
core_form: "non-restorable dependency ⇒ supersession required"
expanded_form: "(Au suppressed ∨ consent invalid ∨ obfuscation non-restorable ∨ pseudo-restoration recurring) ∧ H not reducible as-is ⇒ patching fails; supersession threshold reached"
patch_trap_form: "patching system that preserves failure geometry ⇒ H↑ + ι↑ + recurrence↑"
supersession_valid_form: "higher-coherence attractor viable + transition capacity sufficient ⇒ supersession admissible"
variables:
  primary:
    - "Au"
    - "H"
    - "ι"
    - "Ξ"
    - "BΣ"
    - "R"
    - "R_eff"
    - "O"
    - "L"
    - "K"
    - "σ"
  secondary:
    - "ε"
    - "FI"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "ℛ"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
diagnostics:
  - "Supersession Threshold"
  - "Restorability Assessment"
  - "Effective Auditability"
  - "Consent Validity"
  - "Obfuscation Density"
  - "Pseudo-Restoration Recurrence"
  - "Hidden Debt"
  - "Inversion"
  - "Boundary Integrity"
  - "Restoration Capacity"
  - "Legitimacy Baseline"
  - "Coherence Trajectory"
  - "Temporal Proof"
failure_modes:
  - "Non-Restorable System"
  - "Patch Trap"
  - "Recurring Pseudo-Restoration"
  - "Suppressed Auditability Dependency"
  - "Invalid Consent Dependency"
  - "Obfuscation Lock"
  - "Wrong-Solution Basin"
  - "Restoration Capture"
  - "Patch-Induced Debt"
  - "Legitimacy Collapse"
  - "Hidden Debt Persistence"
  - "Boundary Failure Persistence"
  - "Delayed Collapse"
restoration_arcs:
  - "Supersession Assessment"
  - "Controlled Decoupling"
  - "Basin Supersession"
  - "Higher-Order Attractor Formation"
  - "Auditability Restoration"
  - "Consent Restoration"
  - "Boundary Reconstitution"
  - "Hidden Debt Reduction"
  - "Transition Stabilization"
  - "Parallel Attractor Seeding"
  - "Temporal Validation"
  - "Closure Stack Completion"
related_laws:
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-010"
  - "LAW-011"
  - "LAW-013"
  - "LAW-015"
  - "LAW-016"
  - "LAW-017"
  - "LAW-021"
  - "LAW-030"
  - "LAW-031"
  - "LAW-032"
  - "LAW-041"
  - "LAW-042"
  - "LAW-046"
  - "LAW-047"
  - "LAW-050"
  - "LAW-052"
  - "LAW-053"
  - "LAW-061"
  - "LAW-062"
  - "LAW-063"
  - "LAW-064"
  - "LAW-065"
  - "LAW-066"
  - "LAW-067"
  - "LAW-068"
  - "LAW-069"
  - "LAW-070"
  - "LAW-071"
  - "LAW-072"
  - "LAW-073"
  - "LAW-074"
  - "LAW-075"
  - "LAW-081"
  - "LAW-082"
  - "LAW-102"
  - "LAW-105"
  - "LAW-126"
  - "LAW-150"
related_invariants:
  - "INV-001"
  - "INV-004"
  - "INV-006"
  - "INV-078"
  - "INV-080"
operator_sequence:
  coherent:
    - "Γ restorability assessment"
    - "Θ non-preservation caution"
    - "Σ scope preserve / replace / transition"
    - "Π stop scale + contain risk"
    - "⊗↓ where unsafe"
    - "seed higher-order attractor"
    - "ℛ transition repair"
    - "Ψ validate field effects"
    - "Τ validate replacement O stable/↑"
  inverted:
    - "recurrence visible"
    - "Π patch"
    - "Φ_stability↑"
    - "Au remains suppressed"
    - "H remains"
    - "pseudo-restoration recurs"
    - "Ξ / ι↑"
    - "L↓"
    - "forced supersession / collapse"
aliases:
  - "Supersession Threshold Law"
  - "Replacement Before Patch Law"
  - "Non-Restorable System Law"
  - "Restoration Limit Law"
  - "Patch Failure Threshold Law"
  - "System Supersession Law"
  - "Repair-to-Replacement Threshold Law"
deduplication_note: "Root restoration-to-supersession threshold law. LAW-081 defines the need for a higher-order attractor, LAW-082 defines basin supersession mechanics, LAW-126 specializes the non-patchable audit pattern for AI systems, and LAW-150 specializes economic restoration geometry."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-076 — Supersession Threshold Law

Some systems cannot be restored as-is. They must be superseded.

Core form:

textScroll

non-restorable dependency ⇒ supersession required

Expanded form:

textScroll

(Au suppressed ∨ consent invalid ∨ obfuscation non-restorable ∨ pseudo-restoration recurring)
∧ H not reducible as-is
⇒ patching fails; supersession threshold reached

Plain meaning:

Patch-trap form:

textScroll

patching system that preserves failure geometry ⇒ H↑ + ι↑ + recurrence↑

Supersession-valid form:

textScroll

higher-coherence attractor viable + transition capacity sufficient ⇒ supersession admissible

Primary variables:

Au, H, ι, Ξ, BΣ, R, R_eff, O, L, K, σ, FI, µᵢ, Γ, Π, ℛ, Θ, Σ, Ψ, Τ, Λ, ⊗

Diagnostic signature:

Patch cycles repeat while auditability remains suppressed, consent remains invalid, hidden debt does not decrease, pseudo-restoration recurs, boundaries remain unstable, legitimacy declines, and restoration cannot be verified within the current form.

Failure risk:

Non-restorable system, patch trap, recurring pseudo-restoration, suppressed auditability dependency, invalid consent dependency, obfuscation lock, wrong-solution basin, restoration capture, patch-induced debt, legitimacy collapse, hidden debt persistence, boundary failure persistence, delayed collapse.

Restoration priority:

Assess restorability, identify non-restorable dependencies, stop scaling, reduce unsafe coupling, preserve coherent components, seed a higher-coherence attractor, transition with audit, consent, and boundary repair, and time-validate the replacement.

LAW-075 — Capacity Before Demand Law

Registry

LAW-077 — Pseudo-Coherent Basin Law