FM-ECO-027 — Extraction Masking Instability

Open archive search
Archive registry entry

FM-ECO-027 — Extraction Masking Instability

schema_version: "1.0"

draftid: failure-modes-registry-economy-fm-eco-027-extraction-masking-instabilityversion: operators-v0.1updated: 2026-05-22
Archive Progress

This section can be read now; registry depth and cross-references are still being strengthened.

Foundation
Online

The section has a stable overview route and basic reader context.

Technical Layer
Online

A deeper technical overview is available.

Registry
Current

336 registry entries are available.

Cross-links
Curating

Related concepts are being connected conservatively for accuracy.


schema_version: "1.0"

id: "FM-ECO-027"

title: "FM-ECO-027 — Extraction Masking Instability"

slug: "fm-eco-027-extraction-masking-instability"

type: "failure_mode"

status: "draft"

version: "0.1.0"

last_updated: "2026-06-19"

summary: "Extraction Masking Instability occurs when an economic system maintains apparent stability, profitability, affordability, growth, or continuity by extracting hidden capacity, labor, resilience, time, attention, risk absorption, maintenance deferral, or repair burden from affected nodes, thereby concealing the instability that the extraction itself intensifies."

canonical_url: "/archive/failure-modes/registry/economy/fm-eco-027-extraction-masking-instability"

citation_id: "FM-ECO-027-v0-1-0"

canon:

tier: "registry"

state: "draft"

source: "UTS — Failure Modes Registry"

source_id: "FM-ECO-027"

legacy_ids:

  • "FM-ECOX-024"

classification:

family: "failure-modes"

module: "economy"

module_group: "economy"

density: "advanced-reference"

audience:

  • "UTS readers"
  • "economic systems researchers"
  • "cybernetics researchers"
  • "justice researchers"
  • "restoration researchers"
  • "security researchers"
  • "AI governance researchers"
  • "platform researchers"
  • "coherence researchers"
  • "machine readers"

tags:

  • "failure-modes"
  • "economy"
  • "extraction-masking-instability"
  • "fm-eco-027-extraction-masking-instability"
  • "fm-ecox-024-extraction-masking-instability"
  • "extraction"
  • "instability"
  • "false-stability"
  • "hidden-capacity"
  • "repair-debt"
  • "forced-profit"
  • "hidden-debt"
  • "coherence"

aliases:

  • "Extraction Masking Instability"
  • "Extraction-Masked Instability"
  • "Extractive Stability Mask"
  • "False Stability Through Extraction"
  • "Stability by Extraction"
  • "Profitability by Burden Transfer"
  • "Hidden Capacity Extraction"
  • "Resilience Extraction"
  • "Instability Concealed by Extraction"
  • "Extractive False Calm"

related:

laws:

  • "Parasitic Extraction"
  • "Forced Profit"
  • "False Calm"
  • "Pseudo-Coherence"
  • "Hidden Debt Accumulation"
  • "Exported Economic Incoherence"
  • "Victim Burden Inversion"
  • "Capacity-Inverting Restoration"
  • "Economic Leakiness"
  • "Dependency Lock-In"
  • "Goodhart Collapse"
  • "Suppressed Oscillation / False Calm"

invariants:

  • "Stability Must Not Depend on Hidden Extraction"
  • "Profit Must Not Consume Repair Capacity"
  • "Local Coherence Must Bound Extractive Gain"
  • "Extracted Capacity Must Remain Auditable"
  • "Burden Transfer Must Be Accounted"
  • "Resilience Cannot Be Treated as Free Input"
  • "Visible Stability Must Include Affected-Node Viability"

operators:

  • "Φ — Flow / Resource Movement"
  • "H — Hidden Debt"
  • "K — Constraint / Load"
  • "R — Restoration Capacity"
  • "O — Coherence"
  • "Au — Auditability"
  • "Ψ — Observation / Interface"
  • "G — Gain"
  • "D — Damping"
  • "BΣ — Boundary Integrity"
  • "Γ — Selection"
  • "Λ — Compatibility"
  • "Τ — Trajectory / Time"

