schema_version: "1.0"

id: "FM-R-004"

title: "FM-R-004 — Repair Burden Externalization"

slug: "fm-r-004-repair-burden-externalization"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Repair Burden Externalization occurs when the work, cost, proof, coordination, emotional load, administrative labor, risk, time, explanation, or restoration responsibility required to repair harm is shifted away from the source of burden and onto affected nodes, downstream systems, lower-power actors, volunteers, future budgets, or the wider field."

canonical_url: "/archive/failure-modes/registry/false-repair/fm-r-004-repair-burden-externalization"

citation_id: "FM-R-004-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-R-004"

classification:

family: "failure-modes"

module: "false-repair"

module_group: "restoration"

density: "advanced-reference"

audience:

• "UTS readers"
• "restoration researchers"
• "justice researchers"
• "contract researchers"
• "cybernetics researchers"
• "AI governance researchers"
• "security researchers"
• "organizational systems researchers"
• "coherence researchers"
• "machine readers"

tags:

• "failure-modes"
• "false-repair"
• "repair-burden-externalization"
• "fm-r-004-repair-burden-externalization"
• "burden-transfer"
• "victim-burden-inversion"
• "externalization"
• "proof-burden"
• "administrative-load"
• "hidden-debt"
• "restoration"
• "coherence"

aliases:

• "Repair Burden Externalization"
• "Externalized Repair Burden"
• "Repair Cost Shifting"
• "Restoration Burden Transfer"
• "Burdened-Node Repair Load"
• "Affected-Node Repair Burden"
• "Proof Burden Externalization"
• "Repair Work Offloading"
• "Restoration Responsibility Displacement"
• "Victim Repair Load"

related:

laws:

• "Victim Burden Inversion"
• "Capacity-Inverting Restoration"
• "Exported Economic Incoherence"
• "Parasitic Extraction"
• "Pseudo-Restoration"
• "Insight Without Load Reduction"
• "Process Inflation"
• "Conditional Coercive Delivery"
• "Coercive Contract"
• "Under-Resourced Justice"
• "Hidden Debt Accumulation"
• "Auditability Collapse"

invariants:

• "Repair Burden Must Follow Causal Responsibility"
• "Affected Nodes Must Not Carry the Repair Debt Alone"
• "Proof Must Not Become Punishment"
• "Restoration Must Reduce Affected-Node Load"
• "Repair Responsibility Must Remain Attached to Source"
• "Externalized Repair Must Be Accounted"
• "Redress Must Not Require Further Extraction"

operators:

• "R — Restoration Capacity"
• "H — Hidden Debt"
• "K — Constraint / Load"
• "Φ — Flow / Resource Movement"
• "BΣ — Boundary Integrity"
• "Au — Auditability"
• "Γ — Selection"
• "Ψ — Observation / Interface"
• "Λ — Compatibility"
• "O — Coherence"
• "G — Gain"
• "D — Damping"
• "Τ — Trajectory / Time"

gates:

• "Repair Responsibility Gate"
• "Burden Allocation Gate"
• "Affected-Node Protection Gate"
• "Proof Burden Gate"
• "Restoration Gate"
• "Capacity Gate"
• "Auditability Gate"
• "Justice Gate"
• "Local Coherence Gate"

diagnostics:

• "Repair Burden Allocation"
• "Affected-Node Load"
• "Proof Burden"
• "Responsibility Traceability"
• "Restoration Capacity"
• "Burden Transfer"
• "Hidden Debt"
• "Administrative Load"
• "Auditability"
• "Local Coherence"

failure_modes:

• "FM-R-002 — Process Inflation"
• "FM-R-003 — Insight Without Load Reduction"
• "FM-R-006 — Repair as Compliance"
• "FM-R-008 — Audit Evasion in Repair"
• "FM-R-009 — Therapeutic Capture"
• "FM-R-010 — Infinite Repair Loop"
• "FM-RX-004 — Capacity-Inverting Restoration"
• "FM-RX-005 — Victim Burden Inversion"
• "FM-ECO-011 — Exported Economic Incoherence"
• "FM-ECO-013 — Conditional Coercive Delivery"
• "FM-ECO-023 — Asymmetric Bandwidth"
• "FM-JC-004 — Under-Resourced Justice"

