0. Plain Statement

Repair attempts amplify instability when restoration capacity is lower than load times gain.

Plain-language version:

A system cannot repair more than its restoration capacity can carry. When the load being processed, multiplied by system gain, exceeds available restoration capacity, the repair attempt itself can become destabilizing. In those cases, first moves may need to be load shedding, gain reduction, decoupling, boundary stabilization, slack regeneration, or capacity rebuilding before full repair is attempted.

1. Formal Definition

The Restoration Capacity Sufficiency Law states that a repair process becomes unstable when effective restoration capacity is lower than the load being processed multiplied by the gain of the system.

Restoration is not only a question of intent, correctness, or moral urgency. It is also a question of capacity.

A repair action can be directionally correct and still destabilize the system if the system lacks enough capacity to process the repair load. This is especially true when gain is high: emotional gain, institutional gain, technological gain, informational gain, social gain, market gain, adversarial gain, symbolic gain, or recurrence gain.

When restoration capacity is insufficient, repair can become:

• overwhelming;
• performative;
• extractive;
• delayed;
• fragmented;
• destabilizing;
• recurrence-amplifying;
• boundary-damaging;
• legitimacy-eroding.

Therefore, restoration design must evaluate capacity before loading the system with repair demands.

2. Canonical Form

Core form:

R_eff < Load × Gain ⇒ repair attempt amplifies instability

Capacity-sufficient form:

R_eff ≥ Load × Gain ⇒ repair may proceed coherently

Expanded form:

repair_attempt under R_eff deficit ⇒ σ↓ + 𝓓↓ + H↑ + recurrence↑ + O↓

Stabilization-first form:

R_eff < Load × Gain ⇒ first move = Load↓ and/or Gain↓ and/or R_eff↑

Related variables:

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

Where:

3. Core Mechanism

The law unfolds when repair demand exceeds the system’s ability to metabolize repair.

Overloaded restoration pathway

failure / harm creates repair load
→ system attempts repair under high gain
→ R_eff < Load × Gain
→ repair pathway overloads
→ damping worsens
→ boundaries degrade
→ hidden debt increases
→ recurrence amplifies

Capacity-matched restoration pathway

failure / harm creates repair load
→ load and gain are assessed
→ R_eff is measured
→ load is reduced and gain is damped if needed
→ restoration capacity is rebuilt
→ repair proceeds within capacity
→ recurrence decreases and O stabilizes

The core mechanism is:

repair becomes perturbation when the system lacks capacity to process it

Detailed mechanism:

1. A repair load becomes active.

The system must process harm, debt, conflict, breach, fatigue, biological stress, governance failure, AI error, security incident, or legitimacy damage.

1. Gain amplifies the repair burden.

The load becomes harder to carry because of speed, visibility, emotional charge, institutional pressure, technological leverage, adversarial forcing, recurrence density, or symbolic stakes.

1. Restoration capacity is insufficient.

The system lacks slack, repair staff, attention, time, trust, boundary stability, logistics, energy, auditability, or damping.

1. The repair attempt becomes a new perturbation.

The repair process adds demands faster than the system can absorb them.

1. Instability increases.

Hidden debt rises, recurrence strengthens, boundaries degrade, damping worsens, and coherence declines.

1. The system may misclassify the overload.

It may blame resistance, affected nodes, staff, patients, users, citizens, or downstream systems rather than recognizing capacity insufficiency.

4. When This Law Applies

This law applies when repair is attempted under insufficient restoration capacity.

It is especially important when:

• repair demand exceeds available staff, time, energy, trust, or logistics;
• a harmed node is asked to participate before it has capacity;
• a biological system is pushed into recovery demands while depleted;
• an institution launches reform without repair infrastructure;
• an AI provider scales safety processes without audit and appeal capacity;
• a security team handles incidents faster than it can learn from them;
• a governance system increases reporting without increasing repair capacity;
• a cultural system demands reconciliation without boundary or capacity repair;
• an economy demands productivity from depleted circulation;
• high-gain public attention accelerates repair faster than coherence can stabilize;
• urgency, shame, fear, market pressure, or symbolic stakes amplify repair load.

The law applies strongly when:

repair demand > available restoration capacity

or when:

R_eff is assumed rather than measured

Typical domains:

5. When This Law Does Not Apply

This law should not be used to avoid necessary repair.

Capacity insufficiency does not mean repair is optional. It means repair must be sequenced, scoped, stabilized, buffered, or supported so that the system can carry it.

The law does not justify delay as avoidance, suppression, minimization, or immunity. It does not permit systems to claim incapacity while refusing to build restoration capacity.

False-positive cases:

Important distinction:

Capacity limits do not cancel restoration obligations. They determine the safe sequence, scope, and support required for restoration to work.