gates:

  • "Extraction Gate"
  • "Stability Reality Gate"
  • "Affected-Node Viability Gate"
  • "Burden Accounting Gate"
  • "Restoration Gate"
  • "Profit Legitimacy Gate"
  • "Auditability Gate"
  • "Capacity Gate"
  • "Local Coherence Gate"

diagnostics:

  • "Extraction Load"
  • "False Stability"
  • "Affected-Node Viability"
  • "Hidden Capacity Draw"
  • "Repair Capacity"
  • "Burden Transfer"
  • "Local / Global Coherence Delta"
  • "Hidden Debt"
  • "Auditability"
  • "Local Coherence"

failure_modes:

  • "FM-ECO-005 — Economic Leakiness"
  • "FM-ECO-008 — Forced Profit"
  • "FM-ECO-011 — Exported Economic Incoherence"
  • "FM-ECO-020 — Risk Model Theater"
  • "FM-ECO-026 — Dependency Lock-In"
  • "FM-ECO-028 — Repair Starvation"
  • "FM-ECO-032 — Pseudo-Coherent Economic Stability"
  • "FM-C-006 — Suppressed Oscillation / False Calm"
  • "FM-C-021 — Parasitic Extraction"
  • "FM-CORE-001 — Pseudo-Coherence"
  • "FM-CORE-002 — Hidden Debt Accumulation"
  • "FM-RX-005 — Victim Burden Inversion"

restoration_arcs:

  • "Extraction Load Audit"
  • "False Stability Exposure"
  • "Affected-Node Viability Restoration"
  • "Hidden Capacity Accounting"
  • "Burden Repatriation"
  • "Repair Capacity Replenishment"
  • "Profit Legitimacy Review"
  • "Extraction Throttling"
  • "Hidden Debt Repair"
  • "Local Coherence Restoration"

modules:

  • "Economy"
  • "Cybernetics"
  • "Restoration"
  • "Justice"
  • "Scaling"
  • "Security"
  • "AI Governance"
  • "Diagnostics"
  • "Platforms"
  • "Coherence"

navigation:

order: 1327

parent: "failure-modes"

visible: true

provenance:

created_from: "failure-mode-registry-production"

source_thread: "UTS Failure Modes Registry production"

source_file: "content/archive/failure-modes/registry/economy/fm-eco-027-extraction-masking-instability.md"

legacy_source_file: "content/archive/failure-modes/registry/economy/fm-ecox-024-extraction-masking-instability.md"

notes: "Unified from former FM-ECOX-024 into continuous Economy namespace. Domain expression focused on apparent stability, profitability, affordability, growth, or continuity being preserved by extracting hidden labor, resilience, time, attention, capacity, risk absorption, deferred maintenance, or repair burden from affected nodes."

entry:

failure_mode_id: "FM-ECO-027"

failure_family: "Economy"

production_treatment: "Domain Expression"

legacy_ids:

  • "FM-ECOX-024"

parent_modes:

  • "FM-C-021 — Parasitic Extraction"
  • "FM-ECO-008 — Forced Profit"
  • "FM-C-006 — Suppressed Oscillation / False Calm"
  • "FM-CORE-001 — Pseudo-Coherence"
  • "FM-CORE-002 — Hidden Debt Accumulation"

first_gate_failure: "Extraction Gate"

primary_hidden_debt: "Hidden debt accumulates when apparent economic stability is maintained by consuming unpriced capacity, unpaid labor, deferred repair, resilience reserves, attention, risk absorption, or local viability from affected nodes."

primary_inversion: "Extraction becomes stability; the system treats continued operation, profitability, or calm as evidence of viability while the apparent stability depends on draining the nodes that sustain it."