restoration_arcs:

• "Repair Burden Audit"
• "Causal Responsibility Reattachment"
• "Affected-Node Load Reduction"
• "Proof Burden Reduction"
• "Repair Resource Transfer"
• "Administrative Load Removal"
• "Redress Path Simplification"
• "Hidden Repair Debt Accounting"
• "Standing Restoration"
• "Local Coherence Restoration"

modules:

• "False Repair"
• "Restoration"
• "Justice"
• "Contracts"
• "Economy"
• "Cybernetics"
• "Security"
• "AI Governance"
• "Interfaces"
• "Coherence"

navigation:

order: 1404

parent: "failure-modes"

visible: true

provenance:

created_from: "failure-mode-registry-production"

source_thread: "UTS Failure Modes Registry production"

source_file: "content/archive/failure-modes/registry/false-repair/fm-r-004-repair-burden-externalization.md"

notes: "Expanded from False Repair family index entry and aligned to normalized metadata structure. Standalone false repair entry focused on the burden of repair being shifted onto affected nodes, lower-power actors, downstream systems, volunteers, future budgets, or the wider field instead of remaining with the source of harm or the responsible repair-capable node."

entry:

failure_mode_id: "FM-R-004"

failure_family: "False Repair"

production_treatment: "Standalone Entry"

parent_modes:

• "FM-RX-005 — Victim Burden Inversion"
• "FM-RX-004 — Capacity-Inverting Restoration"
• "FM-ECO-011 — Exported Economic Incoherence"
• "FM-C-021 — Parasitic Extraction"
• "FM-CORE-002 — Hidden Debt Accumulation"

first_gate_failure: "Repair Responsibility Gate"

primary_hidden_debt: "Hidden debt accumulates when the harmed or burdened node must spend additional time, proof, labor, attention, money, coordination, risk, or capacity to obtain the repair owed by another node."

primary_inversion: "Repair becomes further burden; the system treats the affected node’s effort to secure repair as part of restoration while actually increasing the load created by the original harm."

primary_boundary_pattern: "The boundary between responsibility and burden collapses; the node that should receive repair becomes responsible for producing, proving, coordinating, funding, or carrying it."

primary_signature: "Harm or burden occurs; repair is nominally available; affected node must initiate, prove, explain, document, coordinate, wait, pay, or risk more to receive repair; source responsibility weakens; hidden debt grows under repair language."

FM-R-004 — Repair Burden Externalization

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-R-004

Family: False Repair

Production Treatment: Standalone Entry

Parent Modes: FM-RX-005 — Victim Burden Inversion; FM-RX-004 — Capacity-Inverting Restoration; FM-ECO-011 — Exported Economic Incoherence; FM-C-021 — Parasitic Extraction; FM-CORE-002 — Hidden Debt Accumulation

0. False Repair Scope Note

This entry is conceptual and systems-oriented.

It does not treat participation, testimony, feedback, documentation, self-advocacy, claim submission, local coordination, affected-node input, or shared repair as inherently failed.

Affected nodes may need to participate in repair.

Their knowledge can be essential.

Repair can be coherent when affected-node participation is:

• voluntary
• supported
• compensated where appropriate
• bounded
• not repetitive
• not extractive
• not required to prove the obvious
• paired with material relief
• protected from retaliation
• proportional to need
• not a substitute for responsible-node action
• able to reduce affected-node load

The failure begins when repair requires the affected node to carry the repair burden.

The issue is not participation.

The issue is repair responsibility being displaced onto the node already carrying harm.

Repair Burden Externalization occurs when the path to repair adds new burden to the node that should be relieved.

1. Definition