6. Diagnostic Signature

Canonical diagnostic:

R_eff < Load × Gain ⇒ repair attempt amplifies instability

Warning signature:

repair demand↑
gain↑
R_eff insufficient
σ↓
𝓓↓
H↑
recurrence↑
O↓
⇒ restoration overload

Common indicators:

Additional diagnostics:

7. Failure Pattern

If ignored, this law produces repair-induced instability.

General failure pathway:

failure creates repair load
→ system attempts full repair immediately
→ gain amplifies burden
→ R_eff is insufficient
→ repair process overloads
→ boundaries degrade
→ hidden debt increases
→ recurrence intensifies
→ repair is misclassified as failure of cooperation

Common failure modes:

• Repair-Induced Instability — repair itself destabilizes the system.
• Restoration Capacity Exhaustion — repeated repair attempts drain remaining capacity.
• Overloaded Repair Pathway — repair load exceeds available bandwidth and logistics.
• Gain-Amplified Repair Failure — urgency, visibility, or emotional charge amplifies repair beyond capacity.
• Premature Repair Attempt — full restoration is attempted before stabilization.
• Feedback Without Slack — feedback becomes extractive because no capacity exists to process it.
• Reinjury Loop — repair participation reinjures harmed or depleted nodes.
• Pseudo-Restoration — insufficient capacity leads to visible but shallow repair.
• Delayed Collapse — overloaded repair appears functional before failing later.
• Burden Inversion — repair burden shifts onto the damaged node.
• Capacity-Demand Mismatch — the system demands capacities that no longer exist.
• Restoration Burnout — repair agents collapse under unresolved load.

Compact failure signature:

R_eff deficit + high Load × Gain ⇒ repair becomes perturbation

8. Restoration Implications

Restoration requires matching repair load to restoration capacity.

The first restoration question is not:

What repair should happen immediately?

The first restoration question is:

What repair can the system coherently carry now, and what capacity must be rebuilt first?

Restoration priorities:

1. Measure repair load.
2. Measure gain amplification.
3. Measure effective restoration capacity.
4. Reduce load where possible.
5. Reduce gain where possible.
6. Stabilize boundaries before deep repair.
7. Regenerate slack.
8. Rebuild restoration capacity.
9. Phase repair into capacity-matched sequences.
10. Validate that repair reduces recurrence instead of amplifying it.

Relevant restoration arcs:

Minimal restoration sequence:

assess Load × Gain
→ measure R_eff
→ if R_eff insufficient: Load↓ / Gain↓ / decouple / stabilize / rebuild R_eff
→ apply phased repair
→ validate recurrence↓ + 𝓓↑ + O stable/↑

Temporal validation requirement:

R_eff ≥ Load × Gain sustainably
H↓
BΣ stable or rising
K / σ↑
recurrence↓
𝓓↑
Au↑
FI intact
µᵢ stable
O stable or rising

9. Design Rule

Do not load a system with repair demands that exceed its effective restoration capacity.

Operational design requirements:

• Estimate repair load before repair begins.
• Estimate gain amplification.
• Measure actual restoration capacity, not declared capacity.
• Reduce load before full repair when necessary.
• Reduce gain before full repair when necessary.
• Decouple unsafe interactions before deep repair.
• Stabilize boundaries before recoupling.
• Regenerate slack before demanding participation.
• Phase repair into capacity-matched sequences.
• Increase restoration capacity before scaling repair scope.
• Monitor recurrence and ring-down during repair.
• Treat repair overload as a capacity signal, not proof of resistance or bad faith.

Avoid:

• demanding full repair from depleted systems;
• demanding harmed-node participation without capacity;
• treating urgency as capacity;
• treating moral correctness as logistical sufficiency;
• treating visibility as restoration capacity;
• escalating gain during fragile repair;
• forcing recoupling before boundary stabilization;
• increasing process burden without repair capacity;
• adding feedback channels without slack;
• scaling reform before restoration infrastructure exists;
• punishing overload as noncompliance.

10. Cross-Scale Expressions

11. Examples

Example A — Institutional Reform Overload

Scenario:

An institution launches a major reform after public failure. It adds reporting, meetings, documentation, committees, and messaging, but does not increase repair staff, harmed-node support, accountability logistics, or process capacity.

Law expression:

R_eff < reform_load × institutional_gain ⇒ reform amplifies instability

Interpretation:

The reform may be directionally correct, but without capacity it becomes burden. Staff burn out, affected nodes carry more load, feedback degrades, and hidden debt increases.

Example B — Biological Recovery Overload

Scenario:

A depleted biological system begins several interventions at once: intense exercise, restrictive diet, supplements, stimulation, schedule changes, and high cognitive demand.

Law expression:

R_eff_bio < intervention_load × gain ⇒ recovery attempt destabilizes