primary_boundary_pattern: "The boundary between genuine stability and extracted endurance collapses; the system cannot distinguish a healthy operating state from a state temporarily stabilized by hidden capacity draw."

primary_signature: "Visible stability persists; extraction load rises; affected nodes absorb hidden burden; repair capacity falls; instability is delayed or displaced; hidden debt accumulates until the extracted layer can no longer buffer the system."


FM-ECO-027 — Extraction Masking Instability

Status: Draft

Archive Type: Failure Mode

System: Universal Theory Stack

Parent: Failure Modes

Canon Tier: Registry

Registry: Failure Modes Registry

Entry ID: FM-ECO-027

Legacy ID: FM-ECOX-024

Family: Economy

Production Treatment: Domain Expression

Parent Modes: FM-C-021 — Parasitic Extraction; FM-ECO-008 — Forced Profit; FM-C-006 — Suppressed Oscillation / False Calm; FM-CORE-001 — Pseudo-Coherence; FM-CORE-002 — Hidden Debt Accumulation


0. Economic Scope Note

This entry is conceptual and systems-oriented.

It does not treat all extraction, surplus, efficiency, margin, cost control, productivity, reserve use, labor contribution, risk-sharing, or capacity draw as inherently failed.

Economic systems often draw from capacity.

Capacity use can be coherent when it is:

  • consent-valid
  • reciprocal
  • compensated
  • bounded
  • visible
  • restorable
  • phase-aware
  • capacity-aware
  • not dependency-forced
  • not repair-starving
  • not hiding instability
  • compatible with affected-node viability

The failure begins when extraction hides instability.

The issue is not capacity use.

The issue is apparent stability produced by draining unacknowledged support layers.

Extraction Masking Instability occurs when a system looks stable because another node, layer, class, workforce, community, infrastructure, ecosystem, or future horizon is absorbing the instability off-ledger.


1. Definition

Extraction Masking Instability occurs when an economic system maintains apparent stability, profitability, affordability, growth, or continuity by extracting hidden capacity, labor, resilience, time, attention, risk absorption, maintenance deferral, or repair burden from affected nodes, thereby concealing the instability that the extraction itself intensifies.

The extracted buffer may include:

  • unpaid labor
  • underpaid labor
  • overtime
  • emotional labor
  • household support
  • user attention
  • user correction work
  • community resilience
  • supplier risk absorption
  • deferred maintenance
  • worker health
  • local infrastructure
  • ecological absorption
  • future budgets
  • customer patience
  • emergency reserves
  • informal workarounds
  • technical debt
  • shadow administration
  • unpaid moderation
  • caregiver time
  • downstream repair
  • cognitive review
  • data labor
  • reputation labor

The core failure is:

text id="vq86s6"Scroll
visible stability↑
hidden extraction↑
affected-node capacity↓
repair capacity↓
H↑

Extraction Masking Instability is not merely exploitation.

It is exploitation functioning as a stabilizer that hides the system’s real instability.


2. Core Pattern

The core pattern is:

  1. A system faces instability, cost pressure, capacity shortage, maintenance debt, volatility, or under-delivery.
  2. Instead of resolving the instability, the system extracts hidden capacity from another layer.
  3. The visible system stabilizes temporarily.
  4. Official metrics show continuity, affordability, productivity, profitability, or resilience.
  5. The extracted layer absorbs the cost.
  6. Because the visible system appears stable, repair is postponed.
  7. The extracted layer loses viability.
  8. The instability deepens underneath the visible surface.
  9. More extraction is required to preserve the same appearance of stability.
  10. Hidden debt accumulates until the buffer fails or withdraws.

This failure often appears as:

text id="6yrbfb"Scroll
the system is still functioning

while the hidden truth may be:

text id="m4i1nx"Scroll
because an invisible layer is carrying the instability

or:

text id="g182o5"Scroll
costs have been controlled

while the overlooked condition is:

text id="hbp35b"Scroll
costs were displaced into unpriced burden

The restorative question is:

text id="oeiwib"Scroll
whose capacity is being consumed to make this look stable?

Extraction Masking Instability turns hidden endurance into false resilience.


3. Failure Signature

Typical signature:

text id="8tfiy6"Scroll
apparent stability↑
extraction load↑
affected-node viability↓
repair delay↑
false calm↑
H↑

Extended signature:

text id="lxcwx3"Scroll
profits stay stable because labor absorbs volatility
prices stay low because maintenance is deferred
services continue because users perform unpaid support
institutions function because households absorb administrative burden
platforms scale because communities absorb moderation costs
AI tools appear productive because users perform correction and verification labor
infrastructure appears stable because repairs are delayed

Common forms include:

text id="ammm8p"Scroll
a company maintains margin by understaffing and relying on unpaid overtime
a public service appears affordable because families absorb care burden
a platform appears scalable because users moderate, correct, tag, or report for free
a supply chain appears resilient because suppliers absorb volatility
a city appears fiscally stable while infrastructure maintenance is deferred
an AI system appears accurate because users constantly verify and repair outputs
a healthcare system appears functional because workers and patients absorb scheduling, documentation, and navigation burden
a contractor appears efficient because downstream teams absorb rework

The defining condition is not that some burden exists.

The defining condition is that hidden burden is necessary to preserve the appearance of stability.


4. Primary U-Layer Origin

Common origin layers:

  • U1 — Power / Budgets: profit, budget, affordability, valuation, or political pressure prevents visible cost recognition.
  • U2 — Configuration / Boundaries: accounting boundaries exclude extracted capacity and displaced burden.
  • U3 — Execution / Runtime: operations depend on unpaid, hidden, delayed, or offloaded work.
  • U4 — Information / Truth: stability metrics substitute for viability truth.
  • U5 — Coordination / Time: maintenance and repair are deferred into later periods.
  • U6 — Coherence Field: calm, continuity, and profitability create legitimacy aura.
  • U7 — Memory / Recurrence: hidden extraction becomes normalized operating procedure.
  • U8 — Environment / Field: external scarcity, competition, or institutional pressure rewards visible stability.

Common manifestation layers:

  • U1 — Power: extraction pressure protects official stability.
  • U2 — Boundaries: burden falls outside accounting.
  • U3 — Execution: hidden labor and capacity sustain operations.
  • U4 — Truth: visible stability substitutes for full-state truth.
  • U5 — Time: instability is deferred.
  • U6 — Field: false calm masks degradation.
  • U8 — Environment: field absorbs burden until thresholds break.

Extraction Masking Instability is primarily a U2 accounting-boundary / U4 truth-substitution failure, driven by U1 gain pressure.

The system narrows visibility until extraction looks like stability.


5. Typical Development Sequence

A common development sequence is:

  1. A system develops instability or capacity shortage.
  2. Direct repair would be costly, visible, slow, or legitimacy-threatening.
  3. The system quietly shifts burden onto less visible nodes.
  4. Visible performance stabilizes.
  5. Decision-makers interpret the stability as evidence that the system is viable.
  6. Repair is deferred.
  7. The hidden burden increases.
  8. Affected nodes adapt, overwork, absorb, compensate, or silently degrade.
  9. The adaptation becomes expected.
  10. The system builds plans on top of the extracted capacity.
  11. The hidden layer weakens.
  12. A later failure appears sudden, even though it was being buffered for a long time.

The loop often looks like:

text id="10auou"Scroll
instability → hidden extraction → visible stability → repair delay → deeper instability

Another common loop is:

text id="y4m8oj"Scroll
cost pressure → burden transfer → profit stability → extraction normalized → capacity collapse

Extraction Masking Instability becomes self-reinforcing when the extracted layer’s endurance is misread as proof that no repair is needed.


6. Diagnostic Markers

