0. Restoration Scope Note

This entry is conceptual and systems-oriented.

It does not treat every difficult, costly, time-consuming, emotionally demanding, procedurally complex, or multi-stage repair process as failed.

Some restoration requires work.

Some repair requires participation.

Some justice processes require evidence.

Some reconciliation requires time.

Some healing requires sustained effort.

Some institutions require process to verify claims, allocate resources, prevent recurrence, and protect all affected parties.

The failure begins when the repair process extracts more capacity from the affected node than it restores.

A coherent restoration system may require participation, but it must remain net-restorative.

A failed restoration system requires the injured, depleted, burdened, excluded, harmed, or destabilized node to carry the repair process itself.

Capacity-Inverting Restoration occurs when restoration becomes capacity-negative for the node it claims to restore.

The problem is not that repair has cost.

The problem is repair being structured so that the target of repair must spend more capacity than the repair returns.

1. Definition

Capacity-Inverting Restoration occurs when a repair, justice, reconciliation, governance, institutional, platform, relational, or recovery process claims to restore an affected node while requiring that node to spend more capacity, labor, risk, attention, proof, emotional load, procedural effort, or survival margin than the repair returns, causing restoration to become capacity extraction under repair language.

The consumed capacity may include:

• time
• money
• attention
• energy
• health
• credibility
• safety
• privacy
• legal capacity
• procedural capacity
• social capacity
• emotional capacity
• operational capacity
• creative capacity
• recovery capacity
• relational capacity
• cognitive bandwidth
• documentation burden
• proof burden
• appeal burden
• coordination burden
• reputational risk
• retaliation risk
• survival margin

The claimed repair may include:

• complaint process
• appeal process
• reconciliation process
• mediation
• investigation
• settlement
• restoration meeting
• review process
• support process
• healing process
• reintegration process
• grievance process
• remediation path
• recovery plan
• accountability pathway
• reporting mechanism
• compensation process
• contract renegotiation
• trust and safety review
• institutional justice process

The core failure is:

affected node needs restoration
→ system offers repair path
→ repair path requires high capacity from affected node
→ affected node depletes further while pursuing repair
→ system counts process as restoration
→ net capacity declines
→ hidden debt increases

Capacity-Inverting Restoration is not simply slow repair.

It is repair whose operational burden contradicts its restorative purpose.

2. Core Pattern

The core pattern is:

1. A node, group, user, worker, community, relation, system, body, or field is harmed, depleted, excluded, exploited, destabilized, or burdened.
2. The system offers a repair process.
3. The repair process requires the affected node to provide proof, patience, documentation, emotional labor, explanation, repeated testimony, procedural navigation, risk tolerance, or self-advocacy.
4. The affected node must spend scarce capacity to access the repair.
5. The system counts the availability of process as evidence of restoration.
6. The affected node becomes more depleted while pursuing repair.
7. The burden of making restoration happen shifts away from the responsible system.
8. Repair becomes selective for those with enough remaining capacity to survive the repair process.
9. The most depleted nodes are least able to access restoration.
10. The system appears reparative while increasing hidden capacity debt.

A healthy system says:

repair must increase the net capacity of the affected node

A capacity-inverting system says:

repair is available if the affected node can endure the process

The failure is especially dangerous because the system can point to process availability.

There may be forms.

There may be review.

There may be meetings.

There may be appeals.

There may be statements of support.

There may be resources.

There may be case managers.

There may be listening sessions.

But access to restoration is conditioned on the affected node having enough residual capacity to pursue it.

The repair process becomes a filter that selects against those most in need of repair.

3. Failure Signature

Typical signature:

repair process↑
affected-node labor↑
proof burden↑
procedural load↑
capacity drain↑
actual restoration↓
access equity↓
hidden capacity debt↑
R_effective↓
O↓

Extended signature:

repair offered,
burden transferred

process expands,
capacity declines

proof demanded,
depletion deepens

