0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat every delayed repair, temporary maintenance backlog, funding constraint, triage choice, phased repair plan, or resource prioritization decision as inherently failed.

Repair sometimes must be sequenced.

Maintenance may be phased.

Restoration may require timing, readiness, and capacity alignment.

Repair allocation can be coherent when it is:

• visible
• funded
• prioritized by burden
• time-bounded
• affected-node aware
• capacity-matched
• not indefinitely deferred
• auditable
• paired with debt accounting
• connected to actual restoration
• scaled with system growth
• protected from extraction pressure

The failure begins when repair is starved.

The issue is not that every repair happens immediately.

The issue is the system continuing to operate while underfunding the repair that operation requires.

Repair Starvation occurs when the economy treats maintenance and restoration as optional, secondary, or postponable until the debt becomes structural.

1. Definition

Repair Starvation occurs when economic systems allocate insufficient resource, time, labor, authority, funding, attention, slack, legitimacy, or operational capacity to maintenance, restoration, debt reduction, harm repair, infrastructure renewal, affected-node recovery, or correction pathways, causing unresolved burdens to compound beneath continued operation.

The starved repair may involve:

• infrastructure maintenance
• worker recovery
• customer support
• affected-node compensation
• legal remedy
• technical debt reduction
• environmental restoration
• community repair
• service correction
• safety remediation
• accessibility repair
• data correction
• platform appeal
• AI redress
• security patching
• debt discharge
• claims processing
• backlog reduction
• equipment replacement
• trust rebuilding
• governance repair
• documentation repair
• training and capacity restoration
• support staffing

The core failure is:

repair need↑
R capacity↓ / insufficient
operation continues
H↑
future viability↓

Repair Starvation is not merely underfunding.

It is underfunding or under-capacitating the processes that prevent accumulated burden from becoming system debt.

2. Core Pattern

The core pattern is:

1. A system produces wear, harm, backlog, debt, maintenance demand, or affected-node burden.
2. Repair capacity is required to keep the system coherent.
3. Repair is treated as cost, delay, overhead, inefficiency, liability, reputational risk, or future work.
4. Resources continue flowing to operation, growth, extraction, optics, or new commitments.
5. Repair queues age.
6. Maintenance and restoration needs compound.
7. Affected nodes adapt, degrade, exit, or carry unresolved burden.
8. The system continues appearing functional.
9. Hidden debt accumulates beneath operation.
10. Restoration requires making repair a first-class economic flow.

This failure often appears as:

we cannot afford repair right now

while the hidden truth may be:

the system cannot afford not to repair

or:

repair will happen after growth

while the overlooked condition is:

growth is increasing the repair burden faster than repair capacity grows

The restorative question is:

what repair flow is missing from the true cost of operation?

Repair Starvation turns maintenance debt into invisible financing.

3. Failure Signature

Typical signature:

repair need↑
R↓
maintenance backlog↑
repair latency↑
affected-node recovery↓
H↑

Extended signature:

growth funded while maintenance is deferred
profit protected while claims remain unresolved
support demand rises while support staffing stays flat
infrastructure expands while renewal budgets shrink
AI deployment grows while appeal and correction capacity lag
security exposure rises while patching queues age
settlement closes while affected-node repair remains unfunded

Common forms include:

a company scales users while support and safety repair remain underfunded
a city expands infrastructure while maintenance backlog grows
a platform profits from user activity while appeals and corrections are understaffed
a healthcare system increases throughput while worker recovery and patient navigation support collapse
a supply chain grows while supplier repair and resilience are unfunded
an organization logs audit findings but does not fund remediation
an AI system deploys broadly while redress, memory correction, and user harm review remain insufficient
a justice program announces reform while compensation and remedy pathways are starved

The defining condition is not that repair is incomplete.

