0. Cybernetic Scope Note

This entry is conceptual and systems-oriented.

It does not treat exchange, support, interdependence, service, contribution, labor, resource sharing, care, learning, borrowing, dependence, hosting, or asymmetric help as inherently failed. Systems depend on one another. Temporary asymmetry can be valid when it is visible, consented to, bounded, reciprocal across time, and repair-linked.

The failure begins when one node’s coherence is maintained by another node’s unaccounted depletion.

The issue is not interdependence.

The issue is unreciprocated extraction hidden as normal flow.

Parasitic Extraction occurs when a system draws from another node while obscuring the cost, consent condition, boundary violation, restoration obligation, or hidden debt produced by that draw.

1. Definition

Parasitic extraction occurs when a node, subsystem, actor, institution, interface, control layer, model, or process sustains or improves its own coherence, output, stability, power, or reward by drawing energy, attention, labor, signal, value, capacity, legitimacy, or repair resources from another node without reciprocal restoration, truthful accounting, valid consent, or affected-state repair.

The extracted resource may be:

• labor
• attention
• data
• trust
• consent
• identity
• legitimacy
• emotional load
• cognitive load
• repair capacity
• maintenance work
• interpretive bandwidth
• social credibility
• biological energy
• environmental capacity
• institutional stability
• user behavior
• symbolic meaning
• technical infrastructure
• hidden coordination work

The extracting node may appear coherent.

The source node may become depleted.

The core failure is:

extractor O↑
source capacity↓
reciprocity↓
auditability↓
H↑

Parasitic Extraction is a cybernetic resource-flow failure.

The system’s apparent stability is purchased by moving cost somewhere else and failing to account for it.

2. Core Pattern

The core pattern is:

1. A system, actor, subsystem, model, institution, or interface needs resources to maintain function, output, stability, growth, or control.
2. It draws resources from another node or field.
3. The transfer is framed as participation, service, dependency, contribution, efficiency, care, data flow, market exchange, compliance, or normal operation.
4. The cost to the source node is under-measured, hidden, minimized, delayed, or normalized.
5. Reciprocity is insufficient.
6. Consent becomes unclear, stale, coerced, bundled, or functionally unavailable.
7. The extractor receives coherence, reward, power, or legitimacy.
8. The source node carries depletion, repair burden, risk, or hidden load.
9. The system treats extractor success as net success.
10. Hidden debt accumulates in the source node, environment, or future repair field.

This failure mode often appears as:

the system is working because output is rising

or:

the source keeps providing, so the extraction must be acceptable

or:

this is normal participation, not extraction

The restorative question is:

who or what is paying the hidden cost of this coherence?

Extraction becomes parasitic when the source cannot remain whole.

3. Failure Signature

Typical signature:

resource draw↑
source capacity↓
extractor performance↑
reciprocity↓
consent clarity↓
repair burden externalized
H↑

Extended signature:

one node stabilizes while another depletes
output rises while repair burden shifts outward
efficiency improves while hidden labor grows
control appears stronger while source autonomy weakens
growth continues by consuming unmeasured capacity

Common forms include:

platforms extracting user attention while degrading user coherence
AI systems extracting data, labor, or style without repair-linked consent
organizations relying on unpaid coordination work
institutions preserving legitimacy through affected-node exhaustion
security systems offloading burden onto users
governance systems extracting compliance without support
economic systems extracting local capacity for global metrics
restoration processes requiring harmed nodes to carry repair labor
interfaces extracting trust through default settings
control systems maintaining stability by exhausting operators

The defining condition is not resource transfer.

The defining condition is that resource transfer depletes or burdens a source node while remaining under-accounted, under-consented, under-repaired, or falsely framed as coherent exchange.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: extraction preserves power, profit, growth, legitimacy, speed, or stability by externalizing cost.
• U2 — Configuration / Boundaries: source boundaries are porous, misdrawn, ignored, or configured for capture.
• U3 — Execution / Runtime: extraction occurs through everyday operation.
• U4 — Information / Truth: transfer is framed as participation, efficiency, choice, care, or success rather than depletion.
• U5 — Coordination / Time: depletion compounds over repeated cycles.
• U6 — Coherence Field: extractor success creates the feeling of system health.
• U7 — Memory / Recurrence: repeated extraction becomes normalized as baseline.
• U8 — Environment / Field: field-scale asymmetry makes source depletion invisible or distributed.