Interpretation:

The interventions may each be useful in isolation, but the stack exceeds recovery capacity. First moves may need to reduce load, restore energy, improve damping, and phase interventions.

Example C — AI Safety Appeals Overload

Scenario:

An AI platform introduces an appeal process after repeated moderation failures, but appeal volume, user stakes, model velocity, policy complexity, and public scrutiny exceed review capacity.

Law expression:

R_eff_review < appeal_load × platform_gain ⇒ safety repair fails

Interpretation:

The appeal pathway becomes another failure surface. Users experience delay, inconsistency, opacity, and legitimacy loss because restoration capacity is insufficient.

Example D — Security Incident Backlog

Scenario:

A security team faces multiple incidents, patch demands, forensic tasks, reporting requirements, and executive pressure. The team attempts full remediation without reducing load or adding capacity.

Law expression:

R_eff_security < incident_load × urgency_gain ⇒ remediation instability

Interpretation:

The team closes visible issues but misses persistence, root cause, logging gaps, and recurrence pathways. Incident response becomes pseudo-restoration.

Example E — Governance Justice Bottleneck

Scenario:

A governance system increases exposure and reporting pathways for harm but does not increase intake capacity, repair logistics, victim support, adjudication bandwidth, or prevention infrastructure.

Law expression:

R_eff_justice < case_load × exposure_gain ⇒ justice pathway failure

Interpretation:

More reports do not automatically produce justice. Without restoration capacity, exposure becomes destabilizing and harmed nodes face additional burden.

Example F — Cultural Reconciliation Demand

Scenario:

A community asks for rapid reconciliation after conflict while boundaries, safety, material repair, and trust capacity remain damaged.

Law expression:

R_eff_social < reconciliation_load × identity_gain ⇒ reinjury loop

Interpretation:

The demand for reconciliation exceeds restoration capacity. First moves may need boundary stabilization, decoupling, slack, truth, consequence, and phased repair.

12. Relationship to Nearby Laws

Aliases folded into this law:

• Restoration Capacity Sufficiency Law
• Repair Capacity Threshold Law
• Restoration Load-Gain Law
• Insufficient Repair Capacity Law
• Repair Amplification Law
• Capacity Before Repair Law
• Restoration Load Limit Law

Deduplication note:

This law should remain the root restoration-capacity threshold law. LAW-023 handles restoration capacity under load in the broader scaling family; LAW-066 specializes the threshold for active repair attempts. LAW-075 covers capacity-before-demand generally, while LAW-066 covers repair demand specifically.

13. Operator Mapping

Coherent operator sequence:

Γ(Load + Gain + R_eff) → Θ(capacity uncertainty) → Σ(scope repair) → Π(Load↓ / Gain↓ if needed) → ⊗↓ / BΣ stabilize → ℛ(capacity-matched repair) → Ψ(validate field effects) → Τ(validate R_eff ≥ Load × Gain)

Inverted operator sequence:

failure visible → urgency↑ → repair demand↑ → Gain↑ → R_eff ignored → ℛ overloaded → σ↓ / 𝓓↓ → H↑ → recurrence↑ → pseudo-restoration

14. Machine-Readable Summary

id: "LAW-066"
name: "Restoration Capacity Sufficiency Law"
type: "law"
status: "draft"
family:
  - "Restoration Laws"
summary: "Repair attempts amplify instability when effective restoration capacity is lower than the load multiplied by gain."
canonical_statement: "Repair attempts amplify instability when restoration capacity is lower than load times gain."
core_form: "R_eff < Load × Gain ⇒ repair attempt amplifies instability"
capacity_sufficient_form: "R_eff ≥ Load × Gain ⇒ repair may proceed coherently"
expanded_form: "repair_attempt under R_eff deficit ⇒ σ↓ + 𝓓↓ + H↑ + recurrence↑ + O↓"
stabilization_first_form: "R_eff < Load × Gain ⇒ first move = Load↓ and/or Gain↓ and/or R_eff↑"
variables:
  primary:
    - "R_eff"
    - "Load"
    - "Gain"
    - "ℛ"
    - "O"
    - "H"
    - "BΣ"
    - "K"
    - "σ"
    - "𝓓"
  secondary:
    - "ε"
    - "ι"
    - "Ξ"
    - "Au"
    - "FI"
    - "µᵢ"
    - "Φ"
    - "Λ"
    - "⊗"
    - "Γ"
    - "Π"
    - "Θ"
    - "Σ"
    - "Ψ"
    - "Τ"
diagnostics:
  - "Effective Restoration Capacity"
  - "Load"
  - "Gain"
  - "Slack"
  - "Bandwidth"
  - "Ring-Down"
  - "Recurrence"
  - "Latency"
  - "Hidden Debt"
  - "Boundary Integrity"
  - "Coherence Trajectory"
  - "Restoration Validity"
  - "Pseudo-Restoration Risk"