The defining condition is that repair capacity is persistently lower than repair burden while the system continues claiming economic continuity.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: funding, profit, austerity, growth, or political incentives deprioritize repair.
• U2 — Configuration / Boundaries: repair obligations are excluded from operating cost, budget categories, contracts, or accountability boundaries.
• U3 — Execution / Runtime: maintenance, support, redress, and correction teams lack capacity.
• U4 — Information / Truth: repair backlog visibility substitutes for repair completion or is hidden entirely.
• U5 — Coordination / Time: repair windows are missed; deferred burden compounds.
• U6 — Coherence Field: continued operation creates the feeling that repair is not urgent.
• U7 — Memory / Recurrence: chronic under-repair becomes normal.
• U8 — Environment / Field: competitive, market, political, or institutional pressure rewards visible output over restoration.

Common manifestation layers:

• U1 — Power: budgets flow away from repair.
• U2 — Boundaries: repair cost is kept outside core accounting.
• U3 — Execution: repair pathways saturate.
• U4 — Truth: backlog is hidden or normalized.
• U5 — Time: delay compounds debt.
• U6 — Field: operation masks damage.
• U7 — Memory: repair starvation becomes baseline.

Repair Starvation is primarily a U1 budget / R restoration-capacity failure.

The system funds continuation while underfunding restoration.

5. Typical Development Sequence

A common development sequence is:

1. Operation creates maintenance, support, correction, harm, or restoration needs.
2. Repair demand is visible or partially visible.
3. Repair is categorized as overhead, liability, delay, non-core cost, or future work.
4. Budget, staffing, authority, or attention goes to expansion, extraction, optics, or immediate output.
5. Repair backlog grows.
6. Affected nodes carry unresolved burden.
7. The system continues to function because affected nodes adapt or hidden capacity absorbs damage.
8. Repair need becomes larger and more complex.
9. The system reports inability to repair because repair is now too expensive.
10. Continued under-repair creates deeper hidden debt.
11. Eventually operation itself becomes unstable.

The loop often looks like:

operation → wear / harm → repair deferred → hidden debt → higher repair cost → more deferral

Another common loop is:

growth priority → repair starvation → degraded service → more growth needed to cover debt

Repair Starvation becomes self-reinforcing when deferred repair makes future repair harder, more costly, and less politically attractive.

6. Diagnostic Markers

Diagnostic markers include:

• Repair queues grow faster than they clear.
• Maintenance budget falls relative to asset base or usage.
• Support workload rises without support capacity scaling.
• Backlogs are normalized as permanent.
• Claims, appeals, corrections, or remedies age beyond useful windows.
• Audit findings remain unresolved.
• Growth plans do not include proportional repair capacity.
• Affected nodes repeatedly carry the same unrepaired burden.
• “Efficiency” depends on not funding maintenance.
• Crisis response replaces routine repair.
• Repair workers are overloaded or unsupported.
• Hidden debt is visible in workarounds, attrition, distrust, rework, and local degradation.
• Restoration improves when repair is funded as core infrastructure rather than exceptional cost.

Useful diagnostics:

• Restoration Capacity: Measures the system’s ability to repair burden.
• Maintenance Capacity: Measures whether assets, relationships, infrastructure, and workflows can be sustained.
• Repair Backlog: Tracks unresolved restoration work.
• Hidden Debt: Measures deferred burden created by under-repair.
• Deferred Maintenance: Tracks aging and compounding repair needs.
• Repair Funding Fit: Tests whether funding matches repair burden.
• Affected-Node Recovery: Measures whether burdened nodes actually recover.
• Clearance Capacity: Tests whether repair queues can be discharged.
• Auditability: Determines whether repair obligations and delays can be traced.
• Local Coherence: Tests whether repair improves actual affected states.

7. Related Gates

Relevant gates include:

• Restoration Gate: Fails when repair capacity is insufficient.
• Maintenance Gate: Fails when upkeep is not funded or operationalized.
• Repair Capacity Gate: Fails when repair burden exceeds available resource.
• Hidden Debt Gate: Fails when unresolved burden is not counted.
• Budget Gate: Fails when resources exclude restoration needs.
• Clearance Gate: Fails when repair backlog cannot be discharged.
• Affected-Node Gate: Fails when harmed or burdened nodes lack recovery standing.
• Auditability Gate: Fails when repair debt cannot be traced.
• Local Coherence Gate: Fails when continued operation does not restore local states.

The first common gate failure is usually the Restoration Gate.

The system continues operating without verifying that repair capacity can carry the burden operation creates.

