0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat every limit, scarcity, conservation, budget constraint, delay, prioritization, or rationing event as failure. Systems cannot deliver everything everywhere at once. Some restraint is necessary. Some demand is invalid. Some delay is coherent when it is visible, consent-aware, time-bounded, and repair-linked.

The failure begins when actual need is under-supplied.

The issue is not finite resources.

The issue is delivery below coherence threshold.

Under-Delivery occurs when the system delivers less than what is needed for a node, function, relation, repair, or field to remain coherent.

1. Definition

Under-delivery occurs when a system, node, field, institution, economy, interface, or restoration process receives less resource, support, signal, care, value, timing, flow, repair, or capacity than is required to sustain coherence, complete function, preserve agency, or restore affected-state integrity.

The missing delivery may involve:

• money
• time
• attention
• care
• labor
• food
• housing
• tools
• signal
• bandwidth
• trust
• authority
• information
• repair capacity
• maintenance
• protection
• infrastructure
• social support
• interpretation
• medical or biological capacity
• technical support
• justice resources
• restoration resources

The core failure is:

need exists
delivery < need
load remains
local coherence↓
H↑

Under-Delivery is not merely low quantity.

It is insufficiency relative to the actual coherence requirement of the receiving node.

2. Core Pattern

The core pattern is:

1. A node, system, field, function, or repair process requires delivery.
2. The required delivery is under-measured, underfunded, delayed, minimized, misread, rationed, or denied.
3. The receiving node continues to carry load.
4. The system interprets continued operation as evidence that delivery is adequate.
5. The deficit becomes normalized.
6. The affected node compensates through hidden labor, depletion, waiting, adaptation, borrowing, self-suppression, or reduced function.
7. The under-delivery is framed as efficiency, scarcity, discipline, market reality, low priority, resilience, or reduced need.
8. Hidden debt accumulates.
9. Restoration becomes more expensive because the deficit compounds.
10. Collapse appears later as burnout, failure, instability, exit, legitimacy loss, or repair demand.

This failure mode often appears as:

they are still functioning, so they must have enough

or:

the budget is balanced, so delivery is adequate

or:

if the need were real, failure would already be visible

The restorative question is:

what delivery does this node actually need to remain coherent?

Need is measured by coherence requirement, not by what the system prefers to provide.

3. Failure Signature

Typical signature:

need↑
delivery↓ relative to need
compensatory burden↑
local coherence↓
repair latency↑
H↑

Extended signature:

resources arrive below threshold
support exists but is insufficient
care is symbolic but not load-reducing
repair is promised but under-resourced
function continues by depletion
budgets look controlled while need compounds

Common forms include:

underfunded repair programs
understaffed support systems
security teams without investigation capacity
AI governance without review capacity
justice systems without enough case depth
health systems providing contact but not sufficient care
infrastructure maintained below real load
communities receiving symbolic aid below recovery threshold
economies extracting from regions while under-delivering reinvestment
interfaces giving users information without usable action pathways

The defining condition is not that delivery is imperfect.

The defining condition is that delivery remains below the threshold required for the receiving state to become or remain coherent.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: resources are withheld, misallocated, extracted, rationed, or subordinated to higher-power claims.
• U2 — Configuration / Boundaries: delivery pathways do not reach the affected node or define need too narrowly.
• U3 — Execution / Runtime: actual delivery fails, is delayed, or arrives in unusable form.
• U4 — Information / Truth: reported delivery substitutes for adequate delivery.
• U5 — Coordination / Time: delivery arrives too late, too intermittently, or without continuity.
• U6 — Coherence Field: symbolic support creates the feeling that delivery occurred.
• U7 — Memory / Recurrence: chronic under-delivery becomes normalized as baseline.
• U8 — Environment / Field: field-level scarcity, extraction, or circulation failure prevents local sufficiency.

Common manifestation layers:

• U1 — Budgets: delivery is underfunded.
• U2 — Boundaries: need is scoped out.
• U3 — Execution: support does not arrive sufficiently.
• U4 — Truth: delivery claims replace delivery reality.
• U5 — Time: delay compounds cost.
• U6 — Coherence Field: symbolic provision masks deficit.
• U7 — Memory: under-supply becomes normal.

Under-Delivery is primarily a U1 / U3 resource-flow failure.

The system does not move enough usable capacity to where need exists.

5. Typical Development Sequence

A common development sequence is:

1. Need appears.
2. The system acknowledges some portion of need.
3. Delivery is designed below the true requirement.
4. The affected node receives partial support.
5. The system observes that failure has not yet fully manifested.
6. Partial delivery is treated as adequate.
7. The affected node compensates.
8. Compensation becomes invisible.
9. The delivery level becomes the new baseline.
10. Hidden debt grows.
11. The affected node’s capacity declines.
12. The system later faces a larger failure than the original delivery gap.

The loop often looks like:

need → partial delivery → compensation → apparent adequacy → chronic deficit

Another common loop is:

under-delivery creates burden → burden reduces voice → reduced voice lowers perceived need

Under-Delivery becomes self-reinforcing when the burdened node loses the capacity to signal the full deficit.

6. Diagnostic Markers

Diagnostic markers include:

• Support exists but does not reduce load.
• Delivery is counted by amount sent rather than need met.
• Affected nodes continue carrying the same burden after delivery.
• The system measures budget compliance instead of coherence restoration.
• Repair demand persists after support is provided.
• Users, teams, or communities compensate through hidden labor.
• Delivery is intermittent where continuity is required.
• Resources arrive in a form the receiving node cannot use.
• Need is reduced on paper after partial delivery.
• Delivery claims improve while local coherence declines.
• Waiting becomes normalized.
• Under-supplied nodes become quieter because signaling costs too much.
• Future cost rises because present delivery is inadequate.
• Restoration requires more later because under-delivery continued too long.
• The system cannot name the threshold for adequate delivery.

Useful diagnostics:

• Delivery Adequacy: Measures delivery relative to actual need.
• Resource Flow Integrity: Tests whether resource reaches the intended node.
• Need / Supply Fit: Compares supplied form, amount, timing, and usability to need.
• Affected-Node Burden: Measures remaining load after delivery.
• Restoration Capacity: Tests whether delivery enables repair.
• Latency: Measures delay between need and support.
• Hidden Debt: Tracks compounded under-supply cost.
• Auditability: Determines whether under-delivery can be traced.
• Local Coherence: Measures whether the receiving node stabilizes.
• Load Reduction: Tests whether delivery reduces burden.

7. Related Gates

Relevant gates include:

• Delivery Gate: Fails when delivery does not meet need.
• Resource Flow Gate: Fails when capacity does not reach the affected node.
• Need Gate: Fails when need is under-recognized or mismeasured.
• Capacity Gate: Fails when delivery capacity is insufficient.
• Timing Gate: Fails when delivery arrives too late or discontinuously.
• Compatibility Gate: Fails when delivered form does not fit the need.
• Restoration Gate: Fails when delivery does not enable repair.
• Auditability Gate: Fails when deficits cannot be traced.

The first common gate failure is usually the Delivery Gate.

The system sends less than the state requires.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; determines whether capacity moves to need.
• K — Constraint / Load: Remains high when delivery is insufficient.
• R — Restoration Capacity: Declines when support is below repair threshold.
• H — Hidden Debt: Accumulates through unmet need and compensatory burden.
• O — Coherence: Falls locally even when system-level metrics look stable.
• BΣ — Boundary Integrity: Determines whether the affected node is included in delivery accounting.
• Ψ — Observation / Interface: Reveals or hides need and delivery status.
• Au — Auditability: Determines whether deficit can be traced.
• Γ — Selection: Selects which needs receive resources.
• Λ — Compatibility: Tests whether delivered form fits receiving state.
• Τ — Trajectory / Time: Reveals compounding cost across delay.
• D — Damping: Can buffer under-delivery temporarily.
• G — Gain: Can amplify demand, urgency, or extraction without increasing usable delivery.

Common operator pattern:

need appears
Γ under-selects the node
Φ delivers below threshold
Λ fit is partial
K remains high
R cannot activate repair
Ψ sees continued operation
O is overestimated
H accumulates
Τ reveals larger future cost

The core operator inversion is:

some delivery → sufficient delivery

instead of:

delivery → need fit audit → load reduction → coherence validation

Under-Delivery turns partial provision into false sufficiency.

9. Related Laws and Invariants

Related Laws

• Hidden Debt Accumulation: unmet need becomes deferred cost.
• Restoration Starvation: repair cannot occur because capacity is insufficient.
• Zero-Slack Collapse: receiving nodes lose reserve under chronic under-supply.
• Capacity Collapse / Control Impossibility: support capacity falls below demand.
• Economic Leakiness: resources fail to remain available where needed.
• Mis-Targeting: delivery does not reach the correct node or need.
• Late Delivery: support arrives after cost has compounded.
• Phase Failure: delivery arrives in the wrong phase.
• Under-Resourced Justice: justice fails when repair and enforcement capacity are inadequate.
• Pseudo-Coherence: system-level stability masks local under-supply.

