0. Cybernetic Scope Note

This entry is conceptual and systems-oriented.

It does not treat post-exit contact, transitional support, continued obligation, repair negotiation, legitimate accountability, migration assistance, settlement, verification, or bounded re-engagement as inherently failed. Some exits require safe handoff. Some systems need post-exit closure, debt settlement, evidence preservation, repair, or transitional coordination.

The failure begins when post-exit contact becomes a recapture channel.

The issue is not all continued relation.

The issue is re-coupling after exit through dependency, leverage, pressure, or control residue.

Recapture After Exit occurs when a system that lost direct control regains influence through leftover routes that were not fully discharged, protected, audited, or bounded.

1. Definition

Recapture after exit occurs when a node, subsystem, person, institution, process, or field successfully leaves a dependency, regime, basin, platform, relationship, contract, control layer, or unstable loop, but the prior system reasserts capture through dependency, pressure, surveillance, identity hooks, incentives, access control, debt, legitimacy claims, retaliation, or repair obstruction.

The recapture channel may involve:

• accounts
• contracts
• debt
• identity graphs
• reputation
• shared infrastructure
• access permissions
• surveillance
• data retention
• dependency chains
• repair negotiations
• legal process
• funding
• social ties
• platform lock-in
• workflow dependence
• institutional legitimacy
• emergency exceptions
• administrative requirements
• unresolved obligations

The core failure is:

exit achieved
residual leverage remains
prior system activates recapture channel
agency↓
forced coupling↑
H↑

Recapture After Exit differs from Exit Snap-Back.

Exit Snap-Back emphasizes internal or structural pullback into a prior basin.

Recapture After Exit emphasizes active reassertion of control by the prior system or field.

2. Core Pattern

The core pattern is:

1. A node exits a relation, platform, dependency, regime, contract, control field, or unstable loop.
2. The prior system loses direct access or control.
3. Residual channels remain: access, dependency, debt, identity, repair process, surveillance, reputation, data, legitimacy, or administrative linkage.
4. The prior system uses these residual channels to reassert influence.
5. The exited node must spend capacity defending exit rather than stabilizing new state.
6. Agency narrows.
7. Consent becomes pressured.
8. Exit becomes costly to maintain.
9. The prior system frames recapture as support, accountability, safety, repair, normal process, continuity, or obligation.
10. Hidden debt accumulates through post-exit defense, delayed recovery, and renewed dependency.
11. The node is pulled back into constrained relation, even if the original exit was valid.

This failure mode often appears as:

you left, but you still need us for this

or:

this is not control; it is just process

or:

we are only maintaining safety, continuity, or repair

The restorative question is:

what remaining channel allows the prior system to reassert control?

Exit is incomplete while recapture channels remain live.

3. Failure Signature

Typical signature:

exit achieved
residual access / dependency remains
prior-system pressure↑
post-exit agency↓
defense load↑
forced re-coupling↑
H↑

Extended signature:

the old system no longer owns the node but still controls the gate
the relation ended but the dependency remains
the contract closed but the data hook persists
the platform was left but the identity graph remains
the regime ended but emergency authority remains

Common forms include:

platforms retaining user dependency after departure
vendors using data, migration, or compatibility to force return
institutions using reputation or legitimacy claims to reattach exited nodes
contracts preserving leverage after formal termination
security systems retaining surveillance after access is revoked
AI governance regimes leaving old moderation or policy hooks in downstream tooling
organizations recapturing former workers through undocumented knowledge dependence
restoration processes requiring ongoing contact with the harming structure
economic systems using debt to reassert dependency
legal or administrative processes turning exit into renewed capture

The defining condition is not post-exit obligation.

The defining condition is post-exit leverage used to narrow agency and reattach control.

4. Primary U-Layer Origin

Common origin layers:

• U1 — Power / Budgets: prior system benefits from continued access, dependency, revenue, legitimacy, data, compliance, or control.
• U2 — Configuration / Boundaries: exit boundaries retain residual channels or backdoors.
• U3 — Execution / Runtime: administrative, technical, contractual, social, or operational recapture actions occur.
• U4 — Information / Truth: recapture is framed as support, process, safety, continuity, or repair.
• U5 — Coordination / Time: recapture pressure appears after exit when the node is still stabilizing.
• U6 — Coherence Field: prior-system legitimacy makes reattachment appear normal.
• U7 — Memory / Recurrence: old relationship patterns reactivate through habit or infrastructure.
• U8 — Environment / Field: surrounding ecosystem rewards return to dominant dependency.

Common manifestation layers:

• U1 — Power: prior system retains leverage.
• U2 — Boundaries: residual access remains.
• U3 — Execution: recapture mechanisms activate.
• U4 — Truth: recapture is mislabeled.
• U5 — Time: post-exit vulnerability is exploited.
• U6 — Coherence Field: old system appears necessary.
• U8 — Environment: field dependency reinforces capture.

Recapture After Exit is primarily a U2 / U1 post-exit boundary-control failure.

The boundary is crossed, but leverage remains behind it.

5. Typical Development Sequence

A common development sequence is:

1. A node exits a relation, regime, platform, dependency, contract, or control field.
2. The exit is visibly successful.
3. The prior system retains residual leverage.
4. The exited node enters a vulnerable stabilization window.
5. The prior system activates a recapture route.
6. Recapture is framed as normal process, obligation, safety, continuity, support, accountability, or repair.
7. The exited node must comply, respond, defend, or re-engage.
8. New-state stabilization is delayed.
9. The old relation regains influence.
10. Exit cost rises.
11. Other nodes observe the cost and become less likely to exit.
12. The prior system regains control directly or indirectly.

The loop often looks like:

exit → residual leverage → recapture pressure → defense load → weakened exit → re-coupling

Another common loop is:

recapture challenged → prior system cites obligation → agency narrows → challenge becomes costlier

Recapture After Exit becomes self-reinforcing because successful recapture discourages future exit and strengthens the prior system’s field authority.

6. Diagnostic Markers

Diagnostic markers include:

• Exit requires ongoing permission from the prior system.
• The old system retains access, data, keys, accounts, infrastructure, reputation hooks, or legal leverage.
• Post-exit stabilization is consumed by defending boundaries.
• Recapture is framed as safety, continuity, repair, or process.
• The exited node must use old channels to complete exit.
• Exit costs increase after departure.
• Former dependencies become bargaining tools.
• Contact after exit repeatedly benefits the prior system.
• The prior system can delay, block, or complicate migration.
• Exit does not reduce surveillance or influence.
• Repair processes require re-exposure to the recapturing system.
• The prior system treats refusal as noncompliance.
• The exited node cannot fully revoke access.
• Other nodes stay because they see recapture risk.
• Restoration improves when residual leverage is removed.

Useful diagnostics:

• Recapture Pressure: Measures force applied to reattach control.
• Exit Integrity: Tests whether exit is complete and durable.
• Dependency Residue: Identifies remaining dependencies after exit.
• Boundary Integrity: Tests whether post-exit boundaries are protected.
• Post-Exit Agency: Measures choice, refusal, and independent action after exit.
• Retaliation Risk: Measures punitive or coercive response to exit.
• Access Control Leverage: Identifies retained keys, data, permissions, or infrastructure.
• Hidden Debt: Tracks cost of defending exit.
• Auditability: Determines whether recapture pathways can be traced.
• Restoration Capacity: Measures capacity to stabilize outside prior control.

7. Related Gates

Relevant gates include:

• Exit Gate: Fails when exit does not remove post-exit leverage.
• Recapture Gate: Fails when residual channels allow reattachment.
• Boundary Gate: Fails when post-exit boundaries are porous or unenforced.
• Dependency Gate: Fails when old dependencies remain operational.
• Consent Gate: Fails when re-engagement is pressured or coerced.
• Agency Gate: Fails when exited nodes cannot meaningfully refuse.
• Auditability Gate: Fails when recapture routes are hidden.
• Restoration Gate: Fails when repair requires renewed capture.

The first common gate failure is usually the Recapture Gate.