8. Related Operators

Relevant operators include:

• R — Restoration Capacity: Primary operator; insufficient repair capacity drives the failure.
• H — Hidden Debt: Accumulates as repair is deferred.
• Φ — Flow / Resource Movement: Determines whether resources move toward repair or away from it.
• K — Constraint / Load: Rises as unresolved burden compounds.
• Au — Auditability: Reveals repair obligations, queues, and delays.
• Τ — Trajectory / Time: Governs repair windows and debt compounding.
• D — Damping: Should slow growth or extraction when repair capacity is low.
• G — Gain: Often redirects resources toward growth, profit, output, or optics.
• O — Coherence: May appear high while operation continues.
• Ψ — Observation / Interface: Determines whether repair need is visible.
• BΣ — Boundary Integrity: Keeps repair obligation attached to the source of burden.
• Γ — Selection: Selects whether repair receives priority.
• Λ — Compatibility: Tests whether repair flow fits affected-node need.

Common operator pattern:

operation creates burden
R demand rises
Γ selects growth / continuity over repair
Φ bypasses restoration
K rises in affected nodes
H accumulates
O remains visible through continued operation
Au may show backlog but not force action
Τ compounds repair cost

The core operator inversion is:

operation continues → system is viable

instead of:

operation continues + repair capacity + hidden debt reduction + affected-node recovery → system is viable

Repair Starvation turns non-repair into hidden financing.

9. Related Laws and Invariants

Related Laws

• Restoration Starvation: primary parent mechanism.
• Hidden Debt Accumulation: unrepaired burden compounds.
• Late Delivery: repair arrives after valid windows.
• Clearance Failure: repair backlog cannot be discharged.
• Expansion Without Capacity: growth outruns repair capacity.
• Economic Over-Constriction: constraints block repair flow.
• Extraction Masking Instability: stability depends on repair being offloaded or deferred.
• Forced Profit: profit is preserved by withholding repair.
• Exported Economic Incoherence: repair burden is shifted elsewhere.
• Stasis / Blockage: repair pathways freeze.
• Capacity Collapse / Control Impossibility: repair load exceeds system control.
• Terminal Scaling Failure: under-repair becomes nonviable at scale.

Related Invariants

• Repair Capacity Must Scale with Burden: restoration must grow with operation, harm surface, and complexity.
• Maintenance Is Part of Delivery: delivery is incomplete without sustaining capacity.
• Growth Must Fund Repair: expansion must carry its restoration obligation.
• Hidden Debt Must Receive Resource: acknowledged debt requires actual repair flow.
• Restoration Cannot Be Optional Overhead: repair is a core viability function.
• Affected Nodes Require Repair Standing: burdened nodes must be able to trigger restoration.
• Operation Without Repair Converts Flow into Debt: continued activity without restoration compounds harm.

10. Common False Positives

Not every delayed or limited repair is Repair Starvation.

Common false positives include:

• Temporary repair backlog with active capacity scaling.
• Repair intentionally sequenced by urgency and phase.
• Maintenance deferred briefly with funded schedule.
• Triage that protects highest-need nodes.
• Repair paused to prevent greater harm.
• Resource constraints openly acknowledged with debt accounting.
• Repair burden lower than available restoration capacity.
• Growth paused until repair catches up.
• Affected nodes supported while waiting.
• Repair windows preserved despite delay.
• Backlogs decreasing faster than new repair needs.
• Restoration handled outside the visible budget but still fully resourced and auditable.

Clarifying rule:

This is not Repair Starvation unless repair, maintenance, restoration, correction, recovery, or debt reduction is persistently under-resourced relative to burden while continued operation, growth, extraction, or legitimacy claims proceed.

11. Common False Repairs

Common false repairs include:

• documenting repair needs without funding them
• creating repair dashboards while queues keep aging
• launching pilot repair programs that do not scale
• funding new growth to generate money for old repair
• assigning repair responsibility without authority
• asking affected nodes to self-repair
• treating volunteer labor as restoration capacity
• using symbolic apology instead of material repair
• creating complaint channels without resolution capacity
• outsourcing repair to underfunded intermediaries
• closing tickets administratively
• reclassifying maintenance as optional
• delaying repair until the next budget cycle repeatedly
• funding crisis repair while starving routine repair
• praising resilience instead of replenishing capacity