Diagnostic markers include:

  • Official stability persists while affected nodes report exhaustion, overload, or degradation.
  • Cost savings coincide with increased unpaid or invisible work.
  • Profit, affordability, or continuity depends on deferred maintenance.
  • User, worker, supplier, household, or community burden rises without appearing in the ledger.
  • The system cannot explain how work is actually being completed.
  • Informal workarounds become essential.
  • Service continuity depends on people exceeding role boundaries.
  • The visible system has low slack while hidden layers provide emergency buffering.
  • Quality is maintained through rework outside official process.
  • The system celebrates resilience while refusing to fund repair.
  • Collapse appears sudden when the hidden buffer stops absorbing.
  • Restoration improves when extracted burden is surfaced, compensated, or removed.

Useful diagnostics:

  • Extraction Load: Measures hidden capacity draw.
  • False Stability: Tests whether visible stability depends on off-ledger burden.
  • Affected-Node Viability: Checks whether supporting nodes remain healthy enough to continue.
  • Hidden Capacity Draw: Identifies time, labor, attention, maintenance, or resilience consumed invisibly.
  • Repair Capacity: Measures whether extraction is starving restoration.
  • Burden Transfer: Tracks where instability is being moved.
  • Local / Global Coherence Delta: Compares visible node stability to field degradation.
  • Hidden Debt: Tracks accumulated unacknowledged cost.
  • Auditability: Determines whether hidden burden can be traced.
  • Local Coherence: Tests whether stability improves actual affected nodes.

Relevant gates include:

  • Extraction Gate: Fails when capacity is drawn without visibility, reciprocity, or restoration.
  • Stability Reality Gate: Fails when visible stability is not tested against hidden burden.
  • Affected-Node Viability Gate: Fails when supporting nodes degrade under extraction.
  • Burden Accounting Gate: Fails when extracted capacity is not counted.
  • Restoration Gate: Fails when repair is postponed because extraction preserves the surface.
  • Profit Legitimacy Gate: Fails when profit depends on off-ledger burden.
  • Auditability Gate: Fails when the stabilizing extraction path is hidden.
  • Capacity Gate: Fails when the real capacity source is unmeasured.
  • Local Coherence Gate: Fails when apparent stability does not improve affected nodes.

The first common gate failure is usually the Extraction Gate.

The system draws from hidden capacity before testing whether the draw is legitimate, sustainable, or repair-bound.


Relevant operators include:

  • Φ — Flow / Resource Movement: Routes value upward and burden downward or outward.
  • H — Hidden Debt: Accumulates through unacknowledged extracted burden.
  • K — Constraint / Load: Rises in affected nodes absorbing instability.
  • R — Restoration Capacity: Declines when extraction consumes repair capacity.
  • O — Coherence: Appears high at the visible node while falling elsewhere.
  • Au — Auditability: Reveals or hides the extraction pathway.
  • Ψ — Observation / Interface: Determines whether hidden burden is visible.
  • G — Gain: Amplifies extraction pressure through profit, cost, or optics.
  • D — Damping: Should limit extraction before buffer collapse.
  • BΣ — Boundary Integrity: Protects supporting nodes from being consumed.
  • Γ — Selection: Selects which node absorbs instability.
  • Λ — Compatibility: Tests whether burden transfer fits affected-node capacity.
  • Τ — Trajectory / Time: Tracks deferred instability and delayed collapse.

Common operator pattern:

text id="95xezi"Scroll
instability appears
G pressure preserves visible performance
Γ selects hidden burden path
Φ routes load to affected nodes
K rises there
O remains high at visible node
Au fails to expose extraction
R is starved
H accumulates until buffer failure

The core operator inversion is:

text id="1vfikc"Scroll
continued operation → stability

instead of:

text id="ufkccu"Scroll
continued operation + no hidden capacity drain + repair capacity + affected-node viability → stability

