0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat reserves, storage, savings, buffering, waiting periods, triage, queues, pauses, or intentional holding patterns as inherently failed. Some systems need buffers. Some resources must be staged before release. Some flow must pause until timing, consent, safety, compatibility, or readiness is established.

The failure begins when held capacity stops being able to move to need.

The issue is not storage.

The issue is blocked circulation.

Stasis / Blockage occurs when something needed exists somewhere in the system but cannot move coherently to the node, phase, or layer that needs it.

1. Definition

Stasis / blockage occurs when resource, signal, value, care, attention, authority, information, repair, or capacity exists within a system but cannot circulate to the node, phase, layer, or field where it is needed, causing stagnation, backlog, depletion, hidden debt, or local incoherence.

The blocked flow may involve:

• money
• aid
• care
• data
• trust
• labor
• food
• tools
• authority
• repair
• information
• attention
• governance
• maintenance
• legitimacy
• infrastructure
• interpretation
• decision rights
• emotional support
• technical capacity
• justice resources
• restoration capacity

The core failure is:

resource exists
flow path blocked
need remains unmet
backlog / stagnation↑
H↑

Stasis / Blockage is not a lack of resource in the whole system.

It is failure of circulation between capacity and need.

2. Core Pattern

The core pattern is:

1. A node, field, function, or restoration process requires delivery.
2. The needed resource or capacity exists somewhere in the system.
3. Flow is blocked by boundary, bureaucracy, hoarding, fear, policy, bottleneck, interface, debt, timing, mistrust, gatekeeping, routing failure, or incompatibility.
4. The affected node remains under-delivered.
5. The holding location may appear resource-rich or stable.
6. The receiving location becomes depleted, stagnant, overloaded, or unstable.
7. The system counts stored, allocated, promised, or technically available resources as sufficient.
8. Backlog and hidden debt accumulate.
9. The blockage becomes normalized as process, scarcity, caution, efficiency, prioritization, or governance.
10. Restoration requires reopening or redesigning the flow path.

This failure mode often appears as:

the resources exist, so the need is covered

or:

the system has capacity, so delivery should eventually happen

or:

the queue is normal

The restorative question is:

where exactly does flow stop?

Circulation is not proven by possession.

It is proven by arrival.

3. Failure Signature

Typical signature:

resource exists
flow continuity↓
blockage / bottleneck↑
backlog↑
affected-node burden↑
local coherence↓
H↑

Extended signature:

funds allocated but not reaching field
authority exists but decisions stall
care exists but cannot be accessed
data exists but cannot be interpreted
repair capacity exists but queues grow
support exists but routing fails

Common forms include:

aid sitting in institutions while local need persists
security findings accumulating without remediation
AI governance reviews queued beyond deployment speed
justice cases waiting while harm compounds
repair teams blocked by approval chains
budgets allocated but not released
data trapped in silos
authority concentrated where it cannot act locally
maintenance deferred because scheduling pathways are blocked
restoration requests pending while affected nodes carry load

The defining condition is not that flow is slow.

The defining condition is that blocked flow allows need and debt to persist despite resource existing somewhere in the system.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: resources are held by actors, institutions, or layers that benefit from gatekeeping, delay, hoarding, or control.
• U2 — Configuration / Boundaries: boundaries, eligibility rules, silos, interfaces, or routing pathways prevent circulation.
• U3 — Execution / Runtime: delivery processes stall in queues, approvals, handoffs, or operational bottlenecks.
• U4 — Information / Truth: allocated or stored resources are counted as delivered resources.
• U5 — Coordination / Time: delay becomes chronic; timing no longer fits need.
• U6 — Coherence Field: the existence of capacity creates the feeling that the system is resourced.
• U7 — Memory / Recurrence: recurring blockages become normalized process.
• U8 — Environment / Field: field-wide constraints, mistrust, or infrastructure gaps prevent movement.

Common manifestation layers:

• U1 — Budgets: capacity is held.
• U2 — Boundaries: pathways are blocked.
• U3 — Execution: queues and bottlenecks form.
• U4 — Truth: allocated capacity is mistaken for delivered capacity.
• U5 — Time: delay compounds.
• U6 — Coherence Field: resource presence masks under-delivery.
• U7 — Memory: backlog becomes normal.

Stasis / Blockage is primarily a U2 / U3 flow-path failure.

The path between resource and need is broken.

5. Typical Development Sequence

A common development sequence is:

1. A need appears.
2. The system identifies or allocates resource.
3. The resource enters a holding path.
4. Movement depends on approval, routing, interpretation, trust, timing, eligibility, interface access, or operational capacity.
5. The path slows or blocks.
6. Resource accumulates upstream.
7. Need accumulates downstream.
8. The system cites upstream resource as evidence of support.
9. Affected nodes compensate or deteriorate.
10. Backlog becomes normalized.
11. Hidden debt grows.
12. Later failure is framed as scarcity despite resource existing in the system.

The loop often looks like:

need → resource allocated → path blocked → backlog → need persists

Another common loop is:

blockage exposed → more tracking added → tracking adds process load → blockage persists

Stasis / Blockage becomes self-reinforcing when the blocked layer gains authority by controlling access to flow.

6. Diagnostic Markers

Diagnostic markers include:

• Resources exist upstream while need persists downstream.
• Queues grow despite available capacity.
• Allocations are announced but field effects are absent.
• Approval chains delay urgent repair.
• Affected nodes cannot access support without excessive navigation.
• Data, authority, or care is trapped in silos.
• The system measures commitments rather than arrivals.
• Local actors know what is needed but cannot access release authority.
• Backlog becomes permanent baseline.
• Resources expire, degrade, or lose relevance before use.
• Delivery depends on one bottleneck node.
• The system cannot identify where flow is stopping.
• Hoarded reserves are defended as prudence while need compounds.
• Repair is delayed by administrative circulation failure.
• Local coherence improves when the blockage is removed, not when new resources are added.

Useful diagnostics:

• Resource Flow Integrity: Tests whether flow moves from source to need.
• Circulation Continuity: Measures interruptions in flow path.
• Blockage Location: Identifies where flow stops.
• Backlog Load: Measures accumulated unmet delivery.
• Delivery Adequacy: Tests whether arrival meets need.
• Affected-Node Burden: Measures cost carried while flow is blocked.
• Restoration Capacity: Tests whether repair can move through the system.
• Hidden Debt: Tracks compounded cost from delay.
• Auditability: Determines whether blockage can be traced.
• Local Coherence: Tests whether affected nodes stabilize after flow restoration.

7. Related Gates

Relevant gates include:

• Flow Gate: Fails when resource cannot circulate.
• Circulation Gate: Fails when movement between capacity and need breaks.
• Delivery Gate: Fails when resource does not arrive.
• Boundary Gate: Fails when silos, categories, or interfaces block flow.
• Capacity Gate: Fails when release capacity is insufficient.
• Restoration Gate: Fails when repair pathways are blocked.
• Auditability Gate: Fails when blockage cannot be located.
• Timing Gate: Fails when delay exceeds need window.

The first common gate failure is usually the Flow Gate.

The system has capacity but cannot move it.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; determines whether resources move.
• K — Constraint / Load: Rises where need remains unmet and where backlog accumulates.
• R — Restoration Capacity: May exist but fail to reach repair site.
• H — Hidden Debt: Accumulates through delay, unmet need, and stagnation.
• BΣ — Boundary Integrity: Can protect flow or block it through silos and gates.
• O — Coherence: Appears high upstream while falling downstream.
• Ψ — Observation / Interface: Shows allocations, queues, or arrivals depending on design.
• Au — Auditability: Determines whether blockage location can be traced.
• Γ — Selection: Selects which flow paths are opened or closed.
• Λ — Compatibility: Tests whether pathways fit resource, need, timing, and form.
• Τ — Trajectory / Time: Reveals compounding delay and decay.
• D — Damping: Can buffer delay temporarily.
• G — Gain: Can increase pressure but may worsen bottlenecks if pathways remain blocked.

Common operator pattern:

need appears
resource exists upstream
BΣ or process boundary blocks movement
Φ stalls
K rises downstream
O appears stable upstream
Ψ reports allocation
Au fails to locate blockage
R cannot reach affected node
H accumulates
Τ reveals backlog crisis

The core operator inversion is:

resource exists → need is resourced

instead of:

resource exists → flow path open → arrival verified → need is resourced

Stasis / Blockage turns stored capacity into delivery theater.

9. Related Laws and Invariants

Related Laws

• Hidden Debt Accumulation: unmet need compounds while flow is blocked.
• Restoration Starvation: repair capacity cannot reach the repair site.
• Economic Leakiness: flow can dissipate before arrival.
• Shunting / Bypass: flow may be rerouted around the true need.
• Under-Delivery: blocked flow produces under-supply at the affected node.
• Mis-Targeting: flow may be blocked because it is routed to wrong target.
• Zero-Slack Collapse: blocked queues consume margin.
• Capacity Collapse / Control Impossibility: backlogs can exceed control capacity.
• Auditability Collapse: blockage location becomes hard to inspect.
• Pseudo-Coherence: capacity presence masks local deprivation.