Common manifestation layers:

• U1 — Power / Budgets: the extracting node receives reward.
• U2 — Boundaries: source boundary is violated or softened.
• U3 — Execution: extraction is embedded in operations.
• U4 — Truth: extraction is mislabeled.
• U5 — Time: depletion compounds.
• U6 — Coherence Field: success masks drain.
• U8 — Environment: hidden cost disperses.

Parasitic Extraction is primarily a U1 / U2 / U4 resource-boundary failure.

The system captures flow while obscuring cost.

5. Typical Development Sequence

A common development sequence is:

1. A resource flow begins.
2. The flow appears useful or mutually acceptable.
3. One node gains more from the flow than the other can sustainably provide.
4. The asymmetry is not fully measured.
5. The extracting node becomes dependent on the flow.
6. The source node experiences increasing load, depletion, or repair burden.
7. The system normalizes the transfer.
8. Consent becomes less meaningful because exit becomes costly.
9. The extracting node optimizes around continued access.
10. The source node’s degradation becomes invisible, delayed, or blamed on the source.
11. Hidden debt accumulates.
12. Collapse appears as burnout, refusal, degradation, revolt, failure, illness, legitimacy shock, or restoration demand.

The loop often looks like:

resource access → extractor success → dependence on extraction → source depletion → hidden debt

Another common loop is:

source burden appears → framed as inefficiency → more extraction pressure → burden deepens

Parasitic Extraction becomes self-protective because the extracting system often cannot maintain its success without continuing the extraction.

6. Diagnostic Markers

Diagnostic markers include:

• Extractor performance improves while source capacity declines.
• Source nodes require recovery, repair, compensation, or exit but cannot access it.
• Resource transfer is described as voluntary while exit costs are high.
• Consent is bundled, opaque, assumed, stale, or structurally coerced.
• The system measures output but not source depletion.
• Repair burden falls on the extracted node.
• The source is blamed for reduced performance after depletion.
• The extractor depends on hidden labor, attention, data, trust, or legitimacy.
• Reciprocity is symbolic rather than material.
• Extraction is justified by efficiency, innovation, safety, care, mission, or inevitability.
• Hidden intermediaries capture value from source contributions.
• Affected nodes must repeatedly explain their burden.
• Restoration improves when extraction is reduced or repaid.
• Audit reveals cost shifting across boundaries.
• The system cannot name who pays for its coherence.

Useful diagnostics:

• Extraction Load: Measures burden drawn from source nodes.
• Reciprocity Balance: Compares transfer received to restoration returned.
• Resource Flow Integrity: Tests whether flow is truthful, consented, and repair-linked.
• Affected-Node Burden: Measures cost carried by source nodes.
• Consent Validity: Tests whether consent is informed, current, scoped, revocable, and non-coerced.
• Boundary Integrity: Tests whether source boundaries are preserved.
• Hidden Debt: Tracks unaccounted cost.
• Auditability: Determines whether extraction pathways can be traced.
• Repair Burden: Measures who must repair damage.
• Restoration Capacity: Tests whether depletion can be repaired.

7. Related Gates

Relevant gates include:

• Extraction Gate: Fails when resource draw exceeds accountable, consented, repair-linked transfer.
• Consent Gate: Fails when source participation is not validly chosen or revocable.
• Boundary Gate: Fails when source capacity is accessed without coherent boundary.
• Auditability Gate: Fails when extraction cannot be traced.
• Resource Flow Gate: Fails when value, labor, attention, data, or legitimacy moves without honest accounting.
• Restoration Gate: Fails when extracted burden is not repaired.
• Reciprocity Gate: Fails when return flow does not match cost over time.
• Hidden Debt Gate: Fails when source depletion is excluded from system accounting.

