0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Safe Decoupling repairs conditions where a coupling must be reduced or ended because it has become extractive, coercive, invalid, over-fused, compatibility-negative, or structurally unsafe to continue.

It applies when ordinary boundary repair, consent renewal, contract revision, or compatibility recoupling is not enough because the active coupling itself is generating hidden debt, suppressing exit, capturing identity, extracting capacity, or preserving an unsafe dependency.

This arc repairs unsafe coupling by:

• reassessing compatibility;
• reducing or ending invalid coupling;
• restoring boundary integrity;
• creating a safe exit path;
• preserving auditability and evidence;
• reducing recapture pathways;
• protecting post-exit sovereignty;
• repairing damage to the host or affected node;
• validating that the old coupling does not return through proxy, dependency, emergency, or symbolic relays.

Safe Decoupling is the canonical arc for exiting a harmful coupling without abandonment, snap-back, retaliation, or hidden reattachment.

1.2 Core Restoration Function

This arc restores safe exit by reducing compatibility-negative coupling, strengthening boundary integrity, preserving auditability, restoring exit, repairing extraction damage, and preventing recapture until the affected system can stabilize without the invalid connection.

Safe Decoupling prevents the system from confusing continued attachment with coherence.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• Λ ≤ 0 or compatibility is no longer trustworthy;
• the coupling is extractive, coercive, parasitic, or over-fused;
• exit is technically possible but materially, socially, procedurally, economically, or identity-wise unsafe;
• continued participation generates hidden debt;
• dependency pressure makes consent structurally invalid;
• the coupling continues through fear, obligation, survival pressure, role capture, institutional pressure, or interface capture;
• ordinary contract revision would preserve the damage geometry;
• boundary repair cannot hold while coupling remains active;
• affected-node restoration requires distance, exit, or protection from recapture;
• prior decoupling attempts failed through snap-back, proxy relay, or dependency return.

Examples:

• an AI system must revoke tool, memory, or data coupling that cannot be consent-valid;
• a platform or institution must release users from a coercive dependency path;
• an economic relation must reduce debt, lock-in, or survival-edge dependency before renewed exchange is valid;
• a governance process must stop requiring participation from an affected node to preserve institutional legitimacy;
• a relationship, role, or symbolic structure must reduce fusion because continued unity consumes sovereignty;
• a security system must isolate a component whose coupling creates ongoing compromise risk.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and emergency stabilization must occur first;
• safe exit is impossible without first creating replacement support;
• compatibility is positive and scoped recoupling is the better restoration path;
• the system is using decoupling to abandon responsibility;
• the harmed node would be made less safe by separation;
• auditability would be destroyed by exit;
• material repair owed before separation would be avoided;
• the system needs full supersession rather than decoupling alone;
• boundary repair or consent re-formation is sufficient and safer.

Safe Decoupling must not become abandonment 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, boundary reconstitution, audit surface expansion, slack regeneration, controlled decoupling, or supersession planning.

3. Failure / Damage Signature

3.1 Pre-State Across S

3.2 Primary Failure Links

3.3 Origin-Layer Localization

Canon rule:

Safe decoupling requires reducing coupling while preserving boundary integrity, auditability, and post-exit viability.

4. Restoration Objective

4.1 Canonical Objective

Restore safe separation by reducing invalid coupling, restoring exit, protecting boundaries, repairing dependency damage, and preventing recapture.

Formal objective:

Λ ≤ 0 acknowledged or compatibility untrusted
d⊗/dt < 0
BΣ ↑
exit viability ↑
Au_exit ↑
K / σ ↑
H_coupling ↓
recapture risk ↓
recurrence ↓

Expanded objective:

Move the system from harmful attachment into boundary-safe independence, successor topology, or repair-supporting distance without exporting harm, destroying auditability, or allowing the old coupling to return by proxy.

4.2 Non-Goals

This arc does not aim to:

• punish through separation;
• abandon owed repair;
• erase evidence;
• sever necessary support without replacement;
• preserve invalid coupling for comfort;
• use exit language to hide expulsion;
• force independence before capacity exists;
• treat silence after exit as proof of repair;
• restore old coupling under softer language;
• avoid responsibility by declaring “separation.”

5. Operator Sequence

5.1 Minimal Operator Scaffold

