0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Parasitic Extraction Recovery repairs systems where a coupling consumes slack, coherence, attention, labor, data, money, legitimacy, meaning, restoration capacity, or boundary integrity while visible error remains low or difficult to classify.

It applies when a relation, interface, institution, contract, AI system, economic dependency, workflow, symbolic structure, or governance process appears functional but is quietly draining the host system.

This arc repairs parasitic extraction by:

• detecting the extraction hook;
• mapping the hidden drain path;
• distinguishing compatibility from dependency;
• reducing or ending invalid coupling;
• restoring boundary integrity;
• restoring auditability and feedback;
• repairing the host or affected node;
• rebuilding slack and restoration capacity;
• preventing recapture through proxy, dependency, emergency, symbolic, or interface relays;
• validating that extraction does not resume under a new form.

Parasitic Extraction Recovery is the canonical arc for restoring host coherence after silent, low-visibility, or normalized extraction.

1.2 Core Restoration Function

This arc restores host coherence by identifying extraction hooks, reducing invalid coupling, restoring auditability and boundary integrity, repairing drained capacity, and validating that the host no longer loses slack, restoration capacity, or coherence through the parasitic pathway.

Parasitic Extraction Recovery prevents systems from mistaking low visible error for safe coupling.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• coherence declines while visible incidents remain low;
• slack, attention, labor, energy, data, money, legitimacy, or repair capacity is being consumed by a coupling;
• a dependency appears useful but reduces the host’s ability to recover;
• participation continues through convenience, dependency, fear, role pressure, or hidden cost;
• the system feels stable but capacity slowly drains;
• an interface, platform, institution, contract, AI tool, or relation captures more value than it returns;
• boundary signals are weak, delayed, normalized, or dismissed;
• hidden labor or hidden maintenance is required to keep the coupling working;
• attempts to exit trigger snap-back, penalty, confusion, guilt, identity pressure, or loss of critical access;
• the extracting structure is protected by legitimacy, utility, symbolic value, or security language.

Examples:

• an AI tool quietly consumes user context, attention, data, or agency while appearing helpful;
• a platform creates dependency through memory, convenience, lock-in, or workflow capture;
• an institution depends on unpaid emotional, procedural, or legitimacy labor from affected nodes;
• an economic relation extracts hidden labor or externalized cost while showing productivity;
• a security tool creates constant review burden while reducing real capacity;
• a meaning system consumes sovereignty through symbolic obligation while appearing supportive.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is cascading and emergency stabilization is required first;
• the issue is ordinary load rather than extraction;
• coupling is compatible and reciprocal after audit;
• boundary repair alone is sufficient;
• the extraction path is already known and safe decoupling should begin immediately;
• the system lacks observability and must restore visibility first;
• extraction language is being used vaguely without traceable drain;
• the arc would expose affected nodes without protection;
• the system refuses to reduce or interrupt the extracting coupling.

Parasitic Extraction Recovery must not become extraction-label theater.

2.3 Required Preconditions

Before this arc begins, the following must be true:

If required preconditions fail:

Arc cannot validly begin.

The system must return to emergency stabilization, observability restoration, audit surface expansion, boundary reconstitution, controlled decoupling, or safe decoupling.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

A coupling is parasitic when it consumes host coherence or restoration capacity faster than it returns compatible coherence gain.

4. Restoration Objective

4.1 Canonical Objective

Restore host coherence by identifying extraction hooks, reducing invalid coupling, restoring boundaries, rebuilding slack and restoration capacity, and preventing recapture.

Formal objective:

hook surface identified
Λ tested
d⊗/dt < 0 where extractive
BΣ ↑
K / σ ↑
R_host ↑
H_extraction ↓
O_host ↑
recapture risk ↓
recurrence ↓

Expanded objective:

Convert a hidden drain into a visible repair pathway, reduce the coupling that enables extraction, repair the host, and validate that the system no longer depends on being drained to remain functional.

4.2 Non-Goals

This arc does not aim to:

• demonize all dependency;
• reject all coupling;
• collapse useful reciprocity;
• name extraction without proving a drain path;
• punish through abrupt abandonment;
• remove support without successor capacity;
• treat inconvenience as extraction;
• confuse ordinary maintenance with parasitic burden;
• restore productivity without restoring host capacity;
• preserve extraction under softer language.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Μ extraction map → Au value / drain trace → Ξ extraction inversion detection → Λ compatibility reassessment → ⊗↓ coupling reduction → Π boundary repair → Σ anti-recapture lock → ℛ host restoration → Τ recapture validation

Universal grammar alignment:

Σ + Θ → Π → Au↑ → Λ test → ⊗↓ → ℛ(host) → Τ → Temporal Proof

Parasitic Extraction Recovery may route into Hidden Debt Reduction, Safe Decoupling, Boundary Reconstitution, Economic Clearance, Interface Re-Legitimation, or Sovereignty Safeguard Restoration.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is drain-gated, boundary-gated, and recapture-gated.

Visible error may rise temporarily when extraction is interrupted. This can be a valid signal if hidden burden was previously suppressing visible error.

The sequence must distinguish:

reciprocal coupling
ordinary maintenance cost
dependency
coercive dependency
parasitic extraction
silent extraction
post-exit recapture

The following steps cannot be skipped:

extraction map
value / drain trace
compatibility reassessment
coupling reduction
boundary repair
host restoration
recapture validation

If the host looks more unstable at first but slack begins recovering, the arc may be working.

If visible calm returns while host capacity keeps falling, the arc has failed.

6. Restoration Phases

Phase 0 — Detect Extraction Signal

Purpose: Identify evidence that a coupling is draining coherence or capacity.

Actions:

• identify declining slack, attention, labor, energy, data, money, legitimacy, or repair capacity;
• identify low-visible-error drain patterns;
• identify hidden work required to maintain the coupling;
• identify host depletion;
• identify dependency pressure;
• identify who benefits and who carries the cost.

Validation:

extraction signal visible
host depletion suspected or observable
benefit / burden asymmetry named

Phase 1 — Map Extraction Hook

Purpose: Identify how the extraction is attached.

Actions:

• map interface hooks;
• map dependency hooks;
• map permission hooks;
• map role or identity hooks;
• map contract hooks;
• map symbolic or legitimacy hooks;
• map data, attention, labor, or economic hooks.

Validation:

hook surface mapped
coupling pathway visible
dependency mechanism traceable

Phase 2 — Trace Value and Burden Flow

Purpose: Make the extraction path auditable.

Actions:

• trace what is taken;
• trace what is returned;
• trace what is hidden;
• trace what burden is exported;
• trace what repair capacity is consumed;
• trace who can exit and who cannot;
• trace where Φ improves while host O declines.

Validation:

Au_extraction ↑
value / burden asymmetry visible
Φ/O divergence identified where present

Phase 3 — Reassess Compatibility

Purpose: Determine whether the coupling is valid, reciprocal, or extractive.

Actions:

• test Λ;
• distinguish dependence from compatibility;
• distinguish utility from coherence;
• distinguish support from extraction;
• distinguish reciprocity from retention;
• identify whether coupling should reduce, pause, end, or be redesigned.

Validation:

Λ tested
reciprocity assessed
invalid coupling named

Phase 4 — Reduce Extractive Coupling

Purpose: Stop ongoing drain.

Actions:

• reduce access;
• revoke invalid permissions;
• reduce dependency;
• pause extraction channel;
• reduce data, attention, labor, legitimacy, financial, or symbolic drain;
• block new burden export;
• create replacement support if needed.

Validation:

d⊗/dt < 0 where extractive
H_extraction growth slows
K / σ begins improving

Phase 5 — Restore Boundaries and Close Hook Surfaces

Purpose: Prevent continued or hidden reattachment.

Actions:

• restore scope;
• restore consent and revocation;
• repair exit path;
• close interface hooks;
• repair role boundaries;
• block proxy relays;
• document the boundary condition.

Validation:

BΣ ↑
hook surfaces closed or scoped
exit viable

Phase 6 — Repair Host / Affected Node

Purpose: Restore what extraction depleted.

Actions:

• rebuild slack;
• restore restoration capacity;
• repair hidden debt;
• repair boundary damage;
• restore auditability;
• restore agency or portability;
• clear backlog or deferred repair created by extraction.

Validation:

R_host ↑
K / σ ↑
H_extraction ↓
O_host ↑ or stabilizes