Repair Burden Externalization occurs when the work, cost, proof, coordination, emotional load, administrative labor, risk, time, explanation, or restoration responsibility required to repair harm is shifted away from the source of burden and onto affected nodes, downstream systems, lower-power actors, volunteers, future budgets, or the wider field.

The externalized repair burden may include:

• proving harm
• repeated retelling
• documentation gathering
• form completion
• claim navigation
• appeal labor
• unpaid coordination
• emotional labor
• self-advocacy
• legal cost
• translation work
• repair project management
• unpaid moderation
• user correction
• data cleanup
• medical navigation
• service escalation
• risk absorption
• future maintenance
• public explanation
• community repair
• administrative burden
• time spent waiting
• travel or access cost
• reputational risk

The core failure is:

repair owed
repair burden shifted outward
affected-node load↑
source responsibility↓
H↑

Repair Burden Externalization is not mutual repair.

It is repair pathway design that turns harmed nodes into unpaid repair infrastructure.

2. Core Pattern

The core pattern is:

1. A system creates harm, burden, debt, failure, extraction, or unmet obligation.
2. Repair is needed.
3. The responsible node does not carry the full repair work.
4. The affected node must initiate, document, prove, navigate, coordinate, appeal, explain, absorb, or wait.
5. The repair pathway becomes an additional burden.
6. The system records the existence of the pathway as repair availability.
7. Many affected nodes cannot complete the pathway.
8. Uncompleted repair is treated as low uptake, insufficient evidence, user failure, or unresolved case status.
9. Hidden debt accumulates in affected nodes and downstream systems.
10. Restoration requires reattaching repair burden to causal responsibility.

This failure often appears as:

repair is available if they apply

while the hidden truth may be:

the application process is part of the burden

or:

they did not provide enough evidence

while the overlooked condition is:

the system made proof harder than repair

The restorative question is:

who is doing the work required to make repair happen?

Repair Burden Externalization turns redress into an extraction pathway.

3. Failure Signature

Typical signature:

repair pathway present
affected-node admin load↑
proof burden↑
source responsibility↓
repair completion↓
H↑

Extended signature:

claims process requires harmed node to prove harm repeatedly
appeal process requires technical knowledge affected node lacks
repair fund exists but access burden blocks use
platform redress requires unpaid user documentation
security recovery requires victims to perform incident cleanup
AI correction requires users to identify, explain, and repair system outputs
institutional apology requires affected nodes to educate the institution

Common forms include:

a company requires customers to navigate long claims processes for errors the company caused
a platform requires users to prove wrongful enforcement through complex appeals
an institution asks harmed communities to design the repair without giving resources or authority
a workplace asks overloaded workers to document overload as condition for relief
a security breach response pushes identity monitoring and recovery labor onto users
an AI system depends on users to correct outputs without compensation or structural fix
a justice process requires harmed nodes to repeatedly retell harm while remedy remains uncertain
a public relief program requires documentation that harmed nodes lost because of the harm

The defining condition is not that affected nodes provide information.

The defining condition is that affected nodes must carry disproportionate repair work to obtain relief from burden they did not create.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: responsible nodes reduce their own repair cost by shifting work outward.
• U2 — Configuration / Boundaries: claim, appeal, support, or redress pathways are designed around provider convenience.
• U3 — Execution / Runtime: repair operations depend on affected-node labor.
• U4 — Information / Truth: repair availability substitutes for repair accessibility.
• U5 — Coordination / Time: delay and repeated proof requirements compound burden.
• U6 — Coherence Field: existence of a process creates legitimacy aura.
• U7 — Memory / Recurrence: externalized repair becomes standard practice.
• U8 — Environment / Field: under-resourced institutions normalize affected-node self-repair.

Common manifestation layers:

• U1 — Power: source keeps resources.
• U2 — Boundaries: repair obligations cross into affected nodes.
• U3 — Execution: affected nodes perform repair labor.
• U4 — Truth: pathway existence is counted as remedy.
• U5 — Time: delays increase burden.
• U6 — Field: redress optics hide extraction.
• U8 — Environment: downstream systems absorb repair debt.