Λ reassessment → ⊗↓ coupling reduction → BΣ reinforcement → Π exit path → Σ post-exit invariants → Au preservation → Θ recapture damping → ℛ host / affected-node repair → Τ recapture validation

Universal grammar alignment:

Σ + Θ → Π → ⊗↓ → Au preservation → ℛ(host / successor path) → Τ → Temporal Proof

Safe Decoupling may route into Parasitic Extraction Recovery, Fusion Reversal, Contract Release, Sovereignty Safeguard Restoration, Reintegration Membrane, or Supersession.

5.2 Operator Step Table

5.3 Sequence Notes

This arc is exit-gated, recapture-gated, and support-gated.

Safe Decoupling is stronger than ordinary controlled decoupling. It applies when the coupling is not merely uncertain, but unsafe to preserve without significant separation, support, and recapture prevention.

The sequence must distinguish:

controlled decoupling
safe decoupling
punitive exit
abandonment
contract release
supersession

The following steps cannot be skipped:

compatibility reassessment
coupling reduction
boundary reinforcement
safe exit path
audit preservation
post-exit support
recapture prevention
temporal proof

If decoupling creates collapse because support was removed too quickly, the arc has failed.

If separation is announced but dependency remains intact, the arc has become symbolic.

6. Restoration Phases

Phase 0 — Identify Unsafe Coupling

Purpose: Name the coupling that must be exited, reduced, or made inactive.

Actions:

• identify access, dependency, contract, tool, data, memory, labor, role, interface, symbolic, or institutional coupling;
• identify who benefits and who carries cost;
• identify whether coupling is extractive, coercive, over-fused, or compatibility-negative;
• identify whether prior boundary repair failed;
• identify whether ordinary recoupling is inadmissible.

Validation:

unsafe coupling named
burden path visible
continued coupling not assumed valid

Phase 1 — Reassess Compatibility and Exit Necessity

Purpose: Determine whether safe decoupling is the required topology.

Actions:

• test or reassess Λ;
• distinguish dependency from compatibility;
• distinguish safety from control;
• distinguish obligation from coercion;
• identify whether contract repair, consent renewal, or boundary repair is insufficient;
• identify if supersession is needed instead.

Validation:

Λ negative, untrusted, or invalid
safe decoupling justified
lesser repair path ruled insufficient

Phase 2 — Reinforce Boundary and Exit Path

Purpose: Create a protected exit container.

Actions:

• define what must stop, reduce, revoke, pause, or separate;
• restore refusal rights;
• define safe exit path;
• define post-exit protections;
• block retaliation or forced reentry;
• prevent new scope expansion.

Validation:

BΣ ↑
exit path defined
forced reentry blocked

Phase 3 — Preserve Auditability

Purpose: Ensure safe exit does not erase evidence or responsibility.

Actions:

• preserve logs, records, contracts, permissions, state changes, access history, and decisions;
• document the decoupling rationale;
• document revocation and exit steps;
• preserve affected-node verification;
• maintain reviewability of the exit process.

Validation:

Au_exit ↑
state changes traceable
future dispute path remains inspectable

Phase 4 — Reduce Coupling and Dependency

Purpose: Lower harmful connection while preserving continuity where needed.

Actions:

• revoke invalid access;
• reduce dependency hooks;
• separate data, tools, roles, finances, permissions, symbolic authority, or workflows;
• reduce exposure;
• provide replacement pathways;
• preserve necessary support while removing extraction.

Validation:

d⊗/dt < 0
dependency pressure ↓
K / σ ↑
H_coupling growth slows

Phase 5 — Repair Extraction Damage / Support Post-Exit Stability

Purpose: Prevent decoupling from becoming abandonment.

Actions:

• repair damage caused by the coupling;
• provision restoration capacity;
• restore slack;
• repair identity, boundary, contract, economic, data, or access debt;
• provide successor topology where needed;
• prevent the affected node from carrying exit costs alone.

Validation:

R ↑
H ↓
post-exit stability improves
affected-node burden not increased

Phase 6 — Block Recapture and Proxy Relays

Purpose: Prevent the old coupling from returning indirectly.

Actions:

• identify recapture pathways;
• block proxy relays;
• reduce emergency reattachment risk;
• prevent informal access restoration;
• monitor pressure campaigns, dependency hooks, role reassignments, or symbolic reattachment;
• keep exit boundaries active through the review window.