Related Invariants

• Delivery Must Meet Need: delivery is judged against coherence requirement.
• Resources Must Reach the Affected Node: delivery that misses the node is not adequate.
• Support Must Arrive in Usable Form: form matters as much as amount.
• Repair Requires Adequate Capacity: restoration cannot proceed below capacity threshold.
• Circulation Must Preserve Local Coherence: flows must sustain the nodes they depend on.
• Under-Supply Must Remain Auditable: deficits must be visible and traceable.
• Need Must Not Be Reframed as Excess Demand: unmet need cannot be dismissed because delivery is inconvenient.

10. Common False Positives

Not every reduced delivery is Under-Delivery.

Common false positives include:

• Reduced delivery after need genuinely declines.
• Temporary rationing with visible accounting and recovery plan.
• Delivery limits that preserve broader system coherence without hiding cost.
• Partial support clearly labeled as partial.
• Low delivery where the receiving node has sufficient reserve.
• Delayed delivery that remains within the need window.
• Resource conservation that does not increase affected-node burden.
• Support redirected after accurate need reassessment.
• Minimal delivery that is actually sufficient for the state.
• Systems that explicitly track unmet need and repair it later.

Clarifying rule:

This is not Under-Delivery unless delivery of resource, support, signal, value, care, timing, repair, or capacity falls below the threshold required by the receiving node or field while the resulting burden, risk, or hidden debt remains insufficiently repaired or accounted.

11. Common False Repairs

Common false repairs include:

• announcing support without increasing usable delivery
• delivering symbolic aid
• sending resources in unusable form
• counting allocated budget as delivered support
• increasing reporting requirements on under-supplied nodes
• treating waiting as demand management
• blaming the affected node for not thriving under deficit
• delivering once where continuity is required
• sending support too late and calling it adequate
• reducing the definition of need
• using averages to hide local under-supply
• offering advice instead of capacity
• shifting repair burden to the under-served node
• using scarcity language to avoid audit

False repair often produces the loop:

under-delivery exposed → symbolic support sent → delivery claimed → burden persists

Another common loop is:

need remains → node compensates → compensation hides need → delivery remains low

The repair fails because it improves the appearance of delivery without meeting the coherence requirement.

12. Restoration Direction

Restoration requires measuring real need, delivering adequate usable capacity to the affected node, reducing compensatory burden, and accounting for debt created by prior under-delivery.

Primary restoration direction:

measure real need,
route usable resources,
reduce carried load,
and repair under-supply debt

A fuller restoration path includes:

1. Name the under-delivered need. Identify what resource, support, signal, value, care, timing, repair, or capacity is missing.
2. Name the receiving node. Identify who or what is carrying the deficit.
3. Measure actual requirement. Determine delivery threshold for coherence, function, agency, or repair.
4. Audit current delivery. Measure amount, timing, form, usability, continuity, and access.
5. Compare delivery to need. Identify the specific deficit.
6. Measure compensatory burden. Identify hidden labor, depletion, waiting, risk, and repair delay.
7. Route usable capacity. Deliver resources in the form and timing the node can use.
8. Protect delivery pathway. Prevent leakage, blockage, extraction, or mis-targeting.
9. Reduce carried load. Confirm delivery lowers burden.
10. Repair under-supply debt. Address damage caused by prior deficit.
11. Install adequacy monitoring. Track whether delivery remains sufficient over time.
12. Recalibrate selection. Ensure future needs are not under-selected.
13. Validate local coherence. Confirm the receiving node stabilizes.
14. Update resource logic. Use need-fit, not merely budget-fit, as the delivery standard.

A valid restoration path should reduce:

unmet need
compensatory burden
repair latency
resource mismatch
delivery gap
hidden debt
local incoherence
waiting cost
support theater

Under-Delivery is not repaired by sending something.

It is repaired by delivering enough of the right thing to reduce the real load.

13. Cross-Module Links

• Economy: Core economic circulation failure; resources do not reach need at adequate amount, time, or form.
• Diagnostics: Requires delivery-adequacy, resource-flow, need/supply-fit, affected-node-burden, and local-coherence diagnostics.
• Restoration: Repair fails when affected nodes receive less than required for real restoration.
• Justice: Under-resourced justice produces procedural action without adequate repair or enforcement capacity.
• Cybernetics: Under-delivery reduces damping, slack, control capacity, and restoration capacity.
• Scaling: Scale can hide local under-delivery behind aggregate delivery statistics.
• Security: Security systems under-deliver investigation, patching, monitoring, or user support while claiming protection.
• AI Governance: AI governance under-delivers review, context, red-team capacity, user recourse, or harm repair.
• Interfaces: Interfaces may provide information without usable action capacity.
• Coherence: Coherence declines where needed resources do not arrive.