Phase 7 — Temporal and Recapture Proof

Purpose: Confirm extraction does not return.

Actions:

• monitor recurrence;
• monitor recapture pathways;
• monitor host slack;
• monitor hidden debt;
• monitor new hooks;
• monitor whether extraction returns under different language or interface.

Validation:

recapture risk ↓
H_extraction(t+n) ≤ H_extraction(t)
K / σ(t+n) ≥ K / σ(t)
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Parasitic Extraction Recovery cannot validly proceed in that form.

The system must either:

• increase observability;
• expand auditability;
• protect boundaries;
• reduce coupling;
• route to safe decoupling;
• provision host repair;
• block recoupling until compatibility and non-extraction are proven.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

Au_extraction ↑
d⊗/dt < 0 where extractive
BΣ ↑
K / σ ↑
R_host ↑
H_extraction ↓
O_host stable or ↑
recapture risk ↓
recurrence ↓ across U7

Parasitic Extraction Recovery is not complete if:

host slack continues declining
extraction path remains untraceable
coupling remains active through dependency
exit remains symbolic
visible calm returns while host capacity falls
old hook returns through proxy relay
extraction is renamed as support

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• extraction is named but coupling remains unchanged;
• the host is asked to prove depletion while still being drained;
• the extracting system controls the audit surface;
• visible incidents stay low while host slack continues falling;
• access is reduced in language but dependency remains intact;
• the extraction hook returns through convenience, emergency, loyalty, or interface defaults;
• support is removed without repairing host capacity;
• extraction is reframed as growth, service, loyalty, love, safety, or alignment;
• value flow remains one-way;
• the host’s recovered capacity is immediately captured again.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Parasitic Extraction Recovery cannot be declared complete until the host remains less drained over time and the extraction hook does not recur.

Template:

Completion requires H_extraction(t+n) ≤ H_extraction(t),
K / σ(t+n) ≥ K / σ(t),
R_host(t+n) ≥ R_host(t),
and recapture risk decreasing across U7.

Minimum temporal proof:

• host slack recovers;
• host restoration capacity recovers;
• extraction path remains closed or bounded;
• coupling does not return through proxy;
• hidden debt does not re-accumulate;
• any continued coupling remains compatibility-positive and auditable.

10.3 Completion Statement

Canonical format:

This arc is complete only when the extraction path is traceable, invalid coupling has been reduced, host boundaries and restoration capacity have recovered, and the system no longer loses slack, coherence, or repair capacity through the old hook or a proxy replacement.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

H, H_extraction, K, σ(t), R, O, Au, BΣ, Λ, ⊗, ι, 𝓓(t), τ_m, recurrence, recapture risk, Φ/O divergence

11.4 Related Laws / Invariants

INV — Coupling requires compatibility.
INV — Boundary integrity is required for valid coupling.
INV — Hidden debt must be reduced, not relocated.
INV — Exit must be real for consent-like participation to remain valid.
LAW — Parasitic coupling consumes restoration capacity before visible error rises.
LAW — Silent extraction preserves appearance while degrading host coherence.
LAW — Forced dependency accumulates hidden debt.
LAW — Φ improvement is not O restoration.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• data extraction;
• attention extraction;
• memory dependence;
• tool dependence;
• workflow lock-in;
• user agency drain;
• hidden review burden;
• evaluator or moderation labor;
• platform defaults that recapture user state;
• whether helpfulness is coupled to increased dependency.

AI extraction recovery requires restoring user agency, memory boundaries, tool boundaries, data portability, auditability, and non-extractive assistance.

12.2 Justice / Governance / Legitimacy

Check:

• unpaid testimony labor;
• affected-node legitimacy labor;
• procedural extraction;
• public story extraction;
• institutional reputation dependency;
• forced participation;
• repair conditioned on continued exposure;
• rank immunity hidden behind process.

JGL extraction recovery must stop using affected nodes as the resource through which legitimacy is repaired.

12.3 Biology / Medicine

Conceptual systems mapping only.

Parasitic Extraction Recovery in biological systems means identifying patterns that consume energy, repair capacity, clearance, boundary integrity, or resilience while visible error may remain low or intermittently suppressed.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• hidden labor;
• externalized cost;
• debt dependency;
• platform lock-in;
• rent extraction;
• data / attention extraction;
• switching penalties;
• productivity maintained by depletion;
• survival-edge participation.

