1. Short Definition

Parasitic Extraction is a failure mode where coupling consumes slack, coherence, restoration capacity, or boundary integrity from a host while suppressing visible error.

2. Canonical Definition

In UTS, Parasitic Extraction occurs when one system or node benefits by draining another system’s adaptive buffer, energy, attention, repair capacity, legitimacy, data, labor, trust, or meaning without valid reciprocity, consent, compatibility, or repair.

Canonical pattern:

extractor Φ↑
while host K↓ + R↓ + H↑ + O↓

Parasitic Extraction can remain hidden because the host may continue functioning for a time by using slack, compensating labor, suppressed signal, or hidden reserves.

3. Functional Role in UTS

Parasitic Extraction helps identify extractive relationships that appear stable or mutually beneficial on the surface.

It appears in:

• institutions
• economies
• platforms
• AI data systems
• workplaces
• relationships
• contracts
• governance systems
• ecosystems
• healthcare systems
• spiritual or care systems

It is especially dangerous when visible error remains low while the host’s restoration capacity drains.

4. Diagnostic Signatures

Parasitic Extraction active

extractor Φ↑
host σ(t)↓
host K↓
host R↓
host BΣ↓
host H↑
visible ε low

Extraction hardening

host dependency↑
exit cost↑
consent validity↓
repair demand ignored
O↓

Extraction interrupted

extraction path visible
BΣ restored
exit restored
R provisioned
hidden debt repaired
host O↑ over time

5. Canonical Distinctions

Parasitic Extraction is not exchange

Exchange can be coherence-positive when consent, reciprocity, and repair hold.

Parasitic Extraction is not support

Support increases restoration capacity.

Extraction drains it.

Parasitic Extraction is not ordinary dependency

Dependency can be valid when bounded and reciprocal.

Parasitic extraction depends on hidden drain.

Parasitic Extraction is not solved by gratitude

Gratitude language can conceal invalid extraction if material repair is absent.

6. U-Layer Mapping

7. Common Failure Patterns

8. Restoration Implications

Parasitic Extraction restoration requires identifying the extraction path and restoring host capacity.

Typical sequence:

Ξ detect asymmetric benefit
→ Μ map extraction channel
→ Au trace hidden drain
→ restore BΣ and exit
→ reduce or halt invalid coupling
→ repair extracted debt
→ provision host R and K
→ re-couple only if Λ > 0
→ Τ validate recovery

A relationship exits parasitic extraction when mutual coherence increases without hidden drain, coercive dependency, or suppressed cost.

9. Machine-Readable Summary

glossary_entry:
  id: "GL-198"
  term: "Parasitic Extraction"
  symbols:
    - "⊗"
    - "K"
    - "H"
  short_definition: "A failure mode where coupling consumes slack, coherence, restoration capacity, or boundary integrity from a host while suppressing visible error."
  term_family: "Failure Terms"
  term_class:
    - "Failure Term"
    - "Extraction Pattern"
    - "Coupling / Boundary Failure"
  canonical_pattern:
    - "extractor Φ↑ while host K↓ + R↓ + H↑ + O↓"
  diagnostic_negative:
    - "extractor Φ↑"
    - "host σ(t)↓"
    - "host K↓"
    - "host R↓"
    - "host BΣ↓"
    - "host H↑"
    - "visible ε low"
  restoration_requirements:
    - "asymmetric benefit detection"
    - "extraction channel mapping"
    - "hidden drain tracing"
    - "boundary and exit restoration"
    - "invalid coupling reduction"
    - "extracted debt repair"
    - "host restoration capacity provisioning"
    - "compatibility-verified recoupling"