The system leaves but remains reachable by the prior controller.

8. Related Operators

Relevant operators include:

• BΣ — Boundary Integrity: Protects post-exit separation.
• K — Constraint / Load: Rises when exit defense consumes capacity.
• Φ — Flow / Resource Movement: Routes access, data, money, legitimacy, repair, or dependency through recapture channels.
• H — Hidden Debt: Accumulates through post-exit defense and delayed stabilization.
• Au — Auditability: Determines whether residual leverage can be traced.
• Ψ — Observation / Interface: Reveals or conceals post-exit recapture pathways.
• R — Restoration Capacity: Required to stabilize after exit.
• O — Coherence: Prior system may appear coherent by forcing return.
• Γ — Selection: Selects old pathways when they remain easier or more resourced.
• Λ — Compatibility: Tests whether post-exit relations are compatible with agency.
• Τ — Trajectory / Time: Reveals whether exit holds across post-exit pressure.
• G — Gain: Amplifies recapture pressure.
• D — Damping: Can soften transition or suppress recapture signals.

Common operator pattern:

exit occurs
BΣ post-exit boundary incomplete
Φ residual dependency remains
prior system increases G through leverage
K rises on exited node
Γ selects old path under pressure
R is consumed by defense
Au cannot fully trace recapture channel
H accumulates
Τ reveals re-coupling

The core operator inversion is:

continued access → legitimate relation

instead of:

continued access → post-exit consent audit → bounded relation or removal

Recapture After Exit turns residue into control.

9. Related Laws and Invariants

Related Laws

• Exit Denial: exit is prevented or made functionally unavailable.
• Forced Coupling: the node is rebound into unwanted relation.
• Boundary Collapse: post-exit boundaries fail.
• Dominance Masquerading as Control: recapture is framed as governance, safety, or care.
• Parasitic Extraction: recapture preserves access to extracted value or capacity.
• Consent Drift: post-exit re-engagement becomes coerced or stale.
• Hidden Debt Accumulation: exit defense creates unaccounted burden.
• Auditability Collapse: residual leverage is hidden or hard to trace.
• Emergency Normalization: exceptional post-exit control becomes normal.
• Dependency Lock-In: old dependencies keep exit from becoming real.

Related Invariants

• Exit Must Remain Protected After Release: the post-exit state needs defense from reattachment.
• Exited Nodes Must Not Be Recaptured Through Dependency: remaining dependency must not become coercive control.
• Exit Requires Durable Boundary Sovereignty: separation must persist under pressure.
• Post-Exit Agency Must Be Preserved: refusal, revision, and independent action must remain possible.
• Control Claims Must Not Reattach Through Repair: repair cannot become capture.
• Dependency Must Not Become Capture: transitional dependency must be bounded and discharged.
• Restoration Must Protect Against Retaliatory Recoupling: recovery needs shielding from the prior controller.

10. Common False Positives

Not every post-exit relation is Recapture After Exit.

Common false positives include:

• Voluntary post-exit coordination with clear boundaries.
• Legitimate repair process that preserves agency.
• Transitional support with sunset criteria.
• Contractual closure that does not narrow agency.
• Data retention required for bounded legal or safety reasons with audit and deletion path.
• Temporary re-engagement chosen freely.
• Migration assistance that reduces dependency.
• Accountability that does not create renewed capture.
• Shared infrastructure with independent governance.
• Post-exit contact that benefits the exited node and remains revocable.

Clarifying rule:

This is not Recapture After Exit unless the prior system uses residual dependency, access, identity, surveillance, debt, legitimacy, retaliation, contract, repair, or administrative leverage to reassert control or narrow agency after apparent exit.

11. Common False Repairs

Common false repairs include:

• requiring the exited node to negotiate through the prior controller
• adding more process to exit while leaving leverage intact
• framing recapture pressure as support
• asking the prior system to certify its own non-capture
• creating symbolic exit while retaining data, keys, or permissions
• moving control into a vendor, proxy, or administrative layer
• making re-engagement mandatory for repair
• punishing refusal as noncooperation
• offering temporary relief without dependency discharge
• requiring public gratitude or legitimacy signaling after exit
• preserving emergency access indefinitely
• treating exit defense as the exited node’s private burden
• converting recapture into a new contract
• declaring exit complete because the formal relationship ended