Extraction Masking Instability turns endurance into false system health.


  • Parasitic Extraction: one node draws viability from another without sufficient restoration.
  • Forced Profit: profit is preserved through imposed burden.
  • False Calm: visible calm hides suppressed instability.
  • Pseudo-Coherence: local stability hides wider incoherence.
  • Hidden Debt Accumulation: off-ledger burden stores future cost.
  • Exported Economic Incoherence: instability is displaced outside the accounting boundary.
  • Victim Burden Inversion: affected nodes carry the cost of the system’s failure.
  • Capacity-Inverting Restoration: repair demand is pushed onto burdened nodes.
  • Economic Leakiness: value escapes while burden remains.
  • Dependency Lock-In: captive nodes continue absorbing burden.
  • Goodhart Collapse: stability metrics become targets.
  • Suppressed Oscillation / False Calm: pressure suppresses visible signals of instability.
  • Stability Must Not Depend on Hidden Extraction: true stability cannot require invisible depletion.
  • Profit Must Not Consume Repair Capacity: gain is incoherent if it drains restoration.
  • Local Coherence Must Bound Extractive Gain: affected-node viability constrains extraction.
  • Extracted Capacity Must Remain Auditable: hidden support layers must be visible.
  • Burden Transfer Must Be Accounted: cost cannot disappear by crossing a boundary.
  • Resilience Cannot Be Treated as Free Input: endurance must not be consumed without repair.
  • Visible Stability Must Include Affected-Node Viability: stability must be field-valid.

10. Common False Positives

Not every hidden contribution is Extraction Masking Instability.

Common false positives include:

  • Voluntary extra effort that is bounded and restored.
  • Temporary emergency burden-sharing with explicit compensation.
  • Resilience reserves used with replenishment.
  • Maintenance deferral paired with funded repair schedule.
  • Community contribution with consent, reciprocity, and rest.
  • User correction that is optional, compensated, or genuinely collaborative.
  • Supplier risk-sharing that is priced and capacity-matched.
  • Workarounds used briefly while root cause repair is active.
  • Cost control that reduces waste without transferring burden.
  • Stability achieved through real capacity increases.
  • Redundancy use that remains visible and replenished.
  • Extraction that is accounted, limited, and repair-bound.

Clarifying rule:

This is not Extraction Masking Instability unless apparent stability, profitability, affordability, growth, or continuity depends on hidden extraction of capacity, labor, resilience, time, attention, risk absorption, deferred maintenance, or repair burden from affected nodes.


11. Common False Repairs

Common false repairs include:

  • praising resilience instead of reducing extraction
  • giving symbolic recognition without compensation or load reduction
  • improving reporting while leaving burden off-ledger
  • redistributing extraction to a different hidden layer
  • automating the visible process while increasing user correction burden
  • calling unpaid work community engagement
  • funding growth while leaving maintenance unfunded
  • offering wellness support while workload remains extractive
  • adding feedback channels that require more unpaid attention
  • providing temporary bonuses while preserving structural overload
  • reclassifying hidden labor as participation
  • using crisis language to justify continued extraction
  • measuring satisfaction while suppressing burden accounting
  • using AI to hide service degradation while users absorb correction work
  • treating buffer collapse as individual failure

False repair often produces the loop:

text id="p73oxs"Scroll
hidden extraction exposed → recognition added → extraction continues → buffer weakens

Another common loop is:

text id="n2dk2q"Scroll
instability masked by burden transfer → burdened layer degrades → new layer absorbs burden

The repair fails because it preserves visible stability while moving or beautifying the extraction.


12. Restoration Direction

Restoration requires exposing hidden extraction, mapping who is carrying the instability, reducing or compensating the burden, replenishing depleted capacity, restoring repair pathways, and replacing extractive false stability with real coherence.

Primary restoration direction:

text id="n8gji2"Scroll
expose hidden extraction,
restore affected-node capacity,
account for burden,
and rebuild stability without depletion