support exists,
access requires endurance

restoration claimed,
affected node pays

Common verbal signatures include:

we have a process for that
they need to file the correct form
they must prove harm
they need to keep following up
we need them to participate in the process
we cannot help unless they complete the steps
they are not engaging with available support
they rejected the repair pathway
they need to be patient
we already offered mediation
we already opened a case
they did not provide enough documentation
they are making the process difficult

Common system signatures include:

a harmed user must repeatedly appeal an automated decision with no clear route to review
an injured worker must manage complex documentation while depleted
a community must prove harm repeatedly before resources are released
a platform offers support that requires high attention from users already harmed by the system
an institution requires repeated testimony before acknowledging a known pattern
a contract renegotiation process burdens the weaker party with legal and procedural load
a restorative meeting requires the affected party to educate, soothe, or guide the responsible party
a complaint pathway exists but is too slow, confusing, risky, or exhausting for depleted nodes

The defining condition is not that participation is required.

The defining condition is that repair requires capacity expenditure that exceeds, delays, or undermines the capacity restoration it claims to provide.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: the system avoids direct repair cost by shifting process burden onto affected nodes.
• U2 — Configuration / Boundaries: repair pathways are designed with high access friction.
• U3 — Execution / Runtime: affected nodes must repeatedly perform procedural labor.
• U4 — Information / Truth: process availability is narrated as sufficient repair.
• U5 — Coordination / Time: repair delay consumes remaining capacity.
• U6 — Coherence Field: support language masks capacity extraction.
• U7 — Memory / Recurrence: repeated burden patterns become normalized as standard process.
• U8 — Environment / Field: external systems reward documented process over net restoration.

Common manifestation layers:

• U2 — Boundaries: restoration access gates become too costly.
• U3 — Execution: repair work is pushed onto the affected node.
• U4 — Truth: the existence of process is treated as restoration.
• U5 — Time: slow repair erodes capacity.
• U6 — Field: legitimacy is claimed through available support.

Capacity-Inverting Restoration is primarily an R / K / H / Φ failure.

Restoration capacity is inverted into load.

Repair flows are routed away from affected-state rebuilding and toward process endurance.

5. Typical Development Sequence

A common development sequence is:

1. Affected node suffers harm, burden, exclusion, depletion, or loss.
2. System creates or references a repair pathway.
3. The pathway requires forms, evidence, meetings, escalation, repeated contact, emotional labor, or procedural endurance.
4. Affected node must spend scarce capacity to pursue repair.
5. Responsible system delays, fragments, or conditions restoration.
6. The repair process consumes more capacity than it restores.
7. Affected node disengages, collapses, settles, accepts symbolic repair, or is labeled non-cooperative.
8. System records the repair pathway as available.
9. Unrepaired burden remains.
10. Hidden debt grows.
11. Future affected nodes face the same capacity-inverting pathway.
12. The system becomes more efficient at offering repair without restoring.

The loop often looks like:

harm → repair pathway → procedural burden → affected-node depletion → failed access → repair claim remains

Another common loop is:

depletion → proof demand → more depletion → incomplete proof → denied restoration

Capacity-Inverting Restoration becomes durable when the system measures the existence of process rather than the net capacity of the affected node after repair.

6. Diagnostic Markers

Diagnostic markers include:

• Affected nodes must repeatedly prove the same harm.
• Repair access requires high time, attention, money, documentation, or coordination.
• The system counts a process as repair even when capacity does not improve.
• The most depleted nodes are least able to complete the pathway.
• Support exists but requires high procedural literacy.
• Repair timelines exceed the affected node’s remaining capacity margin.
• Affected nodes disengage because the process is too costly.
• The system labels disengagement as refusal, non-cooperation, or lack of interest.
• The responsible system requires the affected node to educate or guide it.
• The repair process increases exposure, retaliation risk, or reputational danger.
• The process protects institutional pacing more than affected-state urgency.
• Capacity metrics are absent from repair evaluation.
• Repair staff or procedures are under-resourced while demand is high.
• Restoration is conditional on endurance.

