0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat rerouting, alternate channels, bypass paths, proxies, detours, triage, load balancing, indirect support, or emergency redirection as inherently failed. Some systems need bypasses. A blocked path may require alternate routing. A direct path can be unsafe, unavailable, or temporarily incompatible.

The failure begins when bypass becomes substitute for arrival.

The issue is not rerouting.

The issue is flow that moves around need instead of reaching it.

Shunting / Bypass occurs when movement exists, but the load-bearing node remains untouched.

1. Definition

Shunting / bypass occurs when resource, value, signal, care, attention, authority, repair, legitimacy, or capacity is routed around the node, layer, field, phase, or burden source that actually requires it, producing apparent circulation while the real need remains unserved.

The bypassed target may be:

• an affected node
• a local field
• a harmed party
• a repair site
• an overloaded team
• a depleted community
• a root cause
• a runtime layer
• a boundary failure
• a hidden debt location
• a biological or material burden
• an implementation layer
• a truth source
• a restoration phase
• a security risk
• an AI review bottleneck
• a justice need

The core failure is:

flow moves
need is bypassed
arrival at burden source↓
delivery credit↑
H↑

Shunting / Bypass is not a failure of motion.

It is a failure of arrival.

2. Core Pattern

The core pattern is:

1. A need, burden, harm, repair site, or load-bearing node exists.
2. Flow is initiated.
3. The direct path is uncomfortable, costly, slow, politically inconvenient, hard to inspect, or difficult to repair.
4. The system routes flow through a visible, easier, safer, more powerful, more legible, or less resistant pathway.
5. Flow appears active.
6. The load-bearing node remains unrepaired or under-supplied.
7. The system counts the routed flow as support, delivery, care, investment, repair, or progress.
8. The actual burden persists.
9. Hidden debt accumulates where the flow failed to arrive.
10. Later failure reveals that circulation was not restoration.

This failure mode often appears as:

resources are moving, so the system is responding

or:

we supported the ecosystem, so the affected node was supported

or:

the repair effort happened near the problem, so the problem was repaired

The restorative question is:

did the flow reach the load-bearing need, or did it route around it?

A bypass is valid only if it still reaches the real target.

3. Failure Signature

Typical signature:

visible flow↑
burden-source arrival↓
proxy-channel activity↑
affected-node load unchanged
delivery credit↑
H↑

Extended signature:

aid moves around the harmed node
funding moves around the local field
attention moves around the root cause
repair moves around the burden
authority moves around the actor who can act
care moves around the person who needs it

Common forms include:

funding public relations instead of repair
supporting institutions around affected communities without reaching them
routing justice resources to procedure while affected nodes remain unrepaired
delivering security tooling around analysts without improving triage
AI governance work routed to policy optics instead of review and remedy
economic investment bypassing local circulation
care routed to symbolic gestures rather than load reduction
restoration work avoiding the hardest wound
attention focusing on visible discourse instead of hidden burden
capacity sent to leadership layers while operators remain overloaded

The defining condition is not indirect delivery.

The defining condition is indirect flow that never reaches the real coherence requirement.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: powerful or visible nodes capture flow before it reaches affected nodes.
• U2 — Configuration / Boundaries: delivery pathways are configured around convenience, hierarchy, optics, or existing channels rather than need.
• U3 — Execution / Runtime: actual routing bypasses the burden source during operation.
• U4 — Information / Truth: visible movement substitutes for arrival truth.
• U5 — Coordination / Time: bypass paths persist because direct repair is delayed.
• U6 — Coherence Field: motion creates the feeling that something is being done.
• U7 — Memory / Recurrence: habitual bypass routes become normalized.
• U8 — Environment / Field: field incentives reward visible circulation over load-bearing arrival.

Common manifestation layers:

• U1 — Budgets: flow follows power.
• U2 — Boundaries: routing avoids affected-state geometry.
• U3 — Execution: bypass occurs operationally.
• U4 — Truth: movement is counted as delivery.
• U5 — Time: bypass becomes chronic.
• U6 — Coherence Field: active circulation masks non-arrival.

Shunting / Bypass is primarily a U2 / U3 routing-fidelity failure.

The pathway becomes more real to the system than the need.

5. Typical Development Sequence

A common development sequence is:

1. A burdened node requires flow.
2. A delivery process begins.
3. Direct delivery is hard, contested, slow, expensive, shameful, or politically inconvenient.
4. The system selects an indirect or proxy route.
5. Flow begins moving visibly.
6. The selected route becomes the official pathway.
7. Intermediaries or adjacent nodes receive attention, resource, or authority.
8. The actual burdened node remains under-supported.
9. The system cites routing activity as progress.
10. The need persists.
11. Additional flow is routed through the same bypass.
12. Hidden debt grows while circulation metrics improve.