A fuller restoration path includes:

  1. Name the visible stability. Identify the profitability, affordability, continuity, service level, growth, or calm being preserved.
  2. Map hidden capacity sources. Identify whose labor, time, attention, resilience, maintenance, risk absorption, or repair capacity is being consumed.
  3. Measure extraction load. Determine how much burden has been shifted.
  4. Test affected-node viability. Determine whether the supporting layer remains coherent.
  5. Trace burden transfer. Identify how instability moves from visible system to hidden layer.
  6. Audit compensation and reciprocity. Determine whether extracted capacity is acknowledged, paid, replenished, or repaired.
  7. Expose false stability. Reclassify apparent stability as extracted stability where appropriate.
  8. Reduce extraction pressure. Lower workload, burden, risk, delay, or off-ledger dependency.
  9. Replenish depleted capacity. Restore slack, maintenance, rest, staffing, infrastructure, funds, or repair ability.
  10. Repair extraction debt. Compensate or restore affected nodes for prior hidden burden.
  11. Reprice or redesign flow. Align visible cost with real cost.
  12. Install extraction gates. Prevent hidden capacity draw from being counted as stability.
  13. Restore auditability. Track who carries burden and who benefits.
  14. Validate field stability. Confirm stability holds without hidden depletion.
  15. Prevent recurrence. Block future metrics that reward extraction-masked performance.

A valid restoration path should reduce:

text id="4osg9t"Scroll
hidden extraction
off-ledger burden
false stability
affected-node depletion
repair starvation
maintenance deferral
capacity draw
burden displacement
H

Extraction Masking Instability is not repaired by making instability invisible in a more elegant way.

It is repaired by removing the need for hidden extraction to keep the system standing.


  • Economy: Core failure of profit, affordability, productivity, continuity, and stability being preserved through hidden burden.
  • Cybernetics: Links directly to false calm, suppressed oscillation, and misread stability signals.
  • Restoration: Repair is starved when hidden extraction is treated as normal operation.
  • Justice: Affected nodes need recognition, standing, compensation, and burden repatriation.
  • Scaling: At scale, hidden extraction can become systemic debt and later collapse.
  • Security: Security systems can appear stable by exporting vigilance, proof, or recovery burden to users.
  • AI Governance: AI systems can appear effective by extracting user correction, data labor, attention, moderation, and verification work.
  • Diagnostics: Requires extraction-load, false-stability, affected-node viability, hidden-debt, and auditability diagnostics.
  • Platforms: Platform stability often depends on user, creator, moderator, vendor, or worker burden.
  • Coherence: Coherence requires stability that does not consume its supporting nodes.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression

This mode maps upward to:

  • FM-C-021 — Parasitic Extraction
  • FM-ECO-008 — Forced Profit
  • FM-C-006 — Suppressed Oscillation / False Calm
  • FM-CORE-001 — Pseudo-Coherence
  • FM-CORE-002 — Hidden Debt Accumulation

Sibling or related Economy modes include:

  • FM-ECO-005 — Economic Leakiness
  • FM-ECO-008 — Forced Profit
  • FM-ECO-011 — Exported Economic Incoherence
  • FM-ECO-020 — Risk Model Theater
  • FM-ECO-026 — Dependency Lock-In
  • FM-ECO-028 — Repair Starvation
  • FM-ECO-029 — Growth Theater
  • FM-ECO-032 — Pseudo-Coherent Economic Stability

Related cross-family modes include:

  • FM-C-006 — Suppressed Oscillation / False Calm
  • FM-C-021 — Parasitic Extraction
  • FM-C-022 — Dominance Masquerading as Control
  • FM-CORE-001 — Pseudo-Coherence
  • FM-CORE-002 — Hidden Debt Accumulation
  • FM-REI-003 — Unbounded Extraction
  • FM-RX-004 — Capacity-Inverting Restoration
  • FM-RX-005 — Victim Burden Inversion
  • FM-SEC-007 — Silent Extraction / Parasitic Coupling
  • FM-JC-012 — Parasitic Contracting
  • FM-AIX-016 — Standingless Instrumentalization
  • FM-AIX-022 — Dependency Loop Formation