Useful diagnostics:

• Net Restoration Capacity: Measures whether the affected node has more usable capacity after repair.
• Repair Load Burden: Measures the effort required to access repair.
• Affected-Node Depletion: Tracks capacity decline during the repair process.
• Proof Burden Load: Measures evidence and documentation demands.
• Restoration Return Ratio: Compares capacity spent to capacity restored.
• Capacity Extraction Index: Detects repair pathways that extract more than they return.
• Repair Accessibility: Tests whether low-capacity nodes can actually access restoration.
• Hidden Capacity Debt: Tracks unresolved depletion created by repair process burden.
• Post-Repair Function: Measures the affected node’s functional state after repair.
• Repair-Induced Attrition: Tracks dropout due to repair pathway burden.

7. Related Gates

Relevant gates include:

• Restoration Capacity Gate: Fails when repair reduces rather than increases capacity.
• Net Capacity Gate: Fails when the affected node exits repair with less capacity.
• Affected-State Repair Gate: Fails when process occurs without affected-state restoration.
• Repair Load Gate: Fails when the burden of accessing repair is too high.
• Burden Transfer Gate: Fails when the repair burden shifts to the affected node.
• Proof Burden Gate: Fails when evidence requirements exceed repair capacity.
• Justice Access Gate: Fails when justice is available only to high-capacity nodes.
• Exhaustion Gate: Fails when restoration requires endurance beyond the affected node’s margin.
• Hidden Debt Gate: Fails when repair-induced depletion is not counted.
• Closure Gate: Fails when the process is closed after the affected node is exhausted.

The first common gate failure is usually the Repair Load Gate.

Once repair access requires too much capacity, the restoration pathway becomes structurally unavailable to those most harmed.

8. Related Operators

Relevant operators include:

• R — Restoration Capacity: Primary operator; restoration must increase capacity but instead drains it.
• K — Constraint / Load: Repair adds load rather than reducing it.
• H — Hidden Debt: Capacity loss accumulates beneath process availability.
• O — Coherence: Declines when repair contradicts restoration purpose.
• Φ — Flow / Resource Movement: Repair flows are blocked, delayed, or rerouted into process.
• Au — Auditability: Fails when process availability is measured instead of net repair.
• BΣ — Boundary Integrity: Fails when affected nodes must overexpose themselves to access repair.
• E — Exit: Affected nodes may be trapped between enduring repair burden and abandoning restoration.
• Τ — Trajectory / Time: Delay consumes capacity over time.
• D — Damping: Can stabilize repair pacing or suppress urgent response.
• Γ — Selection: Selects high-capacity claimants and filters out depleted nodes.
• Ψ — Observation / Interface: Displays repair infrastructure while hiding capacity cost.
• M — Meaning: Support and care language can mask extraction.
• Λ — Compatibility: Tests whether the repair process is compatible with the affected node’s capacity state.

Common operator pattern:

R claimed
K↑ on affected node
Φ delayed or misrouted
Au measures process, not capacity
H↑
R_effective↓
O↓

The core operator inversion is:

restoration process consumes restoration capacity

instead of:

restoration process rebuilds the capacity required for restoration

Capacity-Inverting Restoration converts repair from a load-reducing operation into a load-generating demand.

9. Related Laws and Invariants

Related Laws