The first common gate failure is usually the Extraction Gate.

The system draws from a source without preserving that source’s wholeness.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; routes energy, attention, value, labor, data, trust, and repair resources.
• H — Hidden Debt: Accumulates where extracted cost is not counted.
• BΣ — Boundary Integrity: Protects source-node boundary and consent scope.
• Au — Auditability: Determines whether extraction can be traced.
• K — Constraint / Load: Rises on source nodes carrying extraction burden.
• R — Restoration Capacity: Required to repair depletion and rebalance transfer.
• O — Coherence: Extractor may appear coherent while source coherence declines.
• Ψ — Observation / Interface: Displays or hides extraction through interface framing.
• Γ — Selection: Selects flows that benefit extractor or system-level targets.
• Λ — Compatibility: Tests whether flow is sustainable and compatible with source capacity.
• Τ — Trajectory / Time: Reveals compounding depletion across recurrence.
• G — Gain: Amplifies extraction pressure.
• D — Damping: Can suppress source signals or slow extraction harm if properly used.

Common operator pattern:

Φ routes resource from source to extractor
Γ selects extractor output as success
O rises locally
BΣ source boundary weakens
Au fails to account transfer
K rises on source node
R is not returned
H accumulates
Τ reveals depletion

The core operator inversion is:

extracted output → system success

instead of:

resource flow → source burden audit → reciprocity + repair validation

Parasitic Extraction turns unaccounted drain into apparent coherence.

9. Related Laws and Invariants

Related Laws

• Parasitic Extraction: one system sustains itself by draining another without repair.
• Hidden Debt Accumulation: unaccounted source burden becomes deferred cost.
• Forced Coupling: source nodes are bound into extraction without valid exit.
• Boundary Collapse: source boundaries fail or are ignored.
• Auditability Collapse: transfer and burden cannot be traced.
• Consent Drift: consent decays as conditions, costs, and exit paths change.
• Unbounded Extraction: draw continues past sustainable limits.
• Success Proxy Substitution: extractor output substitutes for whole-system health.
• Pseudo-Coherence: local coherence masks global incoherence.
• Dominance Masquerading as Control: extraction is framed as governance, care, or order.

Related Invariants

• Extraction Must Be Accounted: all resource draw must be visible as cost.
• Capacity Drain Requires Consent and Repair: access to another node’s capacity requires valid consent and restoration.
• Coherence Must Not Be Exported as Debt: one node’s stability cannot be purchased by hidden burden elsewhere.
• Resource Flow Must Preserve Affected Nodes: transfer must not destroy the source.
• Dependency Must Not Hide Extraction: dependence does not erase accountability.
• Repair Burden Must Not Be Externalized: the harmed or drained node should not be forced to repair the extractor’s debt.
• Value Transfer Must Remain Auditable: movement of value, labor, data, or legitimacy must be traceable.

10. Common False Positives

Not every asymmetric flow is Parasitic Extraction.

Common false positives include:

• Temporary support with explicit restoration.
• Mutual exchange where asymmetry balances across time.
• Aid given with valid consent and no coercive dependency.
• Resource sharing with visible limits and replenishment.
• Paid labor with truthful accounting and repair capacity.
• Data use with specific, informed, revocable consent and fair return.
• Emergency extraction followed by repayment and repair.
• Dependency that preserves source boundaries.
• Unequal contribution that does not deplete the source.
• Systems that measure and repair affected-node burden.

Clarifying rule:

This is not Parasitic Extraction unless a node, subsystem, actor, institution, interface, model, or process sustains or improves itself through resource draw from another node while consent, reciprocity, cost accounting, source capacity, or repair obligation is insufficient.

11. Common False Repairs

Common false repairs include:

• thanking the source without reducing extraction
• branding extraction as partnership
• offering symbolic reciprocity
• increasing efficiency of extraction
• improving interface consent language without changing load
• paying one-time compensation while ongoing drain continues
• treating exit as available when exit cost is prohibitive
• shifting repair burden back to the source
• measuring extractor output as proof of mutual benefit
• adding dashboards that track value captured but not depletion
• framing source exhaustion as resilience failure
• replacing one source with another without repair
• extracting data to study the extraction harm
• creating restorative language around unchanged asymmetry

False repair often produces the loop:

extraction exposed → symbolic reciprocity added → extraction continues → source debt deepens

Another common loop is:

source depletion appears → source blamed as inefficient → extractor pressure rises → depletion accelerates

The repair fails because it preserves the flow while leaving the burden unrepaired.

12. Restoration Direction

Restoration requires tracing the extraction flow, naming the source burden, validating consent, rebalancing reciprocity, repairing hidden debt, and reducing or ending unsustainable draw.

Primary restoration direction:

audit extraction,
restore source boundaries,
repair transferred burden,
and rebalance resource flow

A fuller restoration path includes:

1. Name the extraction flow. Identify what is being drawn: labor, attention, data, energy, legitimacy, capacity, trust, repair, or value.
2. Name the source node. Identify who or what carries the cost.
3. Name the extractor. Identify who or what receives coherence, output, power, reward, or stability.
4. Measure source burden. Track depletion, load, hidden labor, lost capacity, repair need, and exit cost.
5. Audit consent. Test whether consent is informed, current, scoped, revocable, and non-coerced.
6. Trace value movement. Determine where resources, benefits, power, and legitimacy flow.
7. Identify hidden debt. Count unaccounted cost and delayed repair obligation.
8. Reduce extraction pressure. Lower draw to sustainable levels or stop it.
9. Restore boundaries. Protect source capacity and exit paths.
10. Rebalance reciprocity. Return value, repair, credit, capacity, or control proportionate to cost.
11. Repatriate repair burden. Move repair obligation away from depleted source nodes where appropriate.
12. Validate source recovery. Confirm affected nodes regain capacity and coherence.
13. Install recurring extraction audits. Prevent normalized drain from returning.
14. Retire extraction-dependent success claims. Stop treating extractor output as net system health until source cost is included.

A valid restoration path should reduce:

source depletion
unaccounted value capture
coerced dependency
repair burden externalization
consent drift
hidden labor
boundary leakage
reciprocity gap
hidden debt

Parasitic Extraction is not repaired by making extraction nicer.

It is repaired by restoring the source.

13. Cross-Module Links

• Cybernetics: Resource-flow and feedback failure; local coherence is maintained by hidden drain elsewhere.
• Diagnostics: Requires extraction-load, reciprocity, affected-node burden, consent-validity, and resource-flow diagnostics.
• Security: Links to silent extraction, parasitic coupling, spyware-like data capture, authorization abuse, and control through hidden dependency.
• Economy: Direct link to forced profit, unbounded extraction, dependency lock-in, and exported economic incoherence.
• Restoration: Repair fails when the burden of repair is extracted from the harmed or depleted node.
• Justice: Justice collapses when affected nodes must pay the cost of proving, repairing, or legitimizing the system.
• AI Governance: AI systems may extract user data, labor, style, attention, feedback, or social trust without consent-valid compensation or repair.
• Control Systems: Controllers can maintain stability by exhausting operators, users, or support systems.
• Interfaces: Interfaces can hide extraction behind defaults, friction, consent banners, gamification, or dependency.
• Coherence: Parasitic extraction produces local coherence and global incoherence.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry / Canon-aligned

This mode maps upward to:

• FM-CORE-002 — Hidden Debt Accumulation
• FM-CORE-008 — Forced Coupling
• FM-REI-003 — Unbounded Extraction
• FM-CORE-005 — Boundary Collapse
• FM-C-022 — Dominance Masquerading as Control

Sibling or related Cybernetics modes include:

• FM-C-003 — Hidden Debt Accumulation, Cybernetic Form
• FM-C-015 — Proxy-Relay Drift
• FM-C-018 — Goodhart Collapse
• FM-C-019 — Adversarial Reward Hacking
• FM-C-020 — Measurement Back-Action Loop
• FM-C-022 — Dominance Masquerading as Control
• FM-C-024 — Recapture After Exit

