0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat all overhead, transaction cost, administration, mediation, infrastructure, translation, coordination, storage, taxation, governance, maintenance, or routing loss as inherently failed. Every flow has some cost. Delivery requires pathways. Repair often needs intermediaries, interpretation, logistics, and governance.

The failure begins when too much usable value disappears before arrival.

The issue is not transaction cost.

The issue is leakage that prevents delivery from becoming usable coherence.

Economic Leakiness occurs when the system confuses input volume with retained value.

1. Definition

Economic leakiness occurs when resource, value, attention, care, signal, legitimacy, authority, repair, or capacity enters a system or delivery pathway but dissipates, escapes, is extracted, is absorbed by overhead, is diverted, or loses usable form before reaching and sustaining the affected node.

The leaked flow may involve:

• money
• labor
• time
• care
• attention
• trust
• authority
• repair capacity
• data
• signal
• meaning
• logistics
• maintenance
• aid
• justice resources
• governance capacity
• security capacity
• AI review capacity
• institutional legitimacy
• community support
• technical capacity

The core failure is:

input flow enters
retained value↓
arrival at need↓
affected burden remains
H↑

Economic Leakiness is a circulation-integrity failure.

The system may have enough input in aggregate, but too little retained value reaches the point of need.

2. Core Pattern

The core pattern is:

1. A system identifies a need or delivery obligation.
2. Resource is allocated or enters the flow pathway.
3. The pathway contains leakage: overhead, extraction, friction, gatekeeping, delays, misrouting, conversion loss, corruption, administrative burden, interface loss, or boundary escape.
4. Each layer consumes, diverts, delays, or degrades part of the flow.
5. The affected node receives less usable value than the input suggests.
6. Delivery is counted by allocation, budget, effort, or gross flow.
7. The receiving node remains under-delivered.
8. The system is confused because resources appear to have been provided.
9. Hidden debt accumulates through the gap between input and arrival.
10. Restoration requires locating and sealing leakage or redesigning the pathway.

This failure mode often appears as:

we put enough resources into the system, so the need should be met

or:

the budget increased, so support increased

or:

the pathway is funded, so delivery is happening

The restorative question is:

how much usable value actually reaches the affected node?

Inputs are not outcomes.

Flow must survive the pathway.

3. Failure Signature

Typical signature:

input flow↑
pathway loss↑
retained value↓
affected-node arrival↓
delivery / outcome gap↑
H↑

Extended signature:

funds enter but repair does not arrive
attention enters but care is not felt
data enters but decision quality does not improve
authority enters but local action remains blocked
aid enters but overhead consumes it
capacity enters but support remains thin

Common forms include:

aid budgets consumed by administration before local delivery
security investment absorbed by tools instead of risk reduction
AI governance funding absorbed by optics, policy, or reporting while review capacity remains low
justice funding increasing procedure but not repair
health resources consumed by billing and coordination overhead
community support diluted through intermediaries
infrastructure budgets leaking through delays and contract layers
platform revenue not returning to user or creator coherence
restoration funds spent on management rather than load reduction
data pipelines losing meaning through aggregation and translation

The defining condition is not that some flow is consumed by the pathway.

The defining condition is that pathway loss prevents the flow from satisfying the need it was meant to serve.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: powerful intermediaries capture or consume flow before it reaches affected nodes.
• U2 — Configuration / Boundaries: pathways allow value to escape, fragment, or be absorbed by non-target layers.
• U3 — Execution / Runtime: delivery loses value through administrative, logistical, contractual, technical, or operational friction.
• U4 — Information / Truth: gross input is reported as net delivery.
• U5 — Coordination / Time: delay reduces value before arrival.
• U6 — Coherence Field: visible allocation creates the feeling that support exists.
• U7 — Memory / Recurrence: chronic leakage becomes normalized as unavoidable overhead.
• U8 — Environment / Field: field-scale extraction or infrastructure weakness causes distributed leakage.

Common manifestation layers:

• U1 — Budgets: flow is captured.
• U2 — Boundaries: value leaks across weak or extractive boundaries.
• U3 — Execution: friction consumes delivery.
• U4 — Truth: input metrics replace arrival metrics.
• U5 — Time: delay degrades value.
• U6 — Coherence Field: visible funding masks non-arrival.
• U8 — Environment: broad pathways dissipate value.

Economic Leakiness is primarily a U2 / U4 flow-accounting failure.

The system does not know how much of its flow remains usable at the point of need.

5. Typical Development Sequence

A common development sequence is:

1. Need is recognized.
2. Resource is allocated.
3. Delivery pathway is selected.
4. The pathway includes multiple layers.
5. Each layer consumes some value.
6. The system tracks input but not retained value.
7. The affected node receives insufficient support.
8. The system increases input.
9. Leakage scales with input.
10. Intermediaries become dependent on the flow.
11. The affected node remains burdened.
12. Hidden debt accumulates despite visible resource commitment.

The loop often looks like:

need → input allocated → pathway leakage → weak arrival → more input allocated

Another common loop is:

leakage exposed → reporting increases → overhead increases → leakage worsens

Economic Leakiness becomes self-reinforcing when the pathway benefits from larger flow even if the affected node does not.

6. Diagnostic Markers

Diagnostic markers include:

• Input increases but affected-node burden does not fall.
• Gross spending rises faster than usable delivery.
• Intermediary layers grow while local support remains thin.
• The system reports allocation rather than arrival.
• Administrative burden consumes repair capacity.
• Delivery is delayed until value decays.
• Resources arrive in reduced, distorted, or unusable form.
• The cost of accessing support absorbs the support.
• The pathway becomes more funded than the need.
• Affected nodes receive a small fraction of nominal value.
• Each reform creates more overhead.
• Flow is difficult to trace from source to arrival.
• Leakage is defended as necessary complexity.
• Restoration improves when pathways are shortened or sealed.
• The system cannot state net value delivered after leakage.

Useful diagnostics:

• Leakage Rate: Measures loss between input and arrival.
• Resource Flow Integrity: Tests whether flow survives the pathway.
• Value Retention: Measures usable value preserved across transfer.
• Delivery Adequacy: Tests whether arrival meets need.
• Overhead Load: Measures administrative, coordination, and process consumption.
• Extraction Load: Measures value captured by non-affected nodes.
• Affected-Node Arrival: Measures what actually reaches the burdened node.
• Hidden Debt: Tracks cost created by non-arrival.
• Auditability: Determines whether flow can be traced.
• Local Coherence: Tests whether arrival improves receiving state.

7. Related Gates

Relevant gates include:

• Leakage Gate: Fails when flow loses too much usable value before arrival.
• Resource Flow Gate: Fails when circulation does not preserve delivery value.
• Boundary Gate: Fails when value escapes through weak, porous, or extractive boundaries.
• Delivery Gate: Fails when net delivery does not meet need.
• Auditability Gate: Fails when leakage cannot be traced.
• Restoration Gate: Fails when repair value is consumed before reaching repair site.
• Extraction Gate: Fails when intermediaries capture value beyond coherent cost.
• Local Coherence Gate: Fails when gross input does not stabilize the receiving node.

The first common gate failure is usually the Leakage Gate.

The system sends value into a path that cannot retain it.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; determines how value moves and where it leaks.
• BΣ — Boundary Integrity: Determines whether flow is retained or lost across boundaries.
• Au — Auditability: Determines whether input, loss, and arrival can be traced.
• H — Hidden Debt: Accumulates through non-arrival and under-repair.
• K — Constraint / Load: Remains high at the affected node and may rise through access costs.
• R — Restoration Capacity: Is weakened when repair value leaks.
• Λ — Compatibility: Tests whether the pathway preserves usable form.
• Γ — Selection: Selects pathways and intermediaries.
• Ψ — Observation / Interface: Shows gross flow, net arrival, or obscures the difference.
• O — Coherence: May appear high through visible input.
• Τ — Trajectory / Time: Reveals decay and compounding non-arrival over time.
• D — Damping: May buffer leakage temporarily.
• G — Gain: Can increase input without reducing leakage.

Common operator pattern:

need appears
Φ sends resource into pathway
BΣ allows leakage across layers
Γ selects intermediaries
Ψ reports gross input
Au cannot trace net arrival
K remains high at affected node
R remains under-resourced
O appears improved upstream
H accumulates downstream

The core operator inversion is:

input allocated → value delivered

instead of:

input allocated → leakage audit → net arrival → burden reduction

Economic Leakiness turns gross flow into false support.

9. Related Laws and Invariants

Related Laws

• Hidden Debt Accumulation: non-arrival creates deferred burden.
• Parasitic Extraction: intermediaries may capture flow while source need remains.
• Under-Delivery: leakage produces insufficient arrival.
• Mis-Targeting: leakage may occur through wrong-target routing.
• Stasis / Blockage: blocked flow can create leakage through delay and overhead.
• Shunting / Bypass: resources may be diverted away from need.
• Auditability Collapse: leakage becomes untraceable.
• Boundary Collapse: value escapes through failed boundaries.
• Restoration Starvation: repair capacity leaks before reaching repair.
• Pseudo-Coherence: visible input creates apparent support.