• Restoration Must Increase Net Capacity: repair must leave the affected node more capable, not less.
• Repair Must Not Consume the Repaired: restoration cannot feed on the remaining capacity of the repair target.
• Affected Nodes Must Not Pay More Capacity Than Restoration Returns: access cost must stay below repair value.
• Repair Burden Must Stay Below Restoration Return: procedural load must not exceed restorative effect.
• Restoration Requires Load Reduction: repair without load reduction is incomplete.
• Justice Must Not Extract From the Injured Node: justice access cannot depend on depletion.
• False Repair: repair form can preserve unresolved burden.
• Victim Burden Inversion: repair labor can be shifted onto the affected node.
• Under-Resourced Justice: insufficient capacity can turn justice process into burden transfer.
• Repair Burden Externalization: systems can offload repair work onto those needing repair.
• Restoration Starvation: restoration fails when capacity is withheld.
• Hidden Debt Accumulation: unrepaired burden and repair-induced burden accumulate as debt.

Related Invariants

• Restoration Must Be Net-Capacity Positive: repair must increase usable capacity.
• Affected-State Repair Must Reduce Burden: the affected state must improve.
• Repair Process Must Not Exhaust the Repair Target: access cannot require depletion.
• Proof Burden Must Not Exceed Repair Capacity: evidence demands must be proportionate.
• Justice Access Must Not Require Depletion: justice must be accessible to low-capacity nodes.
• Restoration Must Preserve Agency: repair cannot make affected nodes dependent, trapped, or coerced.
• Repair Load Must Be Counted: the burden of repair must be measured.
• Capacity Debt Must Be Audited: capacity lost during repair must not disappear from accounting.

10. Common False Positives

Not every demanding repair process is Capacity-Inverting Restoration.

Common false positives include:

• A demanding but net-restorative process that clearly increases affected-node capacity.
• A complex evidence process with support, advocacy, time protection, and burden reduction.
• Participation requirements that are proportional, accessible, and capacity-aware.
• A long repair process where interim support prevents depletion.
• A justice process that requires documentation but provides assistance to produce it.
• A reconciliation process chosen freely by affected nodes with adequate support.
• A recovery process that asks effort while restoring more capacity than it consumes.
• A contract renegotiation process where the weaker party receives support, counsel, time, and protection.
• A platform appeal process that is simple, fast, transparent, and capacity-light.
• A governance process that reduces burden while verifying claims.

Clarifying rule:

This is not Capacity-Inverting Restoration unless the repair pathway consumes, risks, delays, or extracts more capacity from the affected node than it restores.

Repair may require effort.

It fails when the effort required becomes restoration-negative.

11. Common False Repairs

Common false repairs include:

• adding more process steps
• creating a support portal that requires high user effort
• assigning a case manager without reducing procedural load
• asking affected nodes to resubmit information
• creating a formal appeal with no capacity support
• offering mediation that requires the harmed node to educate the responsible party
• extending deadlines while leaving burden unchanged
• documenting participation without measuring depletion
• offering symbolic recognition for enduring the process
• blaming dropout on lack of engagement
• adding resources that are hard to access
• creating “self-service” repair for low-capacity nodes
• requiring repeated testimony as proof of seriousness
• treating exhaustion as closure
• measuring case completion instead of restoration

False repair often produces the loop:

repair burden exposed
→ process support added
→ process still consumes capacity
→ net restoration remains negative

Another common loop is:

affected node cannot continue
→ system marks non-participation
→ repair obligation weakens
→ hidden debt remains

The repair fails because it improves the appearance or availability of process without changing the capacity economics of repair.

12. Restoration Direction

Restoration requires making repair net-capacity-positive, reallocating repair burden away from depleted nodes, reducing proof and procedural load, providing capacity support, and measuring success by affected-state improvement rather than process completion.

Primary restoration direction:

repair must return more capacity than it consumes

A fuller restoration path includes:

1. Identify the affected node’s capacity state. Determine available time, energy, safety, money, attention, trust, health, and procedural bandwidth.
2. Measure repair load. Count every form, meeting, delay, testimony, exposure, escalation, coordination act, and proof demand.
3. Compare load to return. Determine whether the repair process is net-capacity-positive or net-capacity-negative.
4. Remove unnecessary burden. Eliminate steps that protect the process more than the affected state.
5. Shift burden to the responsible system. Require the system with more capacity to perform the repair work.
6. Provide navigation support. Make access possible for low-capacity nodes.
7. Reduce proof burden. Use known patterns, existing records, and system-side evidence where possible.
8. Provide interim relief. Prevent depletion during long repair pathways.
9. Protect against retaliation or exposure. Reduce risk created by pursuing repair.
10. Make restoration accessible. Design for the most depleted legitimate claimant, not the most resilient.
11. Audit attrition. Treat dropout as a signal of repair burden, not proof of no need.
12. Measure post-repair capacity. Evaluate whether the affected node is actually more capable.
13. Count repair-induced debt. Repair capacity consumed by the process must be included in restoration accounting.
14. Redesign future pathways. Ensure the next affected node does not pay the same access cost.

A valid restoration path should reduce:

repair load
proof burden
procedural friction
affected-node depletion
capacity extraction
repair-induced attrition
hidden capacity debt
restoration delay

Capacity-Inverting Restoration is not repaired by making the process more formal.

It is repaired by changing the net capacity equation.

13. Cross-Module Links

• Restoration: Primary family; repair fails when it consumes the capacity it claims to restore.
• False Repair: Strongly linked to Repair Burden Externalization, Infinite Repair Loop, and Repair as Compliance.
• Justice: Justice fails when access requires depletion from those already harmed.
• Contracts: Contract repair fails when weaker parties must spend disproportionate legal, procedural, or coordination capacity.
• Governance: Governance repair fails when affected groups must carry the burden of institutional correction.
• Platforms: Platform appeals, moderation review, account recovery, and safety support can become capacity-inverting when user burden is high.
• AI Governance: AI harm reporting, redress, opt-out, appeal, and evaluation systems can shift capacity load onto affected users.
• Security: Security remediation can burden those harmed by overreach, surveillance, false positives, or access denial.
• Economy: Economic repair fails when relief requires costly navigation by depleted nodes.
• Biology: Living systems can enter recovery pathways that consume more energy than they restore.
• Coherence: Coherence requires restoration to reduce burden at the point where burden exists.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry / Canon-Aligned

This mode maps upward to:

• FM-R-004 — Repair Burden Externalization
• FM-R-013 — Victim Burden Inversion
• FM-JC-004 — Under-Resourced Justice
• FM-S-006 — Restoration Starvation
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Restoration modes include:

• FM-R-001 — Cosmetic Restoration
• FM-R-002 — Process Inflation
• FM-R-003 — Insight Without Load Reduction
• FM-R-004 — Repair Burden Externalization
• FM-R-006 — Repair as Compliance
• FM-R-007 — Repair Suppression via Efficiency
• FM-R-009 — Therapeutic Capture
• FM-R-010 — Infinite Repair Loop
• FM-R-011 — Symbolic Repair Substitution
• FM-R-013 — Victim Burden Inversion

Related Justice / Contract modes include:

• FM-JC-001 — Procedural Theater
• FM-JC-004 — Under-Resourced Justice
• FM-JC-005 — Amnesty Without Repair
• FM-JC-008 — Post-Signing Environmental Incoherence
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-JC-012 — Parasitic Contracting

Related cross-family modes include:

• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-004 — Auditability Collapse
• FM-S-006 — Restoration Starvation
• FM-S-015 — Bandwidth Saturation
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-ECOX-025 — Repair Starvation
• FM-BIOX-005 — Energy-First Compression
• FM-AIX-022 — Dependency Loop Formation
• FM-SEC-012 — Exit Failure / Recapture

Aliases preserved from source material:

• Capacity-Inverting Restoration
• Capacity-Inverted Repair
• Restoration Capacity Inversion
• Repair That Consumes the Repaired
• Capacity-Extractive Restoration
• Repair-as-Capacity Drain
• Burden-Positive Repair
• Restoration That Costs More Than It Returns
• Extractive Repair Process
• Repair Through Affected-Node Depletion