Aliases preserved from source material:

  • Extraction Masking Instability
  • Extraction-Masked Instability
  • Extractive Stability Mask
  • False Stability Through Extraction
  • Stability by Extraction
  • Profitability by Burden Transfer
  • Hidden Capacity Extraction
  • Resilience Extraction
  • Instability Concealed by Extraction
  • Extractive False Calm

Legacy source preserved:

yaml id="0njut8"Scroll
legacy_ids:
  - "FM-ECOX-024"
deprecated_source_ids:
  - "FM-ECOX-024"
source_aliases:
  - "Economy Extended Entry 024"

15. Minimal Entry Version

Definition: Extraction Masking Instability occurs when an economic system maintains apparent stability, profitability, affordability, growth, or continuity by extracting hidden capacity, labor, resilience, time, attention, risk absorption, maintenance deferral, or repair burden from affected nodes, thereby concealing the instability that the extraction itself intensifies.

Signature:

text id="urvy4h"Scroll
apparent stability↑
extraction load↑
affected-node viability↓
repair delay↑
false calm↑
H↑

Restoration direction:

  • name the visible stability
  • map hidden capacity sources
  • measure extraction load
  • test affected-node viability
  • trace burden transfer
  • audit compensation and reciprocity
  • expose false stability
  • reduce extraction pressure
  • replenish depleted capacity
  • repair extraction debt
  • reprice or redesign flow
  • install extraction gates
  • restore auditability
  • validate field stability
  • prevent recurrence

16. Machine-Readable Summary

yaml id="p9vq6c"Scroll
failure_mode:
  id: "FM-ECO-027"
  name: "Extraction Masking Instability"
  family: "Economy"
  production_treatment: "Domain Expression"
  legacy_ids:
    - "FM-ECOX-024"
  parent_modes:
    - "FM-C-021 — Parasitic Extraction"
    - "FM-ECO-008 — Forced Profit"
    - "FM-C-006 — Suppressed Oscillation / False Calm"
    - "FM-CORE-001 — Pseudo-Coherence"
    - "FM-CORE-002 — Hidden Debt Accumulation"
  primary_failure: "Apparent stability, profitability, affordability, growth, or continuity depends on hidden extraction of capacity, labor, resilience, time, attention, risk absorption, deferred maintenance, or repair burden from affected nodes."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-ECO-027"
  deprecated_source_ids:
    - "FM-ECOX-024"
  scope_note: "Conceptual and systems-oriented; does not treat all extraction, surplus, efficiency, margin, cost control, productivity, reserve use, labor contribution, risk-sharing, or capacity draw as inherently failed."
  aliases:
    - "Extraction Masking Instability"
    - "Extraction-Masked Instability"
    - "Extractive Stability Mask"
    - "False Stability Through Extraction"
    - "Stability by Extraction"
    - "Profitability by Burden Transfer"
    - "Hidden Capacity Extraction"
    - "Resilience Extraction"
    - "Instability Concealed by Extraction"
    - "Extractive False Calm"
  signature:
    - "apparent stability↑"
    - "extraction load↑"
    - "affected-node viability↓"
    - "repair delay↑"
    - "false calm↑"
    - "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"
    - "K"
    - "R"
    - "O"
    - "Au"
    - "Ψ"
    - "G"
    - "D"
    - "BΣ"
    - "Γ"
    - "Λ"
    - "Τ"
  first_gate_failure: "Extraction Gate"
  restoration:
    - "Extraction Load Audit"
    - "False Stability Exposure"
    - "Affected-Node Viability Restoration"
    - "Hidden Capacity Accounting"
    - "Burden Repatriation"
    - "Repair Capacity Replenishment"
    - "Profit Legitimacy Review"
    - "Extraction Throttling"
    - "Hidden Debt Repair"
    - "Local Coherence Restoration"