The loop often looks like:

need → flow initiated → difficult target bypassed → visible movement → need persists

Another common loop is:

bypass exposed → pathway renamed direct support → routing unchanged → burden remains

Shunting / Bypass becomes self-reinforcing when proxy pathways develop their own legitimacy, budgets, and survival incentives.

6. Diagnostic Markers

Diagnostic markers include:

• Flow volume rises while affected-node burden remains.
• The load-bearing node cannot identify received benefit.
• Proxy institutions, categories, or interfaces receive most of the movement.
• Resources pass near the problem but not into the repair site.
• The system tracks routed activity rather than arrival.
• Direct delivery is treated as too difficult or disruptive.
• Bypass channels become politically or administratively protected.
• The receiving proxy becomes a gatekeeper.
• The actual burden source must request help repeatedly.
• Delivery reports describe ecosystem-level action but not local load reduction.
• The hardest, most wounded, or most constrained site is avoided.
• Flow is celebrated before arrival is verified.
• Restoration improves when the pathway is rerouted directly.
• Bypass persists because direct repair would expose hidden debt.
• The system cannot distinguish motion from relief.

Useful diagnostics:

• Routing Integrity: Tests whether flow follows the need path.
• Affected-Node Arrival: Measures what reaches the actual burdened node.
• Bypass Detection: Identifies paths that route around need.
• Need / Supply Fit: Tests whether delivered flow matches actual need.
• Resource Flow Integrity: Tests continuity from source to burden.
• Repair Target Fit: Determines whether repair reaches the burden source.
• Hidden Debt: Tracks cost left behind by bypass.
• Auditability: Determines whether routing can be inspected.
• Local Coherence: Tests whether the actual target stabilizes.
• Load Reduction: Measures whether the burden falls at the right site.

7. Related Gates

Relevant gates include:

• Routing Gate: Fails when flow does not follow the burden path.
• Bypass Gate: Fails when alternate routes avoid the actual need.
• Delivery Gate: Fails when movement does not become arrival.
• Need Gate: Fails when the system does not preserve the true target.
• Restoration Gate: Fails when repair avoids the wound.
• Boundary Gate: Fails when proxy boundaries obscure affected-state boundaries.
• Auditability Gate: Fails when routing cannot be traced.
• Local Coherence Gate: Fails when the affected field does not stabilize.

The first common gate failure is usually the Routing Gate.

The system moves resources without preserving target contact.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; determines whether flow reaches need or routes around it.
• Γ — Selection: Selects visible, convenient, powerful, or safe channels over load-bearing channels.
• Λ — Compatibility: Tests whether the route is compatible with actual need.
• BΣ — Boundary Integrity: Determines whether proxy and affected-node boundaries remain distinct.
• Ψ — Observation / Interface: Shows circulation while possibly hiding non-arrival.
• Au — Auditability: Determines whether routing can be traced from source to target.
• H — Hidden Debt: Accumulates where the burden remains.
• K — Constraint / Load: Remains high at the bypassed node.
• R — Restoration Capacity: Fails to reach repair site when bypassed.
• O — Coherence: May appear high because visible motion creates confidence.
• Τ — Trajectory / Time: Reveals persistence of burden despite flow.
• D — Damping: Can hide distress or buffer bypass temporarily.
• G — Gain: Can increase flow volume through the wrong route.

Common operator pattern:

need appears
Γ selects convenient route
Φ moves resource through proxy channel
Ψ observes active circulation
BΣ proxy/affected boundary blurs
Λ fit with true need declines
Au tracks activity but not arrival
K remains at burden source
R fails to reach repair site
H accumulates

The core operator inversion is:

flow near need → delivery to need

instead of:

flow into burden source → load reduction → delivery to need

Shunting / Bypass turns motion into false arrival.

9. Related Laws and Invariants

Related Laws

• Hidden Debt Accumulation: bypassed need remains as deferred cost.
• Mis-Targeting: flow goes to wrong target.
• Economic Leakiness: value dissipates or is diverted before arrival.
• Under-Delivery: the real need remains under-supplied.
• Stasis / Blockage: direct path may be blocked, causing bypass.
• Parasitic Extraction: bypass channels may capture value.
• Restoration Bypass: repair language avoids the real wound.
• Auditability Collapse: route-to-arrival cannot be traced.
• Success Proxy Substitution: routing activity substitutes for actual support.
• Pseudo-Coherence: visible circulation creates apparent response.