False repair often produces the loop:

repair starvation exposed → repair process created → no capacity added → backlog persists

Another common loop is:

repair delayed → harm worsens → repair becomes expensive → delay justified by cost

The repair fails because it creates repair appearance without repair capacity.

12. Restoration Direction

Restoration requires making repair obligations visible, resourcing restoration capacity, prioritizing hidden debt reduction, clearing repair backlogs, protecting affected-node recovery, and tying growth or extraction to repair funding.

Primary restoration direction:

resource repair,
clear hidden debt,
restore affected nodes,
and make maintenance core infrastructure

A fuller restoration path includes:

1. Name the repair burden. Identify maintenance, correction, harm repair, claims, appeals, support, infrastructure renewal, or affected-node recovery need.
2. Map repair sources. Determine what operation, growth, extraction, or policy created the burden.
3. Measure repair backlog. Track age, volume, severity, and affected nodes.
4. Measure restoration capacity. Compare staffing, funding, authority, tools, and time against repair demand.
5. Audit hidden debt. Identify deferred costs and compounding burdens.
6. Prioritize by viability and window. Repair what is most time-sensitive, harmful, or debt-producing first.
7. Fund repair as core flow. Allocate stable resources, not symbolic or residual funding.
8. Scale repair with operation. Tie growth, deployment, extraction, or expansion to proportional restoration capacity.
9. Clear stale backlogs honestly. Resolve, compensate, replace, or explicitly account for old burdens.
10. Restore affected-node standing. Give burdened nodes usable repair pathways.
11. Protect repair workers. Ensure restoration teams are not themselves overloaded.
12. Reduce new burden creation. Slow or redesign operations that generate unrepaired debt.
13. Install repair gates. Prevent continuation or expansion when repair debt exceeds thresholds.
14. Restore auditability. Track who created burden, who carries it, and what repair occurred.
15. Validate local coherence. Confirm affected nodes actually recover.

A valid restoration path should reduce:

repair backlog
maintenance debt
affected-node burden
restoration latency
hidden debt
deferred maintenance
support overload
repair starvation
H

Repair Starvation is not repaired by promising repair.

It is repaired by making restoration resourced, timely, and unavoidable.

13. Cross-Module Links

• Economy: Core failure of repair funding, maintenance capacity, restoration budgets, support staffing, and debt reduction.
• Restoration: Direct domain expression of restoration starvation in economic systems.
• Justice: Remedy, compensation, standing, and affected-node recovery fail when repair is starved.
• Scaling: Expansion increases repair surface; repair capacity must scale faster than burden.
• Cybernetics: Repair starvation creates delayed feedback, false stability, and eventual control failure.
• Diagnostics: Requires restoration-capacity, backlog-age, hidden-debt, repair-funding-fit, and local-coherence diagnostics.
• Security: Patching, incident remediation, access repair, and harm response require funded repair capacity.
• AI Governance: AI appeals, redress, memory correction, content correction, user harm review, and model remediation must be resourced.
• Infrastructure: Deferred maintenance and renewal debt become systemic risk.
• Coherence: Coherence requires the system to repair what it consumes, damages, or burdens.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression

This mode maps upward to:

• FM-S-006 — Restoration Starvation
• FM-CORE-002 — Hidden Debt Accumulation
• FM-ECO-015 — Clearance Failure
• FM-R-007 — Repair Suppression via Efficiency
• FM-C-013 — Capacity Collapse / Control Impossibility

Sibling or related Economy modes include:

• FM-ECO-001 — Under-Delivery
• FM-ECO-004 — Stasis / Blockage
• FM-ECO-010 — Expansion Without Capacity
• FM-ECO-012 — Late Delivery
• FM-ECO-014 — Economic Over-Constriction
• FM-ECO-015 — Clearance Failure
• FM-ECO-027 — Extraction Masking Instability
• FM-ECO-029 — Growth Theater
• FM-ECO-032 — Pseudo-Coherent Economic Stability

Related cross-family modes include:

• FM-S-006 — Restoration Starvation
• FM-S-010 — Hidden Debt Explosion
• FM-S-017 — Terminal Scaling Failure
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-C-026 — Cosmetic Reset
• FM-R-003 — Insight Without Load Reduction
• FM-R-004 — Repair Burden Externalization
• FM-R-007 — Repair Suppression via Efficiency
• FM-R-008 — Audit Evasion in Repair
• FM-R-010 — Infinite Repair Loop
• FM-JC-004 — Under-Resourced Justice

Aliases preserved from source material:

• Repair Starvation
• Economic Repair Starvation
• Restoration Starvation
• Maintenance Starvation
• Repair Underfunding
• Deferred Repair Spiral
• Restoration Capacity Starvation
• Maintenance Capacity Collapse
• Repair Debt Accumulation
• Correction Capacity Starvation

Legacy source preserved:

legacy_ids:
  - "FM-ECOX-025"
deprecated_source_ids:
  - "FM-ECOX-025"
source_aliases:
  - "Economy Extended Entry 025"

15. Minimal Entry Version

Definition: Repair Starvation occurs when economic systems allocate insufficient resource, time, labor, authority, funding, attention, slack, legitimacy, or operational capacity to maintenance, restoration, debt reduction, harm repair, infrastructure renewal, affected-node recovery, or correction pathways, causing unresolved burdens to compound beneath continued operation.

Signature:

repair need↑
R↓
maintenance backlog↑
repair latency↑
affected-node recovery↓
H↑

Restoration direction:

• name the repair burden
• map repair sources
• measure repair backlog
• measure restoration capacity
• audit hidden debt
• prioritize by viability and window
• fund repair as core flow
• scale repair with operation
• clear stale backlogs honestly
• restore affected-node standing
• protect repair workers
• reduce new burden creation
• install repair gates
• restore auditability
• validate local coherence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-028"
  name: "Repair Starvation"
  family: "Economy"
  production_treatment: "Domain Expression"
  legacy_ids:
    - "FM-ECOX-025"
  parent_modes:
    - "FM-S-006 — Restoration Starvation"
    - "FM-CORE-002 — Hidden Debt Accumulation"
    - "FM-ECO-015 — Clearance Failure"
    - "FM-R-007 — Repair Suppression via Efficiency"
    - "FM-C-013 — Capacity Collapse / Control Impossibility"
  primary_failure: "Repair, maintenance, restoration, correction, recovery, or debt reduction is persistently under-resourced relative to burden while continued operation, growth, extraction, or legitimacy claims proceed."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-028"
  deprecated_source_ids:
    - "FM-ECOX-025"
  scope_note: "Conceptual and systems-oriented; does not treat every delayed repair, temporary maintenance backlog, funding constraint, triage choice, phased repair plan, or resource prioritization decision as inherently failed."
  aliases:
    - "Repair Starvation"
    - "Economic Repair Starvation"
    - "Restoration Starvation"
    - "Maintenance Starvation"
    - "Repair Underfunding"
    - "Deferred Repair Spiral"
    - "Restoration Capacity Starvation"
    - "Maintenance Capacity Collapse"
    - "Repair Debt Accumulation"
    - "Correction Capacity Starvation"
  signature:
    - "repair need↑"
    - "R↓"
    - "maintenance backlog↑"
    - "repair latency↑"
    - "affected-node recovery↓"
    - "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"
      - "U7 — Memory"
  state_variables:
    - "R"
    - "H"
    - "Φ"
    - "K"
    - "Au"
    - "Τ"
    - "D"
    - "G"
    - "O"
    - "Ψ"
    - "BΣ"
    - "Γ"
    - "Λ"
  first_gate_failure: "Restoration Gate"
  restoration:
    - "Repair Capacity Audit"
    - "Maintenance Funding Restoration"
    - "Hidden Debt Accounting"
    - "Repair Backlog Triage"
    - "Restoration Capacity Scaling"
    - "Affected-Node Recovery Support"
    - "Deferred Maintenance Reduction"
    - "Budget Reallocation to Repair"
    - "Repair Standing Restoration"
    - "Local Coherence Restoration"