0. Security Scope Note

This entry is conceptual and systems-oriented.

It does not treat all data collection, telemetry, monitoring, logging, service provision, dependency, API integration, platform mediation, managed security, contract relationship, or value exchange as inherently failed.

Security systems need visibility.

Platforms need operational data.

Services often require coupling.

Coupling and data flow may be valid when they are:

• disclosed
• bounded
• auditable
• consent-compatible
• scope-limited
• proportional
• revocable where possible
• necessary to the stated function
• protected against secondary misuse
• paired with reciprocity
• compatible with exit
• accountable to affected states
• not hidden behind security language
• not expanded through dependency
• not presented as protection while extracting unrelated value

The failure begins when the coupling quietly serves the extractor more than the protected or served node.

A valid security coupling protects the node while preserving boundary integrity.

A parasitic coupling extracts from the node while preserving the appearance of protection, service, authorization, or normal operation.

Silent Extraction / Parasitic Coupling occurs when the security or service relationship becomes a covert value channel.

The problem is not telemetry or integration.

The problem is hidden extraction through a coupling that the affected node cannot fully see, refuse, scope, audit, or rebalance.

1. Definition

Silent Extraction / Parasitic Coupling occurs when a security, platform, institutional, technical, contractual, surveillance, data, or access system quietly draws value, data, attention, labor, legitimacy, control, compliance, or strategic advantage from another node through hidden or poorly disclosed coupling while presenting the relationship as protection, service, convenience, authorization, or normal operation.

The extracted value may include:

• data
• metadata
• behavioral signals
• location traces
• identity signals
• attention
• labor
• creative output
• trust
• legitimacy
• compliance
• risk absorption
• security posture
• user dependency
• market leverage
• institutional credibility
• social graph value
• operational telemetry
• model-training value
• interface control
• economic value
• governance advantage
• strategic intelligence
• affected-state silence

The parasitic coupling may appear through:

• telemetry defaults
• hidden logging
• broad monitoring
• opaque integrations
• SDKs
• browser extensions
• mobile permissions
• identity providers
• single sign-on systems
• access management systems
• endpoint agents
• managed security tools
• cloud platforms
• vendor security software
• AI assistants
• platform APIs
• data brokers
• consent banners
• contract clauses
• “security improvement” programs
• fraud prevention systems
• trust and safety systems
• surveillance infrastructure
• user analytics
• risk scoring systems

The coupling may be described as:

• security
• safety
• quality
• convenience
• personalization
• fraud prevention
• compliance
• account protection
• service improvement
• abuse prevention
• risk management
• platform integrity
• operational telemetry
• user experience
• enterprise control
• incident response
• model improvement
• public benefit

The core failure is:

service or security coupling forms
→ visibility or access is granted
→ secondary value flow begins
→ extraction is hidden, vague, or normalized
→ consent and audit lag behind actual flow
→ source burden accumulates
→ extractor records gain as normal operation

Silent Extraction / Parasitic Coupling is not merely data flow.

It is covert or poorly bounded value extraction through a trusted or necessary coupling.

2. Core Pattern

The core pattern is:

1. A node accepts coupling for security, service, access, identity, convenience, or participation.
2. The coupling grants visibility, access, telemetry, control, or dependency.
3. Secondary value flows begin beyond the obvious function.
4. These flows are hidden, bundled, abstracted, or described in broad terms.
5. The affected node cannot easily see, scope, refuse, revoke, or audit the extraction.
6. The extractor benefits from the coupling.
7. The source node carries burden, risk, loss of agency, or exposure.
8. Consent artifacts or security claims preserve legitimacy.
9. The coupling becomes normal infrastructure.
10. Hidden debt accumulates.
11. Exit becomes difficult because the coupling is now operationally embedded.
12. The extraction becomes structural.

A healthy system says:

a protective or service coupling must disclose and bound every material value flow

A parasitic system says:

the coupling is authorized because the service is being used

Silent Extraction often hides beneath utility.

The tool works.

The account is protected.