Related Invariants

• Flow Must Not Bypass Need: routing must preserve contact with the burden.
• Repair Must Reach the Burden Source: restoration must land where load exists.
• Circulation Must Preserve Affected-Node Contact: flow must not lose target.
• Bypass Routes Must Remain Auditable: alternate paths require arrival proof.
• Routing Must Not Replace Restoration: movement is not repair.
• Visible Flow Must Be Tested Against Arrival: activity requires outcome audit.
• Convenient Paths Must Not Override Coherent Paths: routing ease cannot outrank need.

10. Common False Positives

Not every bypass is Shunting / Bypass.

Common false positives include:

• Alternate routing that still reaches the affected node.
• Emergency detour around a blocked path with arrival verification.
• Indirect support that demonstrably reduces load.
• Infrastructure investment that directly enables downstream repair.
• Proxy delivery with strong fidelity and affected-node validation.
• Temporary bypass with clear return to direct delivery.
• Routing around harmful intermediaries to reach need more cleanly.
• Support delivered to an adjacent node because the adjacent node is the true bottleneck.
• A phased bypass that prepares the affected node for later arrival.
• Bypass used to avoid over-delivery while preserving eventual delivery.

Clarifying rule:

This is not Shunting / Bypass unless resource, value, signal, care, authority, repair, or capacity is routed around the actual affected node, burden source, layer, phase, or repair site while the system counts the movement as support, delivery, or restoration.

11. Common False Repairs

Common false repairs include:

• increasing flow through the bypass route
• renaming the bypass as direct support
• funding proxy channels more heavily
• adding reporting about routed activity
• treating ecosystem benefit as affected-node repair
• creating ceremonies around support without arrival
• using symbolic repair near the burden source
• blaming affected nodes for not benefiting from adjacent delivery
• routing through powerful intermediaries for legitimacy
• adding dashboards that show movement but not arrival
• substituting public attention for local repair
• delivering to the easiest layer
• treating bypass as necessary because direct repair is uncomfortable
• creating permanent bypass infrastructure

False repair often produces the loop:

need persists → more flow through bypass → visible circulation rises → need persists

Another common loop is:

bypass criticized → bypass reframed as strategic routing → arrival remains absent

The repair fails because it preserves the route that avoids the actual burden.

12. Restoration Direction

Restoration requires tracing the bypass, restoring contact with the affected node, rerouting flow into the burden source, and verifying actual load reduction.

Primary restoration direction:

identify the bypass,
restore target contact,
reroute into need,
and verify load reduction

A fuller restoration path includes:

1. Name the intended need. Identify the affected node, burden source, repair site, or phase requiring flow.
2. Name the bypass route. Identify where the flow actually goes.
3. Map source-to-target movement. Trace the full routing path.
4. Compare routed flow to arrival. Determine whether movement reaches the actual need.
5. Identify why bypass occurred. Name discomfort, power, convenience, fear, blockage, optics, gatekeeping, or incompatibility.
6. Reduce proxy authority. Stop counting adjacent or proxy movement as affected-node repair.
7. Restore affected-node contact. Let the burdened node validate need and arrival.
8. Reroute usable flow. Send resource, authority, attention, or repair directly into the load-bearing site where possible.
9. Repair blocked direct paths. Remove barriers that made bypass attractive.
10. Protect against capture. Prevent intermediaries from absorbing rerouted flow.
11. Verify load reduction. Confirm the actual burden decreases.
12. Audit bypass debt. Address cost accumulated while flow avoided need.
13. Install arrival metrics. Track arrival and effect, not only movement.
14. Maintain routing integrity. Recheck over time as pathways adapt.

A valid restoration path should reduce:

bypass volume
proxy capture
arrival gap
affected-node burden
routing distortion
delivery theater
repair avoidance
hidden debt
local incoherence

Shunting / Bypass is not repaired by increasing circulation.

It is repaired by making circulation land.

13. Cross-Module Links

• Economy: Core routing failure; circulation appears active while need is bypassed.
• Diagnostics: Requires routing-integrity, bypass-detection, affected-node-arrival, repair-target-fit, and load-reduction diagnostics.
• Restoration: Direct link to restoration bypass and symbolic repair that avoids burden.
• Justice: Justice systems can route activity through procedure, settlement, or optics while harmed nodes remain unrepaired.
• Cybernetics: Bypass reflects selection, routing, boundary, and feedback failure.
• Scaling: Scaled systems often route through legible intermediaries that bypass local need.
• Security: Security resources can route to tools, reports, or compliance while risk-bearing nodes remain exposed.
• AI Governance: Governance effort can bypass users, reviewers, affected communities, or downstream harm sites.
• Interfaces: Interfaces can direct attention around rather than into action pathways.
• Coherence: Coherence requires arrival at burden, not movement near burden.