Related Invariants

• Resource Flow Must Preserve Usable Value: delivery pathways must retain what matters.
• Delivery Must Account for Leakage: gross input is not net support.
• Value Must Reach the Affected Node: arrival, not allocation, validates delivery.
• Overhead Must Not Consume Repair: process cost must not outrun repair value.
• Leakage Must Remain Auditable: lost value must be traceable.
• Circulation Must Preserve Local Coherence: flow must improve receiving state.
• Extraction Must Not Hide as Transaction Cost: pathway consumption must be justified and bounded.

10. Common False Positives

Not every loss or overhead cost is Economic Leakiness.

Common false positives include:

• Necessary logistics that enable delivery.
• Administrative cost that improves targeting, safety, or accountability.
• Translation or mediation that preserves value.
• Storage loss within planned tolerance.
• Investment in infrastructure that increases future delivery.
• Coordination cost that prevents mis-targeting or over-delivery.
• Taxation or pooling that returns value coherently.
• Delayed delivery that preserves more value than immediate delivery.
• Intermediary cost that is transparent, bounded, and effective.
• Flow loss that does not reduce coherence at the affected node.

Clarifying rule:

This is not Economic Leakiness unless resource, value, signal, care, authority, repair, or capacity enters a pathway but loses enough usable value before arrival that the affected node remains under-served or hidden debt accumulates.

11. Common False Repairs

Common false repairs include:

• increasing gross input without sealing leakage
• adding more intermediaries to monitor intermediaries
• reporting allocation more clearly
• increasing overhead to prove accountability
• blaming affected nodes for not receiving value
• adding new programs through the same leaky pathway
• counting spending as impact
• renaming extraction as administration
• reducing direct delivery because it is harder to control
• increasing eligibility friction to reduce visible demand
• making dashboards for leakage without changing flow
• funding the pathway more than the need
• treating delayed arrival as adequate because input was high
• declaring success based on upstream effort

False repair often produces the loop:

need persists → input increases → leakage scales → need persists

Another common loop is:

leakage questioned → compliance overhead added → net delivery decreases → leakage worsens

The repair fails because it increases gross flow or process visibility without increasing net value arrival.

12. Restoration Direction

Restoration requires measuring net arrival, locating leakage points, reducing extractive or unnecessary pathway loss, protecting value through transfer, and verifying affected-node coherence.

Primary restoration direction:

trace flow,
measure leakage,
seal loss points,
and verify net arrival at need

A fuller restoration path includes:

1. Name the intended flow. Identify what resource, value, care, signal, authority, repair, or capacity is supposed to move.
2. Name the affected node. Identify where usable value must arrive.
3. Map the pathway. Trace every layer, intermediary, boundary, delay, conversion, and cost.
4. Measure gross input. Establish what enters the path.
5. Measure net arrival. Determine what reaches the affected node in usable form.
6. Calculate leakage. Identify amount, location, form, and cause of loss.
7. Distinguish necessary cost from extractive loss. Preserve useful coordination while reducing drain.
8. Shorten or redesign pathways. Remove unnecessary intermediaries or friction.
9. Seal boundary leaks. Prevent value from escaping through weak or extractive boundaries.
10. Reduce overhead burden. Ensure process cost does not consume repair value.
11. Protect usable form. Preserve timing, context, meaning, authority, or material usefulness through transfer.
12. Repair leakage debt. Address burden accumulated through prior non-arrival.
13. Install net-delivery metrics. Track arrival and load reduction, not just input.
14. Validate local coherence. Confirm receiving node stabilizes after leakage repair.

A valid restoration path should reduce:

leakage rate
overhead load
extraction load
arrival gap
gross/net confusion
delivery theater
affected-node burden
hidden debt
local incoherence

Economic Leakiness is not repaired by pouring more into the system.

It is repaired by making what enters actually arrive.

13. Cross-Module Links

• Economy: Core circulation-integrity failure; resources enter but do not arrive as usable support.
• Diagnostics: Requires leakage-rate, value-retention, resource-flow, affected-node-arrival, and hidden-debt diagnostics.
• Restoration: Repair resources can leak through process, management, optics, or mediation before reducing burden.
• Justice: Justice resources can be absorbed by procedure while affected nodes remain unrepaired.
• Cybernetics: Leakage weakens flow, control, restoration capacity, and feedback loops.
• Scaling: Large systems often increase pathway length, overhead, and leakage unless net arrival is audited.
• Security: Security spend can leak into tooling, dashboards, and compliance without risk reduction.
• AI Governance: Governance capacity can leak into policy, presentation, or reporting while review and repair remain under-resourced.
• Interfaces: Interfaces can consume attention or trust before action reaches need.
• Coherence: Local coherence depends on net value arrival, not gross input.