Validation:

recapture paths named
proxy relays reduced
old coupling cannot silently reactivate

Phase 7 — Temporal Proof

Purpose: Confirm exit remains safe and stable over time.

Actions:

• monitor recurrence;
• monitor hidden debt;
• monitor recapture attempts;
• monitor post-exit boundary integrity;
• monitor successor topology;
• validate that the system no longer depends on invalid coupling.

Validation:

BΣ(t+n) ≥ BΣ(t)
d⊗/dt remains reduced or inactive
H_coupling(t+n) ≤ H_coupling(t)
recapture risk ↓
recurrence ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Safe Decoupling cannot validly proceed in that form.

The system must either:

• return to stabilization;
• restore boundary integrity;
• increase auditability;
• provision post-exit support;
• reduce dependency gradually;
• route to controlled decoupling;
• route to supersession;
• block recoupling or reattachment.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

Λ ≤ 0 or compatibility untrusted acknowledged
d⊗/dt < 0 for invalid coupling
BΣ(t+n) ≥ BΣ(t)
Au_exit preserved or increased
K / σ ↑
H_coupling ↓
recapture risk ↓
recurrence ↓ across U7

Safe Decoupling is not complete if:

exit remains symbolic
dependency remains structurally active
affected node is abandoned
auditability is lost during exit
old coupling returns through proxy relay
recapture risk remains high
separation optics improve while H increases

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• separation is announced but dependency remains active;
• access is revoked without post-exit support where support is required;
• the system frames abandonment as boundary repair;
• exit exists formally but remains materially unsafe;
• evidence is erased during departure;
• old coupling returns through proxy, emergency, or informal channels;
• harmed nodes carry exit cost alone;
• separation protects the powerful from responsibility;
• the system calls expulsion “safe decoupling”;
• the old dependency is renamed as “support.”

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Safe Decoupling cannot be declared complete until exit remains stable, support remains sufficient, and recapture risk declines over time.

Template:

Completion requires d⊗/dt < 0 for invalid coupling,
BΣ(t+n) ≥ BΣ(t),
H_coupling(t+n) ≤ H_coupling(t),
and recapture risk decreasing across U7.

Minimum temporal proof:

• exit remains real;
• old coupling does not silently reactivate;
• affected nodes are not abandoned;
• dependency does not return under a new name;
• audit trail remains intact;
• successor topology or post-exit stability persists;
• recurrence decreases.

10.3 Completion Statement

Canonical format:

This arc is complete only when invalid coupling has been safely reduced or ended, boundary integrity is stronger, exit remains viable, auditability is preserved, post-exit support is sufficient, and recapture risk declines over time.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

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

11.4 Related Laws / Invariants

INV — Boundary integrity is required for valid coupling.
INV — Exit must be real for consent-like participation to remain valid.
INV — Coupling requires compatibility.
INV — Hidden debt must be reduced, not relocated.
LAW — Forced coupling accumulates hidden debt.
LAW — Invalid coupling must be reduced before recoupling can be tested.
LAW — Recapture after exit reveals unresolved coupling geometry.
LAW — Φ improvement is not O restoration.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• memory deletion or deactivation;
• tool permission revocation;
• API access termination;
• agent autonomy rollback;
• data export and portability;
• user appeal and deletion paths;
• hidden state persistence;
• whether coupling returns through defaults, automation, or product design.

AI safe decoupling requires that revoked permissions, memory scopes, tool access, and data pathways do not silently reactivate through hidden system behavior.

12.2 Justice / Governance / Legitimacy

Check:

• whether harmed nodes can exit without losing protection;
• whether participation is required to preserve institutional legitimacy;
• whether separation is being used to avoid material repair;
• whether evidence and record remain intact;
• whether rank immunity protects the coupled system;
• whether public process pressures recapture.

JGL safe decoupling must distinguish protective exit from abandonment, retaliation, or legitimacy management.

12.3 Biology / Medicine

Conceptual systems mapping only.

Safe Decoupling in biological systems means reducing exposure, signal coupling, trigger dependency, maladaptive recurrence loops, or boundary stress while preserving necessary support, timing, and repair capacity.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