15. Minimal Entry Version

Definition: Capacity-Inverting Restoration occurs when a repair, justice, reconciliation, governance, institutional, platform, relational, or recovery process claims to restore an affected node while requiring that node to spend more capacity, labor, risk, attention, proof, emotional load, procedural effort, or survival margin than the repair returns, causing restoration to become capacity extraction under repair language.

Signature:

repair process↑
affected-node labor↑
proof burden↑
procedural load↑
capacity drain↑
actual restoration↓
access equity↓
hidden capacity debt↑
R_effective↓
O↓

Restoration direction:

• identify the affected node’s capacity state
• measure repair load
• compare load to return
• remove unnecessary burden
• shift burden to the responsible system
• provide navigation support
• reduce proof burden
• provide interim relief
• protect against retaliation or exposure
• make restoration accessible
• audit attrition
• measure post-repair capacity
• count repair-induced debt
• redesign future pathways

16. Machine-Readable Summary

failure_mode:
  id: "FM-R-012"
  name: "Capacity-Inverting Restoration"
  family: "Restoration / False Repair"
  production_treatment: "Standalone Entry / Canon-Aligned"
  source_lineage:
    - "FM-RX-004 — Capacity-Inverting Restoration"
    - "Restoration / JGL Extended"
    - "False Repair Family"
  parent_modes:
    - "FM-R-004 — Repair Burden Externalization"
    - "FM-R-013 — Victim Burden Inversion"
    - "FM-JC-004 — Under-Resourced Justice"
    - "FM-S-006 — Restoration Starvation"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "A repair, justice, reconciliation, governance, institutional, platform, relational, or recovery process claims to restore an affected node while requiring that node to spend more capacity, labor, risk, attention, proof, emotional load, procedural effort, or survival margin than the repair returns, causing restoration to become capacity extraction under repair language."
  scope_note: "Conceptual and systems-oriented; does not treat every difficult, costly, time-consuming, emotionally demanding, procedurally complex, or multi-stage repair process as failed."
  aliases:
    - "Capacity-Inverting Restoration"
    - "Capacity-Inverted Repair"
    - "Restoration Capacity Inversion"
    - "Repair That Consumes the Repaired"
    - "Capacity-Extractive Restoration"
    - "Repair-as-Capacity Drain"
    - "Burden-Positive Repair"
    - "Restoration That Costs More Than It Returns"
    - "Extractive Repair Process"
    - "Repair Through Affected-Node Depletion"
  signature:
    - "repair process↑"
    - "affected-node labor↑"
    - "proof burden↑"
    - "procedural load↑"
    - "capacity drain↑"
    - "actual restoration↓"
    - "access equity↓"
    - "hidden capacity debt↑"
    - "R_effective↓"
    - "O↓"
  primary_layers:
    origin:
      - "U1 — Power / Budgets"
      - "U2 — Configuration / Boundaries"
      - "U3 — Execution / Runtime"
      - "U4 — Information / Truth"
      - "U5 — Coordination / Time"
      - "U6 — Coherence Field"
      - "U7 — Memory / Recurrence"
      - "U8 — Environment / Field"
    manifestation:
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
  state_variables:
    - "R"
    - "K"
    - "H"
    - "O"
    - "Φ"
    - "Au"
    - "BΣ"
    - "E"
    - "Τ"
    - "D"
    - "Γ"
    - "Ψ"
    - "M"
    - "Λ"
  first_gate_failure: "Repair Load Gate"
  restoration:
    - "Net Capacity Restoration Audit"
    - "Repair Load Reduction"
    - "Affected-Node Capacity Rebuild"
    - "Proof Burden Reallocation"
    - "Restoration Access Repair"
    - "Capacity Debt Accounting"
    - "Justice Process Load Audit"
    - "Repair Burden Rebalancing"
    - "Post-Repair Function Review"
    - "Restoration Capacity Reconstitution"