Related Invariants

• Resources Must Circulate to Need: stored capacity is insufficient without arrival.
• Blocked Flow Must Remain Auditable: systems must know where circulation stops.
• Stored Capacity Must Not Masquerade as Delivered Capacity: reserves are not support until usable.
• Repair Requires Unblocked Pathways: restoration must reach the burden source.
• Value Must Not Stagnate Away from Affected Nodes: value must move where it can reduce load.
• Backlog Must Not Be Normalized: chronic queues are hidden debt signals.
• Circulation Must Preserve Coherence Across the Field: upstream coherence cannot justify downstream depletion.

10. Common False Positives

Not every pause or reserve is Stasis / Blockage.

Common false positives include:

• Temporary staging before timely delivery.
• Reserves intentionally held for foreseeable future need.
• Queues that are bounded and within coherence threshold.
• Safe holding until consent, timing, or compatibility is established.
• Delayed release that prevents over-delivery.
• Resource stored where it remains accessible when needed.
• Legitimate triage with visible unmet-need accounting.
• Flow paused because the receiving node cannot yet absorb it.
• Buffering that reduces hidden debt.
• Holding patterns with clear release criteria and auditability.

Clarifying rule:

This is not Stasis / Blockage unless resource, signal, value, care, authority, repair, or capacity exists but cannot circulate to the node, layer, phase, or field where it is needed, leaving burden or hidden debt unresolved.

11. Common False Repairs

Common false repairs include:

• allocating more resource to the blocked pathway
• announcing new reserves
• creating more application steps
• adding dashboards that track backlog but do not move flow
• blaming affected nodes for not accessing support
• creating new gatekeepers
• issuing policy without release authority
• increasing pressure on bottleneck nodes without redesigning flow
• moving resources to a different holding layer
• reclassifying backlog as queue management
• celebrating commitments instead of arrivals
• adding eligibility filters to reduce visible demand
• routing flow around the blockage without reaching need
• calling chronic delay prudent governance

False repair often produces the loop:

blockage exposed → more resources allocated upstream → upstream reserve grows → downstream need persists

Another common loop is:

queue grows → process added to manage queue → process slows flow → queue grows

The repair fails because it increases capacity presence without reopening circulation.

12. Restoration Direction

Restoration requires locating the blockage, distinguishing stored from delivered capacity, reopening flow paths, clearing backlog, and verifying arrival at affected need.

Primary restoration direction:

locate the blockage,
open the flow path,
clear the backlog,
and verify arrival at need

A fuller restoration path includes:

1. Name the blocked flow. Identify the resource, value, care, signal, authority, information, repair, or capacity that is not moving.
2. Name the affected node. Identify where the flow is needed.
3. Map the flow path. Trace source, intermediaries, gates, boundaries, approvals, queues, interfaces, and destination.
4. Locate the blockage. Identify the exact point where flow slows, stalls, hoards, leaks, or loops.
5. Separate allocation from arrival. Stop counting upstream capacity as delivered support.
6. Measure backlog. Quantify unmet need and delay-created debt.
7. Remove unnecessary gates. Reduce approval, eligibility, category, interface, or administrative barriers.
8. Reconfigure boundaries. Open silos or create controlled passages where needed.
9. Increase release capacity. Add decision, distribution, translation, interpretation, or operational capacity.
10. Clear accumulated backlog. Move stuck resources and repair queued burden.
11. Protect against re-blockage. Install flow monitoring and threshold alerts.
12. Verify arrival and usability. Confirm the affected node receives and can use the flow.
13. Repair delay debt. Address harm caused by prior stasis.
14. Maintain circulation cadence. Keep flow moving at a rhythm matched to need.

A valid restoration path should reduce:

blockage
backlog
delay debt
upstream hoarding
downstream depletion
arrival gap
administrative load
repair latency
local incoherence
hidden debt

Stasis / Blockage is not repaired by owning more resource.

It is repaired by restoring movement.

13. Cross-Module Links