The interface is convenient.

The service is integrated.

The dashboard is useful.

But the coupling may be drawing more from the node than the node has actually authorized or can sustain.

3. Failure Signature

Typical signature:

coupling dependency↑
hidden value flow↑
data flow traceability↓
consent-flow divergence↑
secondary use exposure↑
reciprocity ratio↓
boundary permeability↑
exit cost↑
hidden debt↑
O↓

Extended signature:

protection provided,
data extracted

service given,
dependency formed

security claimed,
visibility captured

convenience offered,
boundary crossed

authorization recorded,
secondary use hidden

integration deepens,
exit weakens

Common verbal signatures include:

this data is used to improve the service
telemetry is necessary for security
users agreed to the policy
this is standard industry practice
the integration requires access
the monitoring protects users
we only collect what we need
continued use authorizes processing
the data is anonymized
this helps prevent abuse
this is for platform integrity
the tool cannot work without it

Common system signatures include:

a security agent collects broad telemetry unrelated to immediate protection
an identity provider gains cross-service visibility through authentication coupling
a platform uses safety systems to collect behavioral data for unrelated optimization
an AI system uses interaction data for model improvement beyond clear consent scope
a managed security vendor extracts operational intelligence from customer environments
a fraud prevention system creates hidden profiling and access denial pathways
a mobile app requests protective permissions that become analytics channels
a contract frames data capture as service improvement while preventing meaningful refusal

The defining condition is not that coupling exists.

The defining condition is that the coupling quietly extracts value beyond transparent, consented, reciprocal, and auditable scope.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: extracted value, data, leverage, or dependency benefits the coupling controller.
• U2 — Configuration / Boundaries: integration boundaries allow hidden access, secondary use, or excessive permission.
• U3 — Execution / Runtime: extraction occurs automatically through operational flows.
• U4 — Information / Truth: actual value flow is hidden behind vague labels or technical abstraction.
• U5 — Coordination / Time: scope expands over time as coupling becomes infrastructure.
• U6 — Coherence Field: trust in security, service, or convenience masks extraction.
• U7 — Memory / Recurrence: old authorizations and inherited integrations preserve extraction.
• U8 — Environment / Field: market, platform, vendor, or institutional norms reward hidden value capture.

Common manifestation layers:

• U1 — Resources: value concentrates in the coupling controller.
• U2 — Boundaries: affected boundaries become porous.
• U3 — Execution: data, telemetry, or control flows occur silently.
• U4 — Truth: official description understates material flow.
• U5 — Time: dependency deepens and exit weakens.
• U6 — Field: trust and legitimacy degrade when extraction becomes visible.

Silent Extraction / Parasitic Coupling is primarily a Φ / BΣ / Au / H failure.

Value flow crosses weakened boundaries without sufficient auditability, creating hidden debt.

5. Typical Development Sequence

A common development sequence is:

1. A service, security tool, platform, or institution offers useful coupling.
2. The user or node accepts the coupling for a stated function.
3. The coupling creates access, telemetry, identity linkage, or operational dependence.
4. Additional value flows are enabled by that access.
5. Consent language is broad enough to cover or obscure the flow.
6. Data or value is repurposed.
7. The affected node cannot easily inspect the flow.
8. Revocation or exit becomes costly.
9. The extractor’s dependency on the value channel increases.
10. The coupling expands.
11. The source carries risk, exposure, or loss of agency.
12. Hidden extraction debt accumulates.
13. The relationship is defended as normal operation.
14. Boundary integrity fails.

The loop often looks like:

useful coupling → access granted → secondary value flow → dependency → hidden extraction

Another common loop is:

extraction questioned → security/service purpose cited → audit denied → extraction continues

Silent Extraction becomes durable when the coupling is too useful or necessary to refuse.

6. Diagnostic Markers

Diagnostic markers include:

• Data flows exceed the stated purpose.
• Permissions are broader than the service function requires.
• Telemetry is difficult to disable.
• Secondary uses are disclosed vaguely or not at all.
• The affected node cannot trace where data or value goes.
• Consent exists but does not clearly cover actual extraction.
• Extraction continues after visible use ends.
• Revocation does not propagate downstream.
• Integration removal breaks essential functionality.
• A security or service provider gains strategic visibility beyond the protected function.
• The extractor cannot explain reciprocity.
• Affected nodes carry risk without proportional benefit.
• The coupling becomes required after initial adoption.
• Official descriptions emphasize protection while material flow is extraction.
• Exit is practically costly because the coupling is embedded.

Useful diagnostics:

• Hidden Value Flow: Measures value transfer not visible in the stated relationship.
• Data Flow Traceability: Tests whether data origin, path, use, sharing, and retention are knowable.
• Coupling Visibility: Measures whether coupling structure and permissions are understandable.
• Consent-Flow Divergence: Measures gap between consented flow and actual flow.
• Secondary Use Exposure: Tracks reuse beyond stated purpose.
• Reciprocity Ratio: Compares extracted value to returned value, repair, and protection.
• Boundary Permeability: Measures how easily value crosses affected boundaries.
• Affected-State Burden: Tracks risk, exposure, dependency, or loss carried by the source.
• Exit Cost: Measures practical cost of removing the coupling.
• Hidden Security Debt: Measures unresolved risk created by silent extraction.

7. Related Gates

Relevant gates include:

• Extraction Visibility Gate: Fails when material value flow is hidden.
• Coupling Transparency Gate: Fails when integration scope and access are unclear.
• Consent Scope Gate: Fails when consent does not cover actual extraction.
• Data Flow Audit Gate: Fails when data flow cannot be traced.
• Secondary Use Gate: Fails when repurposing occurs without renewed authorization.
• Reciprocity Gate: Fails when extracted value exceeds return and repair.
• Boundary Integrity Gate: Fails when affected boundaries are crossed silently.
• Affected-State Burden Gate: Fails when source burden is not counted.
• Exit Path Gate: Fails when coupling cannot be removed without disproportionate cost.
• Parasitic Coupling Gate: Fails when the relationship degrades the source while benefiting the extractor.

The first common gate failure is usually the Extraction Visibility Gate.

Once value flow is hidden, the affected node cannot consent, audit, revoke, or rebalance.

8. Related Operators

Relevant operators include:

• Φ — Flow / Resource Movement: Primary operator; value, data, control, or legitimacy flows through the coupling.
• BΣ — Boundary Integrity: Determines whether the coupling respects source boundaries.
• Au — Auditability: Determines whether flows and permissions can be inspected.
• H — Hidden Debt: Accumulates as consent debt, trust debt, exposure, and unrepaired burden.
• O — Coherence: Declines when coupling purpose and actual flow diverge.
• Ψ — Observation / Interface: Displays service or protection while hiding secondary flow.
• G — Gain: Rewards extraction through data, leverage, profit, control, or intelligence.
• Γ — Selection: Selects extractive architectures and broad permissions.
• K — Constraint / Load: Rises as the source becomes dependent or burdened.
• M — Meaning: Reframes extraction as security, service, improvement, or convenience.
• Λ — Compatibility: Tests whether coupling remains compatible with source viability.
• R — Restoration Capacity: Needed to repair boundary violations and rebalance flows.
• Τ — Trajectory / Time: Tracks scope expansion and dependency over time.
• E — Exit: Measures ability to remove the coupling.

Common operator pattern:

service coupling opens Φ
G rewards secondary value capture
Ψ frames flow as protection
Au cannot trace full flow
BΣ becomes porous
E declines
H accumulates
O declines

The core operator inversion is:

service use → authorization for extraction

instead of:

specific consent + disclosed flow + bounded scope + reciprocity + auditability + exit → valid coupling

Silent Extraction / Parasitic Coupling converts service dependency into hidden value transfer.

9. Related Laws and Invariants

Related Laws