Repair Burden Externalization is primarily a U2 responsibility-boundary and R restoration-capacity failure.

The system displaces the work of restoration onto the node requiring restoration.

5. Typical Development Sequence

A common development sequence is:

1. A harm or failure becomes visible.
2. The system creates a repair pathway.
3. The pathway requires affected nodes to initiate and prove the case.
4. Affected nodes must supply information, time, emotion, documentation, or coordination.
5. The system uses the pathway to demonstrate accountability.
6. Many affected nodes cannot complete it.
7. Incomplete claims reduce visible repair demand.
8. The system interprets lower uptake as lower burden or insufficient proof.
9. Affected nodes remain unrepaired.
10. Repair burden accumulates as hidden debt.
11. The pathway becomes the standard repair response.

The loop often looks like:

harm → repair process → affected-node burden → incomplete repair → hidden debt

Another common loop is:

repair unavailable by default → affected node must prove need → proof burden blocks repair → source claims no valid case

Repair Burden Externalization becomes self-reinforcing when the burdensome repair pathway suppresses the evidence that repair demand exists.

6. Diagnostic Markers

Diagnostic markers include:

• Affected nodes must initiate repair despite the source knowing harm occurred.
• Proof requirements exceed what is necessary.
• Repair access requires repeated retelling or documentation.
• The repair path is hardest for the most burdened nodes.
• Responsible nodes control the evidence standard.
• Low uptake is used to claim low harm.
• Affected nodes need advocates or experts to access remedy.
• Redress requires unpaid labor.
• The system measures availability of repair, not usability of repair.
• Repair delays increase the affected node’s cost.
• The source retains resources while affected nodes spend time and capacity.
• Restoration improves when repair is made automatic, supported, compensated, or source-initiated.

Useful diagnostics:

• Repair Burden Allocation: Determines who performs the work of repair.
• Affected-Node Load: Measures added burden caused by repair pathway.
• Proof Burden: Tests whether evidence requirements are proportional.
• Responsibility Traceability: Tracks whether repair obligation remains attached to source.
• Restoration Capacity: Measures whether responsible nodes provide repair resource.
• Burden Transfer: Identifies where repair work is shifted.
• Hidden Debt: Tracks unrepaired burden and added repair burden.
• Administrative Load: Measures forms, steps, waiting, coordination, and documentation.
• Auditability: Determines whether externalized burden is visible.
• Local Coherence: Tests whether repair pathway actually relieves affected nodes.

7. Related Gates

Relevant gates include:

• Repair Responsibility Gate: Fails when source responsibility is not carried by the source.
• Burden Allocation Gate: Fails when repair load is placed on affected nodes.
• Affected-Node Protection Gate: Fails when repair pathways add burden.
• Proof Burden Gate: Fails when proof requirements become punitive.
• Restoration Gate: Fails when repair availability does not become relief.
• Capacity Gate: Fails when harmed nodes lack capacity to access repair.
• Auditability Gate: Fails when externalized repair work is not counted.
• Justice Gate: Fails when remedy requires disproportionate effort from harmed nodes.
• Local Coherence Gate: Fails when the repair pathway worsens local state.

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

The system fails to keep restoration responsibility attached to the source of burden.

8. Related Operators

Relevant operators include:

• R — Restoration Capacity: Must be held by the responsible repair-capable node.
• H — Hidden Debt: Accumulates through unrepaired burden and added repair labor.
• K — Constraint / Load: Rises on affected nodes as repair work is externalized.
• Φ — Flow / Resource Movement: Determines whether repair resources move toward affected nodes or repair work moves away from source.
• BΣ — Boundary Integrity: Keeps responsibility boundaries intact.
• Au — Auditability: Reveals who carries repair work.
• Γ — Selection: Selects repair path, evidence standard, and burden allocation.
• Ψ — Observation / Interface: Shapes how repair pathway appears.
• Λ — Compatibility: Tests whether repair path fits affected-node capacity.
• O — Coherence: May appear high because a repair process exists.
• G — Gain: Incentivizes responsible nodes to externalize repair cost.
• D — Damping: Should slow burden-shifting and protect affected nodes.
• Τ — Trajectory / Time: Tracks compounding cost from delay.