• debt lock-in;
• platform dependency;
• switching cost;
• survival-edge pressure;
• vendor lock-in;
• labor, data, attention, or ecological extraction;
• whether exit is formally available but practically punitive.

Economic safe decoupling must reduce dependency while preserving continuity, support, portability, and successor pathways.

12.5 CMS / Meaning / Archetypes

Check:

• identity fusion;
• symbolic dependency;
• sacred obligation;
• loyalty pressure;
• role capture;
• taboo against exit;
• spiritualized unity;
• whether separation is framed as betrayal.

Meaning systems require decoupling that preserves symbolic value without preserving coercive fusion or invalid obligation.

13. Machine-Readable Metadata

id: "RA-020"
title: "Safe Decoupling"
aliases:
  - "Safe Exit"
family_primary: "Coupling"
families_secondary:
  - "Core"
  - "Boundary"
  - "Contract"
  - "Security"
  - "Justice / Governance / Legitimacy"
  - "AI Governance"
  - "Economy"
  - "CMS"
  - "Cybernetics"
treatment: "Specialized Grammar"
status: "Canon-Ready"
scope:
  - "Local"
  - "Relational"
  - "Institutional"
  - "AI"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U2 boundary / access / permission / interface"
    - "often U1 dependency / capacity"
    - "often U3 control / enforcement"
    - "often U4 role / narrative / legitimacy"
  symptom_visible:
    - "U4 loyalty / agreement / role narrative"
    - "U6 field instability"
    - "Φ retention / continuity / cooperation"
  repair_required:
    - "same or lower than layer where coupling, dependency, or extraction is generated"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Λ reassessment → ⊗↓ coupling reduction → BΣ reinforcement → Π exit path → Σ post-exit invariants → Au preservation → Θ recapture damping → ℛ host / affected-node repair → Τ recapture validation"
  sequence:
    - "Λ"
    - "⊗↓"
    - "BΣ"
    - "Π"
    - "Σ"
    - "Au"
    - "Θ"
    - "ℛ"
    - "Τ"
state_variables:
  primary:
    - "Λ"
    - "⊗"
    - "BΣ"
    - "H"
  secondary:
    - "O"
    - "Au"
    - "K"
    - "R"
    - "ι"
    - "Φ"
diagnostics:
  - "σ(t)"
  - "𝓓(t)"
  - "τ_m"
  - "recurrence"
  - "recapture risk"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Forced Coupling"
  - "Parasitic Extraction"
  - "Silent Extraction"
  - "Exit Denial"
  - "Coercive Dependency"
  - "Dependency Capture"
  - "Boundary Collapse"
  - "Fusion Collapse"
  - "Interface Capture"
  - "Contract Drift"
  - "Recapture After Exit"
  - "Proxy-Relay Drift"
  - "Restoration Bypass"
linked_restoration_arcs:
  - "RA-005"
  - "RA-010"
  - "RA-011"
  - "RA-018"
  - "RA-019"
  - "RA-021"
  - "RA-027"
  - "RA-045"
  - "RA-056"
  - "RA-065"
  - "RA-079"
anti_patterns:
  - "Abandonment Theater"
  - "Symbolic Exit"
  - "Punitive Exit"
  - "Proxy Recapture"
  - "Evidence Erasure"
  - "Dependency Rebranding"
  - "Expulsion-as-Repair"
completion_tests:
  - "Λ ≤ 0 or compatibility untrusted acknowledged"
  - "d⊗/dt < 0 for invalid coupling"
  - "BΣ(t+n) ≥ BΣ(t)"
  - "Au_exit preserved or increased"
  - "K / σ increases"
  - "H_coupling decreases"
  - "recapture risk decreases"
  - "recurrence decreases across U7"
summary: "Safe Decoupling restores boundary-safe exit from extractive, coercive, invalid, over-fused, or compatibility-negative coupling while preserving auditability, post-exit support, and protection against recapture."

Final Calibration Rule

Safe Decoupling answers six questions:

What hidden debt is being generated by unsafe coupling?
What boundary, dependency, access, or exit path must be repaired during separation?
What auditability proves the exit and coupling reduction are traceable?
What coupling, relay, dependency, or reattachment path must remain blocked?
What trajectory becomes viable once exit is safe and recapture risk declines?
How is decoupling proven over time without abandonment, snap-back, or proxy recapture?