• Economy: Core circulation failure; available capacity does not move to need.
• Diagnostics: Requires flow-integrity, blockage-location, backlog-load, delivery-adequacy, and local-coherence diagnostics.
• Restoration: Restoration fails when repair capacity is queued, gated, or blocked before reaching the affected node.
• Justice: Justice can stall in procedural backlog while harm compounds.
• Cybernetics: Blockage produces latency, hidden debt, zero-slack collapse, and control incapacity.
• Scaling: Scale often creates bottlenecks, silos, and queue systems that block local delivery.
• Security: Findings, patches, incident response, or authority can bottleneck before risk is repaired.
• AI Governance: Review, escalation, appeals, and red-team findings can backlog until governance becomes symbolic.
• Interfaces: Interfaces can create or remove access friction.
• Coherence: Coherence depends on circulation; stagnant value cannot repair local fields.

14. Relationship to Parent / Child Modes

Production treatment: Canon / Economy Parent

This mode maps upward to:

• FM-ECO-001 — Under-Delivery
• FM-S-006 — Restoration Starvation
• FM-C-013 — Capacity Collapse / Control Impossibility
• 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-005 — Economic Leakiness
• FM-ECO-006 — Shunting / Bypass
• FM-ECO-007 — Phase Failure
• FM-ECOX-006 — Stasis / Blockage
• FM-ECOX-010 — Clearance Failure
• FM-ECOX-025 — Repair Starvation
• FM-ECOX-032 — Pseudo-Coherent Economic Stability

Related cross-family modes include:

• FM-S-006 — Restoration Starvation
• FM-C-011 — Zero-Slack Collapse
• FM-C-013 — Capacity Collapse / Control Impossibility
• FM-R-004 — Repair Burden Externalization
• FM-OMD-009 — Restoration Bottleneck Collapse
• FM-BIOX-018 — Circulation Stasis / Blockage
• FM-BIOX-019 — Biological Clearance Failure
• FM-M-008 — Information Transfer Collapse
• FM-JC-004 — Under-Resourced Justice
• FM-RX-009 — Repair Through Suppressed Auditability

Aliases preserved from source material:

• Stasis / Blockage
• Economic Stasis
• Resource Blockage
• Circulation Blockage
• Flow Blockage
• Repair Blockage
• Capacity Blockage
• Value Stasis
• Resource Stagnation
• Blocked Circulation

15. Minimal Entry Version

Definition: Stasis / blockage occurs when resource, signal, value, care, attention, authority, information, repair, or capacity exists within a system but cannot circulate to the node, phase, layer, or field where it is needed, causing stagnation, backlog, depletion, hidden debt, or local incoherence.

Signature:

resource exists
flow continuity↓
blockage / bottleneck↑
backlog↑
affected-node burden↑
local coherence↓
H↑

Restoration direction:

• name the blocked flow
• name the affected node
• map the flow path
• locate the blockage
• separate allocation from arrival
• measure backlog
• remove unnecessary gates
• reconfigure boundaries
• increase release capacity
• clear accumulated backlog
• protect against re-blockage
• verify arrival and usability
• repair delay debt
• maintain circulation cadence

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-004"
  name: "Stasis / Blockage"
  family: "Economy"
  production_treatment: "Canon / Economy Parent"
  parent_modes:
    - "FM-ECO-001 — Under-Delivery"
    - "FM-S-006 — Restoration Starvation"
    - "FM-C-013 — Capacity Collapse / Control Impossibility"
  primary_failure: "Resource, signal, value, care, authority, repair, or capacity exists but cannot circulate to the node, layer, phase, or field where it is needed, leaving burden or hidden debt unresolved."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-004"
  scope_note: "Conceptual and systems-oriented; does not treat reserves, storage, savings, buffering, waiting periods, triage, queues, pauses, or intentional holding patterns as inherently failed."
  aliases:
    - "Stasis / Blockage"
    - "Economic Stasis"
    - "Resource Blockage"
    - "Circulation Blockage"
    - "Flow Blockage"
    - "Repair Blockage"
    - "Capacity Blockage"
    - "Value Stasis"
    - "Resource Stagnation"
    - "Blocked Circulation"
  signature:
    - "resource exists"
    - "flow continuity↓"
    - "blockage / bottleneck↑"
    - "backlog↑"
    - "affected-node burden↑"
    - "local coherence↓"
    - "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"
    - "BΣ"
    - "O"
    - "Ψ"
    - "Au"
    - "Γ"
    - "Λ"
    - "Τ"
    - "D"
    - "G"
  first_gate_failure: "Flow Gate"
  restoration:
    - "Circulation Restoration"
    - "Blockage Mapping"
    - "Flow Path Reopening"
    - "Backlog Clearance"
    - "Resource Re-Routing"
    - "Repair Path Unblocking"
    - "Boundary Reconfiguration"
    - "Hidden Debt Accounting"
    - "Local Coherence Restoration"