• Coupling Must Remain Visible and Consent-Compatible: relationships must be inspectable and refusable where possible.
• Security Must Not Hide Extraction: protection claims cannot conceal unrelated value draw.
• Data Flow Must Remain Auditable: origin, use, sharing, and retention must remain traceable.
• Extraction Requires Reciprocity and Scope Integrity: value draw must be bounded and balanced.
• Protection Must Not Become Parasitic Access: protective coupling cannot become an extraction channel.
• Silent Value Flow Creates Hidden Debt: undisclosed extraction stores future trust and repair burden.
• Convenience Must Not Mask Boundary Crossing: ease of use cannot justify hidden flow.
• Authorization Must Not Hide Secondary Extraction: permission for one function does not authorize another.
• Parasitic Extraction: extraction fails when it weakens the source.
• Unbounded Extraction: drawdown fails when reciprocity, consent, and regeneration are absent.
• Consent Theater: artifacts can replace consent reality.
• Boundary Collapse: hidden access can dissolve real boundaries.

Related Invariants

• Extraction Must Be Disclosed: material value flow must be visible.
• Coupling Must Remain Auditable: integration, permissions, data, and value flow must be inspectable.
• Data Use Must Remain Scope-Bounded: use must match authorization.
• Consent Must Cover Actual Flow: consent must reflect what actually happens.
• Secondary Value Flow Must Be Traceable: repurposing must remain visible.
• Protection Claims Must Not Hide Drawdown: security language must not mask extraction.
• Affected-State Burden Must Be Counted: source risk and burden must be included.
• Parasitic Coupling Must Trigger Separation or Rebalancing: source degradation requires repair.

10. Common False Positives

Not every telemetry or integration relationship is Silent Extraction / Parasitic Coupling.

Common false positives include:

• Narrow telemetry required for real protection.
• Data flow that is clearly disclosed and purpose-limited.
• Security monitoring with bounded access and strong audit.
• Service analytics that are optional and revocable.
• Integrations with least privilege and transparent logs.
• Data sharing with specific consent and clear benefit.
• Managed security tools that minimize collection and preserve customer control.
• Fraud prevention systems with appeal and scope limits.
• Model improvement programs with explicit opt-in and deletion paths.
• Contractual data use with fair negotiation and traceability.
• Platform APIs that disclose scope and allow revocation.
• Monitoring that reduces exposure without secondary exploitation.

Clarifying rule:

This is not Silent Extraction / Parasitic Coupling unless hidden or poorly disclosed coupling draws value beyond transparent, consented, reciprocal, and auditable scope.

Data flow can be coherent.

It fails when the flow becomes a hidden extraction channel.

11. Common False Repairs

Common false repairs include:

• adding vague disclosure language
• expanding privacy policies without changing flows
• renaming extraction as telemetry
• adding dashboards that show categories but not actual flow
• allowing opt-out that breaks essential service
• anonymizing data while preserving strategic value extraction
• reducing visible collection while preserving backend sharing
• adding consent banners without scope separation
• creating deletion paths that do not remove downstream copies
• limiting direct identifiers while retaining behavioral profiles
• publishing security justifications without data-flow evidence
• claiming aggregation solves consent failure
• moving extraction into vendor subprocessors
• making data export available while retention continues
• treating user surprise as misunderstanding

False repair often produces the loop:

silent extraction exposed
→ disclosure expanded
→ extraction architecture unchanged
→ trust debt grows

Another common loop is:

secondary use challenged
→ purpose language broadened
→ secondary use becomes officially covered
→ consent reality remains weak

The repair fails because it changes the story around the flow without changing the flow.

12. Restoration Direction

Restoration requires tracing actual flows, disclosing material extraction, bounding coupling, revalidating consent, separating secondary uses, restoring boundaries, rebalancing reciprocity, repairing affected burden, and making exit or revocation real.

Primary restoration direction:

make every material value flow visible, bounded, consent-compatible, and repairable

A fuller restoration path includes:

1. Identify the coupling. Name the tool, integration, contract, platform, agent, API, or monitoring relationship.
2. Map actual flows. Trace data, value, control, attention, legitimacy, and dependency flows.
3. Identify hidden extraction. Determine what value is drawn beyond the stated function.
4. Audit consent scope. Compare actual flow against what was understood and authorized.
5. Separate primary from secondary use. Distinguish required service flow from optional extraction.
6. Disclose material flow. Make extraction visible in understandable terms.
7. Reduce permissions. Apply least privilege to data, access, telemetry, and control.
8. Restore boundaries. Stop flows that cross affected boundaries without valid scope.
9. Revalidate consent. Seek specific, current, revocable authorization where needed.
10. Rebalance reciprocity. Provide proportional return, benefit, repair, or compensation.
11. Restore revocation and exit. Ensure coupling can be removed without disproportionate harm.
12. Repair affected-state burden. Address exposure, trust loss, dependency, or data misuse.
13. Internalize externalized risk. Bring downstream burden into accountability.
14. Add ongoing flow audits. Monitor for new secondary extraction.
15. Gate future coupling. Prevent new integrations without visibility, consent, and exit checks.

A valid restoration path should reduce:

hidden value flow
consent-flow divergence
secondary use exposure
boundary permeability
exit cost
affected-state burden
hidden security debt
O loss

Silent Extraction / Parasitic Coupling is not repaired by saying the coupling is useful.

It is repaired by making usefulness stop hiding extraction.

13. Cross-Module Links

• Security: Primary family; silent extraction is a security failure because hidden coupling crosses boundaries under protection, access, or authorization claims.
• Core: Strongly linked to Boundary Collapse and Forced Coupling.
• Cybernetics: Parasitic Extraction is the cybernetic parent form.
• Reduction / Extraction / Inversion: Unbounded Extraction describes the broad value-flow failure.
• Interactions: Invisible Intrusion and Consent Drift often appear when coupling is hidden.
• Privacy: Data flow, scope, revocation, and secondary use are central privacy expressions.
• AI Governance: AI systems may extract data, interaction history, creative labor, or legitimacy under model improvement or safety language.
• Platforms: Platform infrastructure can silently draw behavioral, social, identity, and attention value.
• Contracts: Parasitic contracting and broad clauses can formalize hidden extraction.
• Economy: Extraction masking instability and forced profit can depend on silent coupling.
• Coherence: Coherence requires coupling to remain visible, bounded, reciprocal, and consent-compatible.

14. Relationship to Parent / Child Modes

Production treatment: Domain Expression of Parasitic Extraction

This mode maps upward to:

• FM-C-021 — Parasitic Extraction
• FM-REI-003 — Unbounded Extraction
• FM-SEC-004 — Consent Theater / Invalid Authorization
• FM-CORE-005 — Boundary Collapse
• FM-CORE-008 — Forced Coupling

Sibling or related Security modes include:

• FM-SEC-004 — Consent Theater / Invalid Authorization
• FM-SEC-005 — Interface Capture
• FM-SEC-008 — Proxy-Relay Drift
• FM-SEC-009 — Over-Surveillance Inversion
• FM-SEC-010 — Emergency Normalization
• FM-SEC-011 — Representation / Proxy Abuse / AIM Failure
• FM-SEC-012 — Exit Failure / Recapture
• FM-SEC-016 — Attention-Control Pseudo-Coherence
• FM-SEC-025 — CCS Suspension Fallacy

Related cross-family modes include:

• FM-C-021 — Parasitic Extraction
• FM-REI-003 — Unbounded Extraction
• FM-CORE-005 — Boundary Collapse
• FM-CORE-008 — Forced Coupling
• FM-ISC-009 — Consent Drift
• FM-ISC-011 — Invisible Intrusion
• FM-JC-012 — Parasitic Contracting
• FM-ECOX-024 — Extraction Masking Instability
• FM-ARCHX-008 — Extraction Through Empathy
• FM-AIX-016 — Standingless Instrumentalization
• FM-AIX-019 — Node Capture
• FM-R-004 — Repair Burden Externalization

Aliases preserved from source material:

• Silent Extraction
• Parasitic Coupling
• Silent Extraction / Parasitic Coupling
• Covert Extraction
• Hidden Value Extraction
• Undisclosed Data Coupling
• Security-Masked Extraction
• Service-Masked Extraction
• Convenience-Masked Extraction
• Authorization-Masked Extraction

15. Minimal Entry Version

Definition: Silent Extraction / Parasitic Coupling occurs when a security, platform, institutional, technical, contractual, surveillance, data, or access system quietly draws value, data, attention, labor, legitimacy, control, compliance, or strategic advantage from another node through hidden or poorly disclosed coupling while presenting the relationship as protection, service, convenience, authorization, or normal operation.

Signature:

coupling dependency↑
hidden value flow↑
data flow traceability↓
consent-flow divergence↑
secondary use exposure↑
reciprocity ratio↓
boundary permeability↑
exit cost↑
hidden debt↑
O↓

Restoration direction:

• identify the coupling
• map actual flows
• identify hidden extraction
• audit consent scope
• separate primary from secondary use
• disclose material flow
• reduce permissions
• restore boundaries
• revalidate consent
• rebalance reciprocity
• restore revocation and exit
• repair affected-state burden
• internalize externalized risk
• add ongoing flow audits
• gate future coupling

16. Machine-Readable Summary

failure_mode:
  id: "FM-SEC-007"
  name: "Silent Extraction / Parasitic Coupling"
  family: "Security"
  production_treatment: "Domain Expression of Parasitic Extraction"
  parent_modes:
    - "FM-C-021 — Parasitic Extraction"
    - "FM-REI-003 — Unbounded Extraction"
    - "FM-SEC-004 — Consent Theater / Invalid Authorization"
    - "FM-CORE-005 — Boundary Collapse"
    - "FM-CORE-008 — Forced Coupling"
  primary_failure: "A security, platform, institutional, technical, contractual, surveillance, data, or access system quietly draws value, data, attention, labor, legitimacy, control, compliance, or strategic advantage from another node through hidden or poorly disclosed coupling while presenting the relationship as protection, service, convenience, authorization, or normal operation."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-SEC-007"
  scope_note: "Conceptual and systems-oriented; does not treat all data collection, telemetry, monitoring, logging, service provision, dependency, API integration, platform mediation, managed security, contract relationship, or value exchange as inherently failed."
  aliases:
    - "Silent Extraction"
    - "Parasitic Coupling"
    - "Silent Extraction / Parasitic Coupling"
    - "Covert Extraction"
    - "Hidden Value Extraction"
    - "Undisclosed Data Coupling"
    - "Security-Masked Extraction"
    - "Service-Masked Extraction"
    - "Convenience-Masked Extraction"
    - "Authorization-Masked Extraction"
  signature:
    - "coupling dependency↑"
    - "hidden value flow↑"
    - "data flow traceability↓"
    - "consent-flow divergence↑"
    - "secondary use exposure↑"
    - "reciprocity ratio↓"
    - "boundary permeability↑"
    - "exit cost↑"
    - "hidden debt↑"
    - "O↓"
  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 — Resources"
      - "U2 — Boundaries"
      - "U3 — Execution"
      - "U4 — Truth"
      - "U5 — Time"
      - "U6 — Field"
  state_variables:
    - "Φ"
    - "BΣ"
    - "Au"
    - "H"
    - "O"
    - "Ψ"
    - "G"
    - "Γ"
    - "K"
    - "M"
    - "Λ"
    - "R"
    - "Τ"
    - "E"
  first_gate_failure: "Extraction Visibility Gate"
  restoration:
    - "Extraction Visibility Audit"
    - "Data Flow Trace Reconstruction"
    - "Coupling Transparency Restoration"
    - "Consent Scope Revalidation"
    - "Secondary Use Separation"
    - "Reciprocity Rebalancing"
    - "Boundary Re-Separation"
    - "Affected-State Burden Repair"
    - "Parasitic Coupling Release"
    - "Exit Path Restoration"