14. Relationship to Parent / Child Modes

Production treatment: Canon / Economy Parent

This mode maps upward to:

• FM-ECO-003 — Mis-Targeting
• FM-ECO-005 — Economic Leakiness
• FM-RX-001 — Pseudo-Restoration
• FM-CORE-003 — Success Proxy Substitution
• FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Economy modes include:

• FM-ECO-001 — Under-Delivery
• FM-ECO-003 — Mis-Targeting
• FM-ECO-004 — Stasis / Blockage
• FM-ECO-005 — Economic Leakiness
• FM-ECO-007 — Phase Failure
• FM-ECOX-009 — Shunting / Bypass
• FM-ECOX-014 — Suppression-by-Abstraction
• FM-ECOX-024 — Extraction Masking Instability
• FM-ECOX-032 — Pseudo-Coherent Economic Stability

Related cross-family modes include:

• FM-RX-002 — Symbolic Repair
• FM-R-001 — Cosmetic Restoration
• FM-R-003 — Insight Without Load Reduction
• FM-R-004 — Repair Burden Externalization
• FM-JC-001 — Procedural Theater
• FM-C-015 — Proxy-Relay Drift
• FM-C-021 — Parasitic Extraction
• FM-SEC-006 — Metric Capture / Reward-Hacked Security
• FM-MT-008 — Logistics Blind Spot
• FM-OMD-009 — Restoration Bottleneck Collapse

Aliases preserved from source material:

• Shunting / Bypass
• Resource Shunting
• Economic Bypass
• Repair Bypass
• Need Bypass
• Flow Bypass
• Value Shunting
• Circulation Bypass
• Bypass Delivery
• Load-Bearing Node Bypass

15. Minimal Entry Version

Definition: Shunting / bypass occurs when resource, value, signal, care, attention, authority, repair, legitimacy, or capacity is routed around the node, layer, field, phase, or burden source that actually requires it, producing apparent circulation while the real need remains unserved.

Signature:

visible flow↑
burden-source arrival↓
proxy-channel activity↑
affected-node load unchanged
delivery credit↑
H↑

Restoration direction:

• name the intended need
• name the bypass route
• map source-to-target movement
• compare routed flow to arrival
• identify why bypass occurred
• reduce proxy authority
• restore affected-node contact
• reroute usable flow
• repair blocked direct paths
• protect against capture
• verify load reduction
• audit bypass debt
• install arrival metrics
• maintain routing integrity

16. Machine-Readable Summary

failure_mode:
  id: "FM-ECO-006"
  name: "Shunting / Bypass"
  family: "Economy"
  production_treatment: "Canon / Economy Parent"
  parent_modes:
    - "FM-ECO-003 — Mis-Targeting"
    - "FM-ECO-005 — Economic Leakiness"
    - "FM-RX-001 — Pseudo-Restoration"
  primary_failure: "Resource, value, signal, care, authority, repair, or capacity is routed around the actual affected node, burden source, layer, phase, or repair site while the system counts the movement as support, delivery, or restoration."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-006"
  scope_note: "Conceptual and systems-oriented; does not treat rerouting, alternate channels, bypass paths, proxies, detours, triage, load balancing, indirect support, or emergency redirection as inherently failed."
  aliases:
    - "Shunting / Bypass"
    - "Resource Shunting"
    - "Economic Bypass"
    - "Repair Bypass"
    - "Need Bypass"
    - "Flow Bypass"
    - "Value Shunting"
    - "Circulation Bypass"
    - "Bypass Delivery"
    - "Load-Bearing Node Bypass"
  signature:
    - "visible flow↑"
    - "burden-source arrival↓"
    - "proxy-channel activity↑"
    - "affected-node load unchanged"
    - "delivery credit↑"
    - "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"
  state_variables:
    - "Φ"
    - "Γ"
    - "Λ"
    - "BΣ"
    - "Ψ"
    - "Au"
    - "H"
    - "K"
    - "R"
    - "O"
    - "Τ"
    - "D"
    - "G"
  first_gate_failure: "Routing Gate"
  restoration:
    - "Bypass Route Audit"
    - "Resource Re-Routing"
    - "Affected-Node Recontact"
    - "Repair Target Rebinding"
    - "Routing Integrity Repair"
    - "Hidden Debt Accounting"
    - "Arrival Verification"
    - "Local Coherence Restoration"
    - "Bypass Closure"