Economic extraction recovery restores bargaining room, clearance, portability, exit, and non-coercive exchange.

12.5 CMS / Meaning / Archetypes

Check:

• symbolic obligation;
• devotion as access;
• belonging as dependency;
• love as extraction;
• spiritualized labor;
• archetypal role capture;
• taboo against exit;
• meaning used to drain sovereignty.

Meaning systems require recovery from extraction while preserving real symbolic value, relationship, and depth where valid.

13. Machine-Readable Metadata

id: "RA-027"
title: "Parasitic Extraction Recovery"
aliases:
  - "Extraction Recovery"
family_primary: "Security"
families_secondary:
  - "Core"
  - "Coupling"
  - "Boundary"
  - "Cybernetics"
  - "Economy"
  - "AI Governance"
  - "Justice / Governance / Legitimacy"
  - "CMS"
  - "Scaling"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Local"
  - "Relational"
  - "Institutional"
  - "AI"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U1 capacity / labor / energy drain"
    - "often U2 boundary / interface / access"
    - "often U3 control / dependency path"
    - "often U4 legitimacy / meaning / utility narrative"
  symptom_visible:
    - "U6 field exhaustion"
    - "U4 justification narrative"
    - "Φ productivity / convenience / low-error signal"
  repair_required:
    - "same or lower than layer where extraction hook or dependency is generated"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Μ extraction map → Au value / drain trace → Ξ extraction inversion detection → Λ compatibility reassessment → ⊗↓ coupling reduction → Π boundary repair → Σ anti-recapture lock → ℛ host restoration → Τ recapture validation"
  sequence:
    - "Μ"
    - "Au"
    - "Ξ"
    - "Λ"
    - "⊗↓"
    - "Π"
    - "Σ"
    - "ℛ"
    - "Τ"
state_variables:
  primary:
    - "H"
    - "K"
    - "σ(t)"
    - "R"
    - "O"
  secondary:
    - "Au"
    - "BΣ"
    - "Λ"
    - "⊗"
    - "ι"
    - "Φ"
diagnostics:
  - "H_extraction"
  - "𝓓(t)"
  - "τ_m"
  - "recurrence"
  - "recapture risk"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Parasitic Extraction"
  - "Silent Extraction"
  - "Hook-Surface Capture"
  - "Forced Dependency"
  - "Coupling Without Compatibility"
  - "Coercive Dependency"
  - "Boundary Collapse"
  - "Interface Capture"
  - "Consent Theater"
  - "Security Theater"
  - "Hidden Labor Drain"
  - "Dependency Capture"
  - "Recapture After Exit"
linked_restoration_arcs:
  - "RA-005"
  - "RA-006"
  - "RA-010"
  - "RA-014"
  - "RA-018"
  - "RA-020"
  - "RA-025"
  - "RA-028"
  - "RA-030"
  - "RA-056"
  - "RA-063"
anti_patterns:
  - "Extraction-Label Theater"
  - "Host-Proof Burden"
  - "Support Rebranding"
  - "Convenience Recapture"
  - "Audit Capture"
  - "Drain Reduction Theater"
  - "Capacity Recapture"
completion_tests:
  - "Au_extraction increases"
  - "d⊗/dt < 0 where extractive"
  - "BΣ increases"
  - "K / σ increases"
  - "R_host increases"
  - "H_extraction decreases"
  - "O_host stable or increases"
  - "recapture risk decreases"
  - "recurrence decreases across U7"
summary: "Parasitic Extraction Recovery repairs systems where a coupling, interface, dependency, role, contract, tool, institution, or symbolic structure consumes slack, coherence, restoration capacity, data, attention, labor, or legitimacy while visible error remains low."

Final Calibration Rule

Parasitic Extraction Recovery answers six questions:

What hidden debt is being generated by extraction or hidden drain?
What boundary, hook surface, dependency, or exit path must be repaired?
What auditability proves the extraction path and value flow are traceable?
What coupling, dependency, interface, or proxy relay must be reduced or blocked?
What trajectory becomes viable once host slack and restoration capacity recover?
How is recovery proven over time without support rebranding, capacity recapture, or proxy reattachment?