Common operator pattern:

harm occurs
repair need appears
Γ selects affected-node-initiated pathway
Φ shifts repair work outward
K rises on affected node
R remains under-resourced at source
O appears improved through repair availability
Au fails to count externalized work
H accumulates

The core operator inversion is:

repair pathway available → repair responsibility fulfilled

instead of:

repair pathway available + source-carried burden + affected-node load reduction + completion → repair responsibility fulfilled

Repair Burden Externalization turns access to repair into further work.

9. Related Laws and Invariants

Related Laws

• Victim Burden Inversion: harmed nodes carry the burden of correction.
• Capacity-Inverting Restoration: repair consumes the capacity of the node needing repair.
• Exported Economic Incoherence: burden is shifted outside the source boundary.
• Parasitic Extraction: value or capacity is drawn from affected nodes.
• Pseudo-Restoration: repair pathway appears restorative without relief.
• Insight Without Load Reduction: affected nodes generate understanding without load reduction.
• Process Inflation: repair process grows as burden remains.
• Conditional Coercive Delivery: repair is conditional on affected-node compliance.
• Coercive Contract: remedy requires waivers or constrained agreement.
• Under-Resourced Justice: remedy pathways lack adequate source-funded capacity.
• Hidden Debt Accumulation: externalized repair stores future cost.
• Auditability Collapse: burden transfer becomes hard to trace.

Related Invariants

• Repair Burden Must Follow Causal Responsibility: source-created burden requires source-carried repair.
• Affected Nodes Must Not Carry the Repair Debt Alone: harmed nodes should not fund or manage restoration by default.
• Proof Must Not Become Punishment: evidence requirements must not intensify harm.
• Restoration Must Reduce Affected-Node Load: repair pathways must relieve, not add burden.
• Repair Responsibility Must Remain Attached to Source: accountability cannot be outsourced to the harmed node.
• Externalized Repair Must Be Accounted: all repair work must be visible in the ledger.
• Redress Must Not Require Further Extraction: remedy cannot depend on extracting more capacity from affected nodes.

10. Common False Positives

Not every affected-node participation requirement is Repair Burden Externalization.

Common false positives include:

• Affected-node input requested once and supported.
• Documentation required for accurate repair and kept minimal.
• Participation chosen by affected nodes.
• Claim process with direct assistance and compensation.
• Repair pathway initiated by the responsible node.
• Evidence standards proportional to uncertainty.
• Testimony protected, bounded, and not repetitive.
• Community-led repair fully resourced by the responsible system.
• Appeals designed to be low-burden and accessible.
• Repair process that reduces load more than it requires effort.
• Shared repair where responsibility, power, and resources are distributed coherently.
• Temporary affected-node involvement paired with immediate relief.

Clarifying rule:

This is not Repair Burden Externalization unless the work, cost, proof, coordination, risk, time, explanation, or restoration responsibility required to repair harm is shifted disproportionately away from the source of burden and onto affected or lower-power nodes.

11. Common False Repairs

Common false repairs include:

• simplifying forms while preserving affected-node initiation
• offering guidance pages instead of direct repair support
• creating help desks without authority
• reducing proof requirements slightly while keeping proof burden excessive
• offering reimbursement after affected nodes front costs
• creating support groups instead of source-funded repair
• requiring affected nodes to co-design repair without compensation
• automating claim intake without increasing resolution
• adding advocates without reducing administrative load
• calling unpaid affected-node labor participation
• asking for more testimony to improve future repair
• giving symbolic recognition for the burden of seeking repair
• shifting repair to charities, volunteers, or families
• extending deadlines while keeping the same burden
• treating non-completion as lack of need