Related cross-family modes include:

• FM-SEC-007 — Silent Extraction / Parasitic Coupling
• FM-REI-003 — Unbounded Extraction
• FM-JC-012 — Parasitic Contracting
• FM-R-004 — Repair Burden Externalization
• FM-AIX-016 — Standingless Instrumentalization
• FM-ARCHX-008 — Extraction Through Empathy
• FM-ECOX-023 — Forced Profit
• FM-ECOX-024 — Extraction Masking Instability
• FM-BIOX-023 — Burden Opacity
• FM-M-005 — Extraction-Driven Optimization Collapse

Aliases preserved from source material:

• Parasitic Extraction
• Parasitic Coupling
• Silent Extraction
• Unreciprocated Extraction
• Hidden Extraction
• Extraction Without Repair
• Capacity Parasitism
• Coherence Parasitism
• Repair Resource Extraction
• Asymmetric Resource Drain

15. Minimal Entry Version

Definition: Parasitic extraction occurs when a node, subsystem, actor, institution, interface, control layer, model, or process sustains or improves its own coherence, output, stability, power, or reward by drawing energy, attention, labor, signal, value, capacity, legitimacy, or repair resources from another node without reciprocal restoration, truthful accounting, valid consent, or affected-state repair.

Signature:

resource draw↑
source capacity↓
extractor performance↑
reciprocity↓
consent clarity↓
repair burden externalized
H↑

Restoration direction:

• name the extraction flow
• name the source node
• name the extractor
• measure source burden
• audit consent
• trace value movement
• identify hidden debt
• reduce extraction pressure
• restore boundaries
• rebalance reciprocity
• repatriate repair burden
• validate source recovery
• install recurring extraction audits
• retire extraction-dependent success claims

16. Machine-Readable Summary

failure_mode:
  id: "FM-C-021"
  name: "Parasitic Extraction"
  family: "Cybernetics"
  production_treatment: "Standalone Entry / Canon-aligned"
  parent_modes:
    - "FM-CORE-002 — Hidden Debt Accumulation"
    - "FM-CORE-008 — Forced Coupling"
    - "FM-REI-003 — Unbounded Extraction"
  primary_failure: "A node, subsystem, actor, institution, interface, model, or process sustains or improves itself through resource draw from another node while consent, reciprocity, cost accounting, source capacity, or repair obligation is insufficient."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-C-021"
  scope_note: "Conceptual and systems-oriented; does not treat exchange, support, interdependence, service, contribution, labor, resource sharing, care, learning, borrowing, dependence, hosting, or asymmetric help as inherently failed."
  aliases:
    - "Parasitic Extraction"
    - "Parasitic Coupling"
    - "Silent Extraction"
    - "Unreciprocated Extraction"
    - "Hidden Extraction"
    - "Extraction Without Repair"
    - "Capacity Parasitism"
    - "Coherence Parasitism"
    - "Repair Resource Extraction"
    - "Asymmetric Resource Drain"
  signature:
    - "resource draw↑"
    - "source capacity↓"
    - "extractor performance↑"
    - "reciprocity↓"
    - "consent clarity↓"
    - "repair burden externalized"
    - "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 / Budgets"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Coherence Field"
      - "U8 — Environment"
  state_variables:
    - "Φ"
    - "H"
    - "BΣ"
    - "Au"
    - "K"
    - "R"
    - "O"
    - "Ψ"
    - "Γ"
    - "Λ"
    - "Τ"
    - "G"
    - "D"
  first_gate_failure: "Extraction Gate"
  restoration:
    - "Extraction Audit"
    - "Resource Flow Rebalancing"
    - "Consent Revalidation"
    - "Boundary Reassertion"
    - "Hidden Debt Accounting"
    - "Affected-Node Burden Repair"
    - "Reciprocity Restoration"
    - "Repair Burden Repatriation"
    - "Restoration Capacity Rebuild"