14. Relationship to Parent / Child Modes

Production treatment: Canon / Economy Parent

This mode maps upward to:

• FM-CORE-002 — Hidden Debt Accumulation
• FM-S-006 — Restoration Starvation
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-CORE-001 — Pseudo-Coherence

Sibling or related Economy modes include:

• FM-ECO-002 — Over-Delivery
• FM-ECO-003 — Mis-Targeting
• FM-ECO-004 — Stasis / Blockage
• FM-ECO-005 — Economic Leakiness
• FM-ECO-006 — Shunting / Bypass
• FM-ECO-007 — Phase Failure
• FM-ECO-010 — Expansion Without Capacity
• FM-ECO-011 — Exported Economic Incoherence
• FM-ECOX-004 — Late Delivery
• FM-ECOX-025 — Repair Starvation

Related cross-family modes include:

• FM-S-006 — Restoration Starvation
• FM-S-015 — Bandwidth Saturation
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-JC-004 — Under-Resourced Justice
• FM-R-004 — Repair Burden Externalization
• FM-R-007 — Repair Suppression via Efficiency
• FM-RX-004 — Capacity-Inverting Restoration
• FM-BIOX-005 — Energy-First Compression
• FM-M-007 — Aging Without Restoration

Aliases preserved from source material:

• Under-Delivery
• Insufficient Delivery
• Resource Under-Supply
• Support Under-Supply
• Delivery Deficit
• Repair Under-Delivery
• Capacity Under-Delivery
• Flow Deficit
• Insufficient Circulation
• Unmet Delivery Need

15. Minimal Entry Version

Definition: Under-delivery occurs when a system, node, field, institution, economy, interface, or restoration process receives less resource, support, signal, care, value, timing, flow, repair, or capacity than is required to sustain coherence, complete function, preserve agency, or restore affected-state integrity.

Signature:

need↑
delivery↓ relative to need
compensatory burden↑
local coherence↓
repair latency↑
H↑

Restoration direction:

• name the under-delivered need
• name the receiving node
• measure actual requirement
• audit current delivery
• compare delivery to need
• measure compensatory burden
• route usable capacity
• protect delivery pathway
• reduce carried load
• repair under-supply debt
• install adequacy monitoring
• recalibrate selection
• validate local coherence
• update resource logic

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-001"
  name: "Under-Delivery"
  family: "Economy"
  production_treatment: "Canon / Economy Parent"
  parent_modes:
    - "FM-CORE-002 — Hidden Debt Accumulation"
    - "FM-S-006 — Restoration Starvation"
    - "FM-C-011 — Zero-Slack Collapse"
  primary_failure: "Delivery of resource, support, signal, value, care, timing, repair, or capacity falls below the threshold required by the receiving node or field while the resulting burden, risk, or hidden debt remains insufficiently repaired or accounted."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-001"
  scope_note: "Conceptual and systems-oriented; does not treat every limit, scarcity, conservation, budget constraint, delay, prioritization, or rationing event as failure."
  aliases:
    - "Under-Delivery"
    - "Insufficient Delivery"
    - "Resource Under-Supply"
    - "Support Under-Supply"
    - "Delivery Deficit"
    - "Repair Under-Delivery"
    - "Capacity Under-Delivery"
    - "Flow Deficit"
    - "Insufficient Circulation"
    - "Unmet Delivery Need"
  signature:
    - "need↑"
    - "delivery↓ relative to need"
    - "compensatory burden↑"
    - "local coherence↓"
    - "repair latency↑"
    - "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 — Budgets"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Coherence Field"
      - "U7 — Memory"
  state_variables:
    - "Φ"
    - "K"
    - "R"
    - "H"
    - "O"
    - "BΣ"
    - "Ψ"
    - "Au"
    - "Γ"
    - "Λ"
    - "Τ"
    - "D"
    - "G"
  first_gate_failure: "Delivery Gate"
  restoration:
    - "Delivery Adequacy Restoration"
    - "Resource Flow Repair"
    - "Affected-Node Need Audit"
    - "Capacity Rebuild"
    - "Timing Recalibration"
    - "Repair Resource Routing"
    - "Hidden Debt Accounting"
    - "Local Coherence Restoration"
    - "Under-Supply Correction"