False repair often produces the loop:

recapture exposed → formal exit process expanded → prior system retains leverage → recapture persists

Another common loop is:

exit defense burdens node → node needs old support → prior system regains influence

The repair fails because it treats recapture as administrative friction rather than control reattachment.

12. Restoration Direction

Restoration requires identifying recapture channels, removing residual leverage, protecting post-exit agency, discharging dependencies, and creating independent restoration pathways.

Primary restoration direction:

identify recapture channels,
remove residual leverage,
protect post-exit agency,
and stabilize outside prior control

A fuller restoration path includes:

1. Name the prior system. Identify the platform, institution, relation, contract, regime, dependency, or control layer exited.
2. Name the exit. Clarify what separation was supposed to accomplish.
3. Map recapture channels. Identify remaining access, data, keys, accounts, contracts, identity hooks, funding, debt, reputation, infrastructure, or repair pathways.
4. Measure recapture pressure. Determine how the prior system can create cost, delay, threat, dependency, or legitimacy loss.
5. Audit post-exit agency. Test whether the exited node can refuse, revise, revoke, ignore, migrate, or stabilize independently.
6. Remove residual access. Revoke permissions, close backdoors, rotate credentials, transfer data, and dissolve unnecessary links where applicable.
7. Discharge dependencies. Replace old services, tools, funding, workflows, identity routes, or legitimacy paths.
8. Protect against retaliation. Build shields against punitive reattachment, reputational attack, surveillance, or resource denial.
9. Create independent repair pathways. Ensure restoration does not require submission to the prior system.
10. Bound legitimate contact. Define scope, duration, purpose, and consent conditions for any continued relation.
11. Repair exit-defense burden. Restore capacity spent maintaining exit.
12. Validate independence over time. Confirm the prior system cannot reassert control through delayed channels.
13. Install recapture monitoring. Track reattachment attempts and dependency return.
14. Update the field map. Store the new relation as independent, not pending return.

A valid restoration path should reduce:

residual leverage
dependency residue
access capture
exit-defense burden
retaliation risk
post-exit surveillance
forced re-engagement
agency loss
hidden debt
recapture pressure

Recapture After Exit is not repaired by asking the prior system to behave better.

It is repaired by removing its leverage.

13. Cross-Module Links

• Cybernetics: Directly concerns exit, recapture, control reattachment, dependency, and boundary durability.
• Diagnostics: Requires recapture-pressure, exit-integrity, dependency-residue, access-leverage, and post-exit-agency diagnostics.
• Security: Direct link to access revocation, identity systems, surveillance residue, vendor lock-in, and post-compromise recapture.
• Justice: Exit from captured, coercive, punitive, or illegitimate regimes requires protection from retaliatory recoupling.
• Restoration: Repair must not force re-exposure to the recapturing system unless safely bounded.
• AI Governance: AI systems, platforms, or policies may retain downstream hooks after formal exit from a governance regime or model dependency.
• Control Systems: Controllers can reattach through residual feedback or actuator pathways.
• Interfaces: Interfaces can preserve recapture through accounts, defaults, credentials, identity graphs, dark patterns, and administrative loops.
• Economy: Dependency lock-in, debt, contracts, and infrastructure access commonly enable recapture.
• Coherence: Recapture can look like continuity while it destroys post-exit agency.

14. Relationship to Parent / Child Modes

Production treatment: Standalone Entry

This mode maps upward to:

• FM-C-023 — Exit Snap-Back
• FM-CORE-008 — Forced Coupling
• FM-SEC-012 — Exit Failure / Recapture
• FM-C-022 — Dominance Masquerading as Control
• FM-C-021 — Parasitic Extraction

Sibling or related Cybernetics modes include:

• FM-C-014 — Topology Brittleness
• FM-C-015 — Proxy-Relay Drift
• FM-C-021 — Parasitic Extraction
• FM-C-022 — Dominance Masquerading as Control
• FM-C-023 — Exit Snap-Back
• FM-C-027 — Drift After Recovery

Related cross-family modes include:

• FM-SEC-012 — Exit Failure / Recapture
• FM-JC-011 — Locked-In Renegotiation Failure
• FM-JC-012 — Parasitic Contracting
• FM-ISC-009 — Consent Drift
• FM-ISC-012 — Restoration Lock-In
• FM-SEC-008 — Proxy-Relay Drift
• FM-ECOX-022 — Dependency Lock-In
• FM-ECOX-021 — Coercive Contract
• FM-AIX-019 — Node Capture
• FM-MT-014 — Institutional Absorption

Aliases preserved from source material:

• Recapture After Exit
• Post-Exit Recapture
• Exit Recapture
• Dependency Recapture
• Control Reassertion
• Post-Release Capture
• Exit Retaliation Capture
• Re-Coupling After Exit
• Basin Recapture
• Exit Path Capture

15. Minimal Entry Version

Definition: Recapture after exit occurs when a node, subsystem, person, institution, process, or field successfully leaves a dependency, regime, basin, platform, relationship, contract, control layer, or unstable loop, but the prior system reasserts capture through dependency, pressure, surveillance, identity hooks, incentives, access control, debt, legitimacy claims, retaliation, or repair obstruction.

Signature:

exit achieved
residual access / dependency remains
prior-system pressure↑
post-exit agency↓
defense load↑
forced re-coupling↑
H↑

Restoration direction:

• name the prior system
• name the exit
• map recapture channels
• measure recapture pressure
• audit post-exit agency
• remove residual access
• discharge dependencies
• protect against retaliation
• create independent repair pathways
• bound legitimate contact
• repair exit-defense burden
• validate independence over time
• install recapture monitoring
• update the field map

16. Machine-Readable Summary

failure_mode:
  id: "FM-C-024"
  name: "Recapture After Exit"
  family: "Cybernetics"
  production_treatment: "Standalone Entry"
  parent_modes:
    - "FM-C-023 — Exit Snap-Back"
    - "FM-CORE-008 — Forced Coupling"
    - "FM-SEC-012 — Exit Failure / Recapture"
  primary_failure: "The prior system uses residual dependency, access, identity, surveillance, debt, legitimacy, retaliation, contract, repair, or administrative leverage to reassert control or narrow agency after apparent exit."
  source: "UTS — Failure Modes Registry"
  source_id: "FM-C-024"
  scope_note: "Conceptual and systems-oriented; does not treat post-exit contact, transitional support, continued obligation, repair negotiation, legitimate accountability, migration assistance, settlement, verification, or bounded re-engagement as inherently failed."
  aliases:
    - "Recapture After Exit"
    - "Post-Exit Recapture"
    - "Exit Recapture"
    - "Dependency Recapture"
    - "Control Reassertion"
    - "Post-Release Capture"
    - "Exit Retaliation Capture"
    - "Re-Coupling After Exit"
    - "Basin Recapture"
    - "Exit Path Capture"
  signature:
    - "exit achieved"
    - "residual access / dependency remains"
    - "prior-system pressure↑"
    - "post-exit agency↓"
    - "defense load↑"
    - "forced re-coupling↑"
    - "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 — Coherence Field"
      - "U8 — Environment"
  state_variables:
    - "BΣ"
    - "K"
    - "Φ"
    - "H"
    - "Au"
    - "Ψ"
    - "R"
    - "O"
    - "Γ"
    - "Λ"
    - "Τ"
    - "G"
    - "D"
  first_gate_failure: "Recapture Gate"
  restoration:
    - "Recapture Defense"
    - "Post-Exit Boundary Protection"
    - "Dependency Discharge"
    - "Access Leverage Reduction"
    - "Retaliation Shielding"
    - "Exit Path Hardening"
    - "Consent Revalidation"
    - "Agency Restoration"
    - "Restoration Independence Repair"