0. Economic Scope Note
This entry is conceptual and systems-oriented.
It does not treat specialization, trade, delegation, outsourcing, distribution, local optimization, differentiated roles, interdependence, or boundary-setting as inherently failed.
Economic systems often move work, risk, value, and responsibility across nodes.
That movement can be coherent when it is:
- consent-valid
- auditable
- reciprocal
- capacity-aware
- restoration-bound
- locally viable
- globally coherent
- transparent about cost
- accountable for downstream effects
- compatible with affected nodes
- honest about maintenance and repair
The failure begins when incoherence is exported.
The issue is not exchange across boundaries.
The issue is local success built by displacing unresolved burden outside the accounting frame.
Exported Economic Incoherence occurs when a system looks stable, efficient, profitable, affordable, or scalable only because some other node is made to absorb what the originating system refuses to carry, price, repair, or reveal.
1. Definition
Exported Economic Incoherence occurs when a system preserves or improves local economic coherence by displacing cost, instability, risk, extraction burden, repair debt, scarcity, volatility, maintenance load, or harm into another node, region, class, layer, generation, ecosystem, or future time horizon.
The exported burden may include:
- unpaid labor
- under-maintenance
- environmental damage
- degraded health
- infrastructure decay
- local instability
- downstream scarcity
- family or community burden
- future debt
- user friction
- worker exhaustion
- social distrust
- repair backlog
- hidden risk
- legal exposure
- attention drain
- cognitive burden
- governance burden
- emergency response burden
- unpriced dependency
- ecological absorption
- legitimacy loss
The core failure is:
local success↑
accounting boundary narrows
external burden↑
global coherence↓
H↑Exported Economic Incoherence is not ordinary cost distribution.
It is unacknowledged burden transfer that allows one location of the system to appear coherent by making another location less coherent.
2. Core Pattern
The core pattern is:
- A system faces cost, risk, repair need, maintenance load, complexity, scarcity, or instability.
- The system preserves its local metrics by moving the burden elsewhere.
- The receiving node lacks equivalent power, visibility, compensation, agency, or repair capacity.
- The originating node records improved efficiency, profit, affordability, growth, or stability.
- The receiving node accumulates hidden debt.
- Accounting boundaries prevent the exported burden from appearing in the success metric.
- Local coherence is mistaken for total coherence.
- The exported burden compounds.
- The wider field becomes less stable.
- Restoration requires bringing the burden back into visibility, accounting, reciprocity, and repair.
This failure often appears as:
our system is efficientwhile the hidden truth is:
because another system is absorbing the inefficiencyor:
our costs are lowwhile the overlooked condition is:
because someone else is paying the cost outside the ledgerThe restorative question is:
where did the incoherence go?Exported Economic Incoherence turns accounting boundaries into concealment boundaries.
3. Failure Signature
Typical signature:
local coherence↑
external burden↑
accounting boundary tightens
affected-node viability↓
repair debt↑
Au↓
H↑Extended signature:
prices stay low while labor burden rises
profits rise while maintenance is deferred
service expands while support burden moves to users
platforms scale while moderation burden moves to communities
cities grow while infrastructure debt moves to future budgets
supply chains cheapen while ecological cost moves downstream
contracts stabilize buyers while risk moves to suppliers
AI tools improve productivity while cognitive repair burden moves to usersCommon forms include:
cheap goods created through invisible labor strain
organizational efficiency created by pushing admin burden onto clients
public cost reduced by moving repair burden to households
profit preserved by deferring infrastructure maintenance
security burden transferred to end users without usable support
AI deployment moving review, correction, and meaning repair to users
contract value preserved by forcing downstream suppliers to absorb volatility
growth funded by future maintenance debt
local stability maintained by exporting pollution, scarcity, or instability
platform value created by extracting social graph labor without restorationThe defining condition is not that one system affects another.
The defining condition is that the originating system counts itself successful while displaced burden degrades another node or horizon.
4. Primary U-Layer Origin
Common origin layers:
- U1 — Power / Budgets: power asymmetry allows one node to transfer cost to another.
- U2 — Configuration / Boundaries: accounting, legal, contractual, organizational, or geographic boundaries exclude exported burden.
- U3 — Execution / Runtime: operations route work, cost, friction, risk, or maintenance load downstream.
- U4 — Information / Truth: local metrics substitute for global coherence truth.
- U5 — Coordination / Time: burdens are shifted into the future or outside the timing window of accountability.
- U6 — Coherence Field: local stability creates legitimacy aura despite field damage.
- U7 — Memory / Recurrence: repeated burden export becomes normalized as business model or policy.
- U8 — Environment / Field: external environments absorb unpriced instability until thresholds break.
Common manifestation layers:
- U1 — Power: stronger nodes define the terms of burden transfer.
- U2 — Boundaries: responsibility stops at convenient edges.
- U3 — Execution: burden routing becomes operational.
- U4 — Truth: metrics hide external effects.
- U5 — Time: cost is deferred.
- U6 — Field: local success masks global degradation.
- U8 — Environment: external systems absorb damage.
Exported Economic Incoherence is primarily a U2 accounting-boundary and U4 truth-substitution failure, anchored by U1 power asymmetry.
The system narrows the frame until the exported burden no longer counts.
5. Typical Development Sequence
A common development sequence is:
- A system identifies a cost, risk, repair need, or operational burden.
- Carrying the burden would reduce local profit, speed, efficiency, growth, or stability.
- A pathway exists to move the burden elsewhere.
- The system shifts the burden across a boundary.
- The local metric improves.
- The displaced burden is not measured or is assigned to a lower-power node.
- The system interprets improvement as success.
- More burden-shifting is selected.
- Affected nodes degrade or accumulate repair debt.
- The wider field becomes more fragile.
- The originating node appears coherent until the externalized debt returns as crisis, instability, legitimacy loss, or systemic breakdown.
The loop often looks like:
local burden → export path → local success → export normalized → field debtAnother common loop is:
cost pressure → boundary narrowing → hidden external burden → improved metric → more cost pressureExported Economic Incoherence becomes self-reinforcing when local metrics reward the act of displacement.
6. Diagnostic Markers
Diagnostic markers include:
- Local metrics improve while downstream nodes degrade.
- Cost reductions are not matched by genuine efficiency improvements.
- Affected nodes report increased burden outside the official ledger.
- Repair needs appear somewhere other than where gain is recorded.
- Profit, affordability, speed, or growth depends on unmeasured maintenance debt.
- The system cannot answer where displaced cost went.
- Responsibility boundaries are narrower than effect boundaries.
- Externalities are treated as irrelevant, incidental, or outside scope.
- Future budgets carry costs created by present decisions.
- User, worker, supplier, community, or ecological burden rises.
- Stability appears local but not field-wide.
- Audits stop at legal, contractual, departmental, or platform boundaries.
- Harm is described as downstream adaptation rather than upstream displacement.
- The receiving node lacks power to refuse or price the burden.
- Restoration improves when accounting boundaries expand.
Useful diagnostics:
- Externalized Burden: Measures burden transferred outside the originating node.
- Local / Global Coherence Delta: Compares local stability to wider-field degradation.
- Hidden Debt: Tracks displaced cost, risk, repair, and maintenance burden.
- Repair Debt: Measures unresolved restoration obligations created by export.
- Risk Transfer: Identifies where risk has moved.
- Cost Displacement: Tracks unpriced or off-ledger cost.
- Affected-Node Viability: Tests whether receiving nodes remain coherent.
- Auditability: Determines whether exported burden can be traced.
- Reciprocity Balance: Tests whether receiving nodes are compensated or restored.
- Restoration Capacity: Measures whether repair can occur where burden lands.
7. Related Gates
Relevant gates include:
- Externality Gate: Fails when displaced burden is excluded from success accounting.
- Global Coherence Gate: Fails when local success is accepted despite wider-field degradation.
- Burden Accounting Gate: Fails when cost, risk, repair, or harm is not traced to source.
- Auditability Gate: Fails when burden pathways cannot be inspected.
- Reciprocity Gate: Fails when receiving nodes absorb burden without equivalent support.
- Restoration Gate: Fails when exported harm lacks repair obligation.
- Boundary Gate: Fails when responsibility boundaries are narrower than effect boundaries.
- Justice Gate: Fails when affected nodes lack standing, remedy, or recognition.
- Local / Global Fit Gate: Fails when local coherence is incompatible with global coherence.
The first common gate failure is usually the Externality Gate.
The system lets displaced burden fall outside what counts.
8. Related Operators
Relevant operators include:
- Φ — Flow / Resource Movement: Determines how value, cost, risk, and burden move.
- H — Hidden Debt: Accumulates where displaced burden lands.
- O — Coherence: Splits into local apparent coherence and global incoherence.
- Au — Auditability: Determines whether burden pathways remain traceable.
- BΣ — Boundary Integrity: Defines whether accounting boundaries match effect boundaries.
- Γ — Selection: Selects which burdens are internalized and which are exported.
- Λ — Compatibility: Tests whether burden transfer is compatible with affected-node viability.
- K — Constraint / Load: Rises in receiving nodes.
- R — Restoration Capacity: Must follow burden; fails when repair is not assigned.
- Ψ — Observation / Interface: Reveals or hides externalized effects.
- G — Gain: Amplifies pressure to export burden for local advantage.
- D — Damping: Should limit harmful displacement.
- Τ — Trajectory / Time: Tracks deferred burden and future-return effects.
Common operator pattern:
G local success pressure rises
Γ selects burden export
Φ routes cost outward
BΣ narrows accounting boundary
Au falls across the boundary
K rises in receiving nodes
R does not follow burden
O appears high locally
H accumulates globallyThe core operator inversion is:
local coherence → system coherenceinstead of:
local coherence + no exported burden + restored externalities → system coherenceExported Economic Incoherence turns boundary design into burden concealment.
9. Related Laws and Invariants
Related Laws
- Hidden Debt Accumulation: exported burden becomes stored system cost.
- Pseudo-Coherence: local coherence hides global incoherence.
- Forced Profit: profit can depend on displaced burden.
- Economic Leakiness: value leaves intended circuits while burden remains.
- Shunting / Bypass: flows route around responsibility or local need.
- Unbounded Extraction: extraction grows beyond reciprocity and repair.
- Parasitic Extraction: one node feeds on another’s viability.
- Success Proxy Substitution: local metrics replace global coherence.
- Goodhart Collapse: local performance targets incentivize burden export.
- Terminal Scaling Failure: exported debt eventually returns as scale collapse.
- Capacity-Inverting Restoration: repair burden is pushed onto affected nodes.
- Victim Burden Inversion: harmed nodes are forced to carry correction cost.
Related Invariants
- Local Coherence Must Not Export Global Incoherence: local success is invalid if it depends on field degradation.
- Economic Gain Must Account for Displaced Burden: value must include downstream cost.
- Externalities Must Remain Auditable: effects outside the origin must remain traceable.
- Repair Debt Must Follow the Source: the origin of burden carries restoration obligation.
- Value Flow Must Preserve Affected Nodes: economic circulation must not consume the nodes that enable it.
- No Stability Through Burden Displacement: stability cannot be considered coherent if it is achieved by exporting instability.
- Global Coherence Bounds Local Success: local performance is constrained by wider-field effects.
10. Common False Positives
Not every cross-boundary cost movement is Exported Economic Incoherence.
Common false positives include:
- Coherent outsourcing with fair compensation and auditability.
- Trade where value, risk, and responsibility are transparently distributed.
- Delegation to a node with real capacity and consent.
- Insurance-like risk pooling with honest pricing and repair capacity.
- Specialization that increases total coherence.
- Shared infrastructure where maintenance obligations are clearly assigned.
- Temporary burden transfer paired with restoration support.
- External cost that is fully priced, disclosed, and repaired.
- Local optimization that does not degrade the wider field.
- Future investment where future capacity is funded and protected.
- Distributed responsibility with clear accountability.
- Emergency burden transfer chosen by affected nodes with later repair.
Clarifying rule:
This is not Exported Economic Incoherence unless local economic success, stability, efficiency, affordability, growth, or profitability depends on transferring unresolved cost, risk, repair, scarcity, harm, or instability outside the accounting boundary.
11. Common False Repairs
Common false repairs include:
- adding disclosure without repairing displaced burden
- redefining externalities as outside scope
- creating offset programs that do not restore affected nodes
- compensating visible harm while ignoring hidden burden
- improving local metrics while downstream debt continues
- moving the burden to a different downstream node
- creating audits that stop at legal boundaries
- calling burden export “efficiency”
- treating future debt as future opportunity
- requiring affected nodes to prove damage after auditability was suppressed
- pricing externalized burden too low
- offering symbolic restitution without changing the transfer mechanism
- centralizing gain while decentralizing repair obligation
- using charitable programs to mask structural displacement
- claiming compliance while responsibility boundaries remain narrower than effect boundaries
False repair often produces the loop:
externality exposed → symbolic accounting → burden path preserved → incoherence continuesAnother common loop is:
downstream degradation appears → blamed on downstream weakness → upstream export continuesThe repair fails because it does not bring the exported burden back into the coherence ledger.
12. Restoration Direction
Restoration requires expanding the accounting boundary, tracing displaced burden, assigning repair obligation to the source, restoring affected nodes, and redesigning value flow so local success no longer depends on global incoherence.
Primary restoration direction:
trace exported burden,
expand the accounting frame,
assign repair debt,
and rebalance local / global coherenceA fuller restoration path includes:
- Name the local success. Identify the profit, efficiency, affordability, growth, speed, or stability being claimed.
- Map the accounting boundary. Identify what is counted and what is excluded.
- Trace burden pathways. Determine where cost, risk, maintenance, repair, instability, or harm moved.
- Identify affected nodes. Name the workers, users, suppliers, communities, ecosystems, future budgets, or downstream systems carrying the burden.
- Measure local / global coherence delta. Compare origin-node success with field-wide effects.
- Audit power asymmetry. Determine whether receiving nodes could refuse, price, or renegotiate the burden.
- Account for hidden debt. Quantify deferred repair, maintenance, risk, scarcity, or loss of viability.
- Assign repair obligation. Link restoration responsibility to the source of displacement.
- Repatriate burden where needed. Return cost, responsibility, or maintenance load to the origin when it was improperly exported.
- Compensate affected nodes. Provide repair, resources, agency, and recognition where burden landed.
- Redesign value flow. Align gain with responsibility and maintenance.
- Expand auditability. Make cross-boundary effects visible.
- Install externality gates. Prevent future success claims from excluding displaced burden.
- Validate field coherence. Confirm that wider-system viability improves, not only local metrics.
- Prevent recurrence. Block accounting boundaries that conceal responsibility.
A valid restoration path should reduce:
externalized burden
off-ledger cost
downstream degradation
future debt
repair displacement
local/global coherence delta
risk transfer
hidden debt
HExported Economic Incoherence is not repaired by making local success more visible.
It is repaired by making displaced burden impossible to ignore.
13. Cross-Module Links
- Economy: Core failure of local/global coherence, externalities, burden transfer, and value accounting.
- Restoration: Repair must follow the burden back to its source.
- Justice: Affected nodes need standing, remedy, recognition, and compensation.
- Contracts: Contract boundaries often hide displaced cost and risk.
- Cybernetics: Local metrics can suppress feedback from downstream instability.
- Scaling: Exported debt compounds under scale and can return as systemic failure.
- Security: Security burden can be exported to users, downstream vendors, or vulnerable nodes.
- AI Governance: AI systems can export cognitive labor, review burden, data risk, moderation cost, and meaning repair to users or society.
- Civilization Interface: Species-level or inter-system interfaces can export harm beyond the visible legitimacy boundary.
- Coherence: Coherence must be evaluated across the full field of effects.
14. Relationship to Parent / Child Modes
Production treatment: Canon / Economy Parent
This mode maps upward to:
- FM-CORE-001 — Pseudo-Coherence
- FM-CORE-002 — Hidden Debt Accumulation
- FM-REI-003 — Unbounded Extraction
- FM-C-021 — Parasitic Extraction
- FM-CORE-003 — Success Proxy Substitution
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-008 — Forced Profit
- FM-ECO-009 — Hoarding as Pseudo-Security
- FM-ECO-010 — Expansion Without Capacity
- FM-ECOX-024 — Extraction Masking Instability
- FM-ECOX-025 — Repair Starvation
- FM-ECOX-031 — Exported Economic Incoherence
- FM-ECOX-032 — Pseudo-Coherent Economic Stability
Related cross-family modes include:
- FM-CORE-001 — Pseudo-Coherence
- FM-CORE-002 — Hidden Debt Accumulation
- FM-CORE-003 — Success Proxy Substitution
- FM-C-018 — Goodhart Collapse
- FM-C-021 — Parasitic Extraction
- FM-REI-003 — Unbounded Extraction
- FM-REI-004 — Incentive Backpropagation
- FM-REI-005 — Functional Inversion
- FM-RX-004 — Capacity-Inverting Restoration
- FM-RX-005 — Victim Burden Inversion
- FM-JC-012 — Parasitic Contracting
- FM-SEC-007 — Silent Extraction / Parasitic Coupling
- FM-S-010 — Hidden Debt Explosion
- FM-S-017 — Terminal Scaling Failure
Aliases preserved from source material:
- Exported Economic Incoherence
- Economic Externalization
- Burden Export
- Local Gain Global Debt
- Local Coherence Exporting Global Incoherence
- Displaced Economic Instability
- Externalized Economic Debt
- Cost Export
- Risk Export
- Downstream Burden Transfer
15. Minimal Entry Version
Definition: Exported Economic Incoherence occurs when a system preserves or improves local economic coherence by displacing cost, instability, risk, extraction burden, repair debt, scarcity, volatility, maintenance load, or harm into another node, region, class, layer, generation, ecosystem, or future time horizon.
Signature:
local coherence↑
external burden↑
accounting boundary tightens
affected-node viability↓
repair debt↑
Au↓
H↑Restoration direction:
- name the local success
- map the accounting boundary
- trace burden pathways
- identify affected nodes
- measure local / global coherence delta
- audit power asymmetry
- account for hidden debt
- assign repair obligation
- repatriate burden where needed
- compensate affected nodes
- redesign value flow
- expand auditability
- install externality gates
- validate field coherence
- prevent recurrence
16. Machine-Readable Summary
failure_mode:
id: "FM-ECO-011"
name: "Exported Economic Incoherence"
family: "Economy"
production_treatment: "Canon / Economy Parent"
parent_modes:
- "FM-CORE-001 — Pseudo-Coherence"
- "FM-CORE-002 — Hidden Debt Accumulation"
- "FM-REI-003 — Unbounded Extraction"
primary_failure: "Local economic success, stability, efficiency, affordability, growth, or profitability depends on transferring unresolved cost, risk, repair, scarcity, harm, or instability outside the accounting boundary."
source: "UTS — Failure Modes Registry"
source_id: "FM-ECO-011"
scope_note: "Conceptual and systems-oriented; does not treat specialization, trade, delegation, outsourcing, distribution, local optimization, differentiated roles, interdependence, or boundary-setting as inherently failed."
aliases:
- "Exported Economic Incoherence"
- "Economic Externalization"
- "Burden Export"
- "Local Gain Global Debt"
- "Local Coherence Exporting Global Incoherence"
- "Displaced Economic Instability"
- "Externalized Economic Debt"
- "Cost Export"
- "Risk Export"
- "Downstream Burden Transfer"
signature:
- "local coherence↑"
- "external burden↑"
- "accounting boundary tightens"
- "affected-node viability↓"
- "repair debt↑"
- "Au↓"
- "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"
- "U8 — Environment"
state_variables:
- "Φ"
- "H"
- "O"
- "Au"
- "BΣ"
- "Γ"
- "Λ"
- "K"
- "R"
- "Ψ"
- "G"
- "D"
- "Τ"
first_gate_failure: "Externality Gate"
restoration:
- "Externality Audit"
- "Burden Repatriation"
- "Hidden Debt Accounting"
- "Repair Debt Assignment"
- "Reciprocity Restoration"
- "Affected-Node Repair"
- "Local / Global Coherence Rebalancing"
- "Risk Transfer Reversal"
- "Value Flow Redesign"
- "Restoration Obligation Fulfillment"