failure_modes:
  - "Repair-Induced Instability"
  - "Restoration Capacity Exhaustion"
  - "Overloaded Repair Pathway"
  - "Gain-Amplified Repair Failure"
  - "Premature Repair Attempt"
  - "Feedback Without Slack"
  - "Reinjury Loop"
  - "Pseudo-Restoration"
  - "Delayed Collapse"
  - "Burden Inversion"
  - "Capacity-Demand Mismatch"
  - "Restoration Burnout"
restoration_arcs:
  - "Restoration Capacity Rebuild"
  - "Load Shedding"
  - "Gain Reduction"
  - "Controlled Decoupling"
  - "Boundary Stabilization"
  - "Slack Regeneration"
  - "Origin-Layer Repair"
  - "Auditability Restoration"
  - "Temporal Validation"
  - "Recurrence Reduction"
related_laws:
  - "LAW-006"
  - "LAW-007"
  - "LAW-008"
  - "LAW-010"
  - "LAW-011"
  - "LAW-012"
  - "LAW-020"
  - "LAW-021"
  - "LAW-022"
  - "LAW-023"
  - "LAW-024"
  - "LAW-030"
  - "LAW-047"
  - "LAW-049"
  - "LAW-050"
  - "LAW-052"
  - "LAW-061"
  - "LAW-062"
  - "LAW-063"
  - "LAW-064"
  - "LAW-065"
  - "LAW-067"
  - "LAW-068"
  - "LAW-073"
  - "LAW-075"
  - "LAW-076"
related_invariants:
  - "INV-001"
  - "INV-006"
  - "INV-077"
  - "INV-079"
  - "INV-080"
operator_sequence:
  coherent:
    - "Γ Load + Gain + R_eff"
    - "Θ capacity uncertainty"
    - "Σ scope repair"
    - "Π Load↓ / Gain↓ if needed"
    - "⊗↓ / BΣ stabilize"
    - "ℛ capacity-matched repair"
    - "Ψ validate field effects"
    - "Τ validate R_eff ≥ Load × Gain"
  inverted:
    - "failure visible"
    - "urgency↑"
    - "repair demand↑"
    - "Gain↑"
    - "R_eff ignored"
    - "ℛ overloaded"
    - "σ↓ / 𝓓↓"
    - "H↑"
    - "recurrence↑"
    - "pseudo-restoration"
aliases:
  - "Restoration Capacity Sufficiency Law"
  - "Repair Capacity Threshold Law"
  - "Restoration Load-Gain Law"
  - "Insufficient Repair Capacity Law"
  - "Repair Amplification Law"
  - "Capacity Before Repair Law"
  - "Restoration Load Limit Law"
deduplication_note: "Root restoration-capacity threshold law. LAW-023 handles restoration capacity under load in the broader scaling family; LAW-066 specializes the threshold for active repair attempts. LAW-075 covers capacity-before-demand generally, while LAW-066 covers repair demand specifically."
source: "content/archive/laws/technical.md"

15. Compact Card Version

LAW-066 — Restoration Capacity Sufficiency Law

Repair attempts amplify instability when restoration capacity is lower than load times gain.

Core form:

R_eff < Load × Gain ⇒ repair attempt amplifies instability

Capacity-sufficient form:

R_eff ≥ Load × Gain ⇒ repair may proceed coherently

Plain meaning:

A system cannot repair more than its restoration capacity can carry. When the repair burden, amplified by gain, exceeds available restoration capacity, the repair attempt itself can destabilize the system.

Expanded form:

repair_attempt under R_eff deficit ⇒ σ↓ + 𝓓↓ + H↑ + recurrence↑ + O↓

Stabilization-first form:

R_eff < Load × Gain ⇒ first move = Load↓ and/or Gain↓ and/or R_eff↑

Primary variables:

R_eff, Load, Gain, ℛ, O, H, BΣ, K, σ, 𝓓, ι, Au, FI, µᵢ, Γ, Π, Θ, Σ, Ψ, Τ

Diagnostic signature:

Repair demand rises under high gain while effective restoration capacity is insufficient; slack drops, damping worsens, hidden debt increases, recurrence rises, and coherence declines.

Failure risk:

Repair-induced instability, restoration capacity exhaustion, overloaded repair pathway, gain-amplified repair failure, premature repair attempt, feedback without slack, reinjury loop, burden inversion, pseudo-restoration, delayed collapse.

Restoration priority:

Assess Load × Gain, measure R_eff, reduce load, reduce gain, decouple if needed, stabilize boundaries, regenerate slack, rebuild restoration capacity, then apply phased repair and time-validate recurrence reduction.