False repair often produces the loop:

externalized repair burden exposed → pathway guidance improved → affected node still carries repair

Another common loop is:

affected node cannot complete repair process → case closed → system records no repair need

The repair fails because it preserves the burden allocation.

12. Restoration Direction

Restoration requires reattaching repair work to causal responsibility, reducing affected-node load, transferring resources toward the burdened node, simplifying redress paths, and accounting for the debt created by externalized repair.

Primary restoration direction:

reattach repair responsibility,
reduce affected-node load,
transfer repair resources,
and account for externalized burden

A fuller restoration path includes:

1. Name the original burden. Identify the harm, debt, error, extraction, failure, or unmet obligation.
2. Name the repair pathway. Identify how repair is currently accessed.
3. Map repair work. Determine who initiates, proves, documents, coordinates, pays, waits, risks, and completes repair.
4. Identify causal responsibility. Determine which node created or controls the burden.
5. Measure affected-node repair load. Quantify time, proof, cost, risk, emotional labor, administrative burden, and delay.
6. Reduce proof burden. Use source-held evidence, presumptive eligibility, or automatic repair where possible.
7. Shift initiation to responsible nodes. Make repair source-initiated when harm is known.
8. Transfer resources. Move funding, staffing, support, authority, or compensation toward affected nodes.
9. Simplify redress paths. Remove unnecessary steps, forms, retellings, and appeals.
10. Compensate repair labor. Account for time and cost spent seeking repair.
11. Protect affected nodes. Prevent retaliation, exposure, or repeated harm during repair.
12. Restore standing. Give affected nodes authority to validate whether repair worked.
13. Audit non-completion. Treat abandoned claims as possible pathway failure, not absence of need.
14. Repair externalized debt. Address the extra burden created by the repair path itself.
15. Validate load reduction. Confirm affected-node burden actually decreases.

A valid restoration path should reduce:

proof burden
administrative load
affected-node repair labor
waiting cost
source responsibility diffusion
unrepaired claims
redress friction
externalized repair debt
H

Repair Burden Externalization is not repaired by making affected nodes better at carrying the burden.

It is repaired by moving the burden back where responsibility belongs.

13. Cross-Module Links

• False Repair: Core failure where the repair pathway becomes additional burden.
• Restoration: Repair must reduce affected-node load rather than require affected-node self-restoration.
• Justice: Remedy fails when harmed nodes must carry proof, procedure, risk, and cost alone.
• Contracts: Waivers, claim procedures, arbitration, and terms can externalize repair burden.
• Economy: Repair burden is often exported as unpaid labor, administrative cost, or future debt.
• Cybernetics: Feedback and correction fail when affected nodes cannot carry reporting burden.
• Security: Breach recovery, identity repair, and incident reporting often push repair work onto victims.
• AI Governance: Users may be forced to identify, explain, appeal, correct, or absorb AI harms without source-carried repair capacity.
• Interfaces: Forms, portals, appeals, and support flows determine whether repair is accessible or externalized.
• Coherence: Coherent restoration requires burden reduction for the node that was burdened.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-RX-005 — Victim Burden Inversion
• FM-RX-004 — Capacity-Inverting Restoration
• FM-ECO-011 — Exported Economic Incoherence
• FM-C-021 — Parasitic Extraction
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related False Repair modes include:

• FM-R-001 — Cosmetic Restoration
• FM-R-002 — Process Inflation
• FM-R-003 — Insight Without Load Reduction
• FM-R-005 — Stabilization Freeze
• FM-R-006 — Repair as Compliance
• FM-R-007 — Repair Suppression via Efficiency
• FM-R-008 — Audit Evasion in Repair
• FM-R-009 — Therapeutic Capture
• FM-R-010 — Infinite Repair Loop

Related cross-family modes include:

• FM-RX-004 — Capacity-Inverting Restoration
• FM-RX-005 — Victim Burden Inversion
• FM-RX-009 — Repair Through Suppressed Auditability
• FM-ECO-011 — Exported Economic Incoherence
• FM-ECO-013 — Conditional Coercive Delivery
• FM-ECO-023 — Asymmetric Bandwidth
• FM-ECO-028 — Repair Starvation
• FM-C-021 — Parasitic Extraction
• FM-JC-004 — Under-Resourced Justice
• FM-JC-007 — Manufactured Consent
• FM-JC-010 — Proxy-Relay Obfuscation
• FM-SEC-007 — Silent Extraction / Parasitic Coupling

Aliases preserved from source material:

• Repair Burden Externalization
• Externalized Repair Burden
• Repair Cost Shifting
• Restoration Burden Transfer
• Burdened-Node Repair Load
• Affected-Node Repair Burden
• Proof Burden Externalization
• Repair Work Offloading
• Restoration Responsibility Displacement
• Victim Repair Load

15. Minimal Entry Version

Definition: Repair Burden Externalization occurs when the work, cost, proof, coordination, emotional load, administrative labor, risk, time, explanation, or restoration responsibility required to repair harm is shifted away from the source of burden and onto affected nodes, downstream systems, lower-power actors, volunteers, future budgets, or the wider field.

Signature:

repair pathway present
affected-node admin load↑
proof burden↑
source responsibility↓
repair completion↓
H↑

Restoration direction:

• name the original burden
• name the repair pathway
• map repair work
• identify causal responsibility
• measure affected-node repair load
• reduce proof burden
• shift initiation to responsible nodes
• transfer resources
• simplify redress paths
• compensate repair labor
• protect affected nodes
• restore standing
• audit non-completion
• repair externalized debt
• validate load reduction

16. Machine-Readable Summary

failure_mode:
  id: "FM-R-004"
  name: "Repair Burden Externalization"
  family: "False Repair"
  production_treatment: "Standalone Entry"
  parent_modes:
    - "FM-RX-005 — Victim Burden Inversion"
    - "FM-RX-004 — Capacity-Inverting Restoration"
    - "FM-ECO-011 — Exported Economic Incoherence"
    - "FM-C-021 — Parasitic Extraction"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "The work, cost, proof, coordination, risk, time, explanation, or restoration responsibility required to repair harm is shifted disproportionately away from the source of burden and onto affected or lower-power nodes."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-R-004"
  scope_note: "Conceptual and systems-oriented; does not treat participation, testimony, feedback, documentation, self-advocacy, claim submission, local coordination, affected-node input, or shared repair as inherently failed."
  aliases:
    - "Repair Burden Externalization"
    - "Externalized Repair Burden"
    - "Repair Cost Shifting"
    - "Restoration Burden Transfer"
    - "Burdened-Node Repair Load"
    - "Affected-Node Repair Burden"
    - "Proof Burden Externalization"
    - "Repair Work Offloading"
    - "Restoration Responsibility Displacement"
    - "Victim Repair Load"
  signature:
    - "repair pathway present"
    - "affected-node admin load↑"
    - "proof burden↑"
    - "source responsibility↓"
    - "repair completion↓"
    - "H↑"
  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:
      - "U1 — Power"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
      - "U8 — Environment"
  state_variables:
    - "R"
    - "H"
    - "K"
    - "Φ"
    - "BΣ"
    - "Au"
    - "Γ"
    - "Ψ"
    - "Λ"
    - "O"
    - "G"
    - "D"
    - "Τ"
  first_gate_failure: "Repair Responsibility Gate"
  restoration:
    - "Repair Burden Audit"
    - "Causal Responsibility Reattachment"
    - "Affected-Node Load Reduction"
    - "Proof Burden Reduction"
    - "Repair Resource Transfer"
    - "Administrative Load Removal"
    - "Redress Path Simplification"
    - "Hidden Repair Debt Accounting"
    - "Standing Restoration"
    - "Local Coherence Restoration"