14. Relationship to Parent / Child Modes

Production treatment: Canon / Economy Parent

This mode maps upward to:

• FM-ECO-001 — Under-Delivery
• FM-C-021 — Parasitic Extraction
• FM-CORE-005 — Boundary Collapse
• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-004 — Auditability Collapse

Sibling or related Economy modes include:

• FM-ECO-001 — Under-Delivery
• FM-ECO-003 — Mis-Targeting
• FM-ECO-004 — Stasis / Blockage
• FM-ECO-006 — Shunting / Bypass
• FM-ECO-008 — Forced Profit
• FM-ECO-011 — Exported Economic Incoherence
• FM-ECOX-007 — Economic Leakiness
• FM-ECOX-024 — Extraction Masking Instability
• FM-ECOX-032 — Pseudo-Coherent Economic Stability

Related cross-family modes include:

• FM-C-021 — Parasitic Extraction
• FM-SEC-007 — Silent Extraction / Parasitic Coupling
• FM-JC-012 — Parasitic Contracting
• FM-R-004 — Repair Burden Externalization
• FM-R-007 — Repair Suppression via Efficiency
• FM-BIOX-018 — Circulation Stasis / Blockage
• FM-M-008 — Information Transfer Collapse
• FM-OMD-009 — Restoration Bottleneck Collapse
• FM-AIX-016 — Standingless Instrumentalization
• FM-REI-003 — Unbounded Extraction

Aliases preserved from source material:

• Economic Leakiness
• Resource Leakiness
• Value Leakage
• Circulation Leakage
• Delivery Leakage
• Repair Leakage
• Capacity Leakage
• Leaky Flow
• Resource Dissipation
• Value Drain

15. Minimal Entry Version

Definition: Economic leakiness occurs when resource, value, attention, care, signal, legitimacy, authority, repair, or capacity enters a system or delivery pathway but dissipates, escapes, is extracted, is absorbed by overhead, is diverted, or loses usable form before reaching and sustaining the affected node.

Signature:

input flow↑
pathway loss↑
retained value↓
affected-node arrival↓
delivery / outcome gap↑
H↑

Restoration direction:

• name the intended flow
• name the affected node
• map the pathway
• measure gross input
• measure net arrival
• calculate leakage
• distinguish necessary cost from extractive loss
• shorten or redesign pathways
• seal boundary leaks
• reduce overhead burden
• protect usable form
• repair leakage debt
• install net-delivery metrics
• validate local coherence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-005"
  name: "Economic Leakiness"
  family: "Economy"
  production_treatment: "Canon / Economy Parent"
  parent_modes:
    - "FM-ECO-001 — Under-Delivery"
    - "FM-C-021 — Parasitic Extraction"
    - "FM-CORE-005 — Boundary Collapse"
  primary_failure: "Resource, value, signal, care, authority, repair, or capacity enters a pathway but loses enough usable value before arrival that the affected node remains under-served or hidden debt accumulates."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-005"
  scope_note: "Conceptual and systems-oriented; does not treat all overhead, transaction cost, administration, mediation, infrastructure, translation, coordination, storage, taxation, governance, maintenance, or routing loss as inherently failed."
  aliases:
    - "Economic Leakiness"
    - "Resource Leakiness"
    - "Value Leakage"
    - "Circulation Leakage"
    - "Delivery Leakage"
    - "Repair Leakage"
    - "Capacity Leakage"
    - "Leaky Flow"
    - "Resource Dissipation"
    - "Value Drain"
  signature:
    - "input flow↑"
    - "pathway loss↑"
    - "retained value↓"
    - "affected-node arrival↓"
    - "delivery / outcome gap↑"
    - "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"
      - "U8 — Environment"
  state_variables:
    - "Φ"
    - "BΣ"
    - "Au"
    - "H"
    - "K"
    - "R"
    - "Λ"
    - "Γ"
    - "Ψ"
    - "O"
    - "Τ"
    - "D"
    - "G"
  first_gate_failure: "Leakage Gate"
  restoration:
    - "Leakage Audit"
    - "Resource Flow Sealing"
    - "Value Retention Repair"
    - "Overhead Deflation"
    - "Extraction Path Exposure"
    - "Boundary Reassertion"
    - "Affected-Node Arrival Verification"
    - "Hidden Debt Accounting"
    - "Local Coherence Restoration"