0. Registry Classification

1. Purpose

1.1 What This Arc Repairs

Controlled Decoupling repairs conditions where a coupling has become invalid, extractive, coercive, over-fused, compatibility-negative, or structurally unsafe to maintain.

It applies when continued connection, access, dependency, contract, role, interface, memory, permission, or participation is generating hidden debt faster than the system can restore coherence.

This arc repairs invalid coupling by:

• reassessing compatibility;
• reducing coupling intensity;
• preserving boundary integrity;
• restoring exit;
• protecting identity and continuity during separation;
• preserving auditability and evidence;
• reducing dependency and recapture pathways;
• preventing snap-back into the old coupling geometry;
• routing repair to the host, affected node, or successor topology.

Controlled Decoupling is the canonical restoration arc for separating systems without collapse, abandonment, retaliation, or hidden recapture.

1.2 Core Restoration Function

This arc restores boundary-safe separation by reducing invalid coupling, protecting exit and identity continuity, preserving auditability, reducing dependency pressure, and validating that the system no longer requires the damaged coupling to remain stable.

Controlled Decoupling prevents separation from becoming either abandonment or recapture.

2. Use Conditions

2.1 When to Apply

Use this arc when:

• compatibility is negative, uncertain, or no longer valid;
• coupling continues through dependency rather than coherence;
• exit is technically possible but practically unsafe;
• participation is maintained by coercion, exhaustion, survival pressure, or role capture;
• a contract, interface, relation, memory, tool, workflow, or institution is extracting more than it repairs;
• decoupling is needed but sudden separation would cause collapse;
• coupling has become parasitic, over-fused, coercive, or identity-binding;
• the system needs to reduce dependency before clean release is possible;
• recoupling is being attempted before boundary repair or compatibility validation;
• old coupling pathways keep reactivating after attempted exit.

Examples:

• an AI agent retains tool, memory, or API coupling after scope has become invalid;
• an institution depends on a harmed node’s continued participation to preserve legitimacy;
• an economic relationship continues because exit would threaten survival;
• a platform or contract makes departure technically available but materially punitive;
• a relationship, role, or symbolic structure has become over-fused and identity-capturing;
• a security or governance interface remains active because no successor topology exists yet.

2.2 When Not to Apply

Do not apply this arc when:

• active harm is still cascading and emergency stabilization is required first;
• immediate safe decoupling is already possible and no staged control is needed;
• compatibility is positive and boundary repair plus recoupling is the better path;
• decoupling would abandon affected nodes without support;
• the system lacks any viable exit or replacement path;
• separation would destroy auditability;
• the decoupling plan shifts burden to the harmed node;
• the coupling is invalid due to formal contract failure and requires contract release first;
• the correct move is supersession rather than partial decoupling.

Controlled 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, load shedding, safe 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:

Coupling is valid only when compatibility remains positive and exit remains real.

4. Restoration Objective

4.1 Canonical Objective

Restore coherence by reducing invalid coupling, preserving boundary integrity, protecting exit, reducing dependency pressure, and preventing recapture while routing repair to the damaged node or successor topology.

Formal objective:

Λ reassessed
d⊗/dt < 0
BΣ ↑
exit viable
Au preserved
K / σ ↑
H_coupling ↓
recapture risk ↓

Expanded objective:

Separate the coupled systems enough that each can stabilize, repair, or transition without continuing the invalid dependency geometry that generated hidden debt.

4.2 Non-Goals

This arc does not aim to:

• punish through abandonment;
• erase history;
• destroy evidence;
• force clean separation faster than capacity allows;
• preserve invalid coupling for comfort;
• hide extraction behind “transition” language;
• shift burden to the harmed node;
• restore the old relationship by default;
• sever all contact when scoped decoupling is sufficient;
• treat exit as real when survival, identity, role, data, or material continuity would collapse.

5. Operator Sequence

5.1 Minimal Operator Scaffold

Λ reassessment → ⊗↓ coupling reduction → Π exit boundary → Σ invariant lock → Au preservation → Θ dependency/gain reduction → ℛ host repair → Τ recapture validation

Universal grammar alignment:

Σ + Θ → Π → ⊗↓ → ℛ → Au + FI → Τ → Temporal Proof

Controlled Decoupling may route into compatibility recoupling, safe decoupling, contract release, fusion reversal, parasitic extraction recovery, reintegration membrane, or supersession.

5.2 Operator Step Table

5.3 Sequence Notes

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

Controlled Decoupling does not assume that all coupling is invalid. It reduces only coupling that cannot currently meet compatibility, consent, boundary, or coherence requirements.

The following steps cannot be skipped:

compatibility reassessment
coupling map
exit boundary
audit preservation
dependency reduction
host / affected-node repair
recapture validation

If decoupling increases hidden debt by abandoning support layers, the arc has failed.

If decoupling is announced but dependency remains unchanged, the arc has become theater.

6. Restoration Phases

Phase 0 — Identify Invalid Coupling

Purpose: Name the coupling that is generating harm, debt, dependency, or incoherence.

Actions:

• identify coupling path;
• identify access, dependency, role, permission, contract, interface, or memory link;
• identify who or what benefits from the coupling;
• identify who or what carries the burden;
• identify whether compatibility is uncertain, negative, expired, or untested.

Validation:

coupling path named
burden path visible
Λ requires reassessment

Phase 1 — Reassess Compatibility

Purpose: Determine whether the coupling can remain valid.

Actions:

• test Λ;
• distinguish compatibility from dependency;
• distinguish cooperation from compliance;
• distinguish loyalty from lack of exit;
• identify asymmetry, coercion, or scope drift;
• identify whether recoupling is inadmissible.

Validation:

Λ clarified
dependency separated from compatibility
invalid or uncertain coupling named

Phase 2 — Stabilize Exit Boundary

Purpose: Create a safe boundary around the decoupling process.

Actions:

• define what will be paused, reduced, revoked, separated, or transitioned;
• restore refusal and exit rights;
• protect affected nodes;
• prevent retaliation or forced reentry;
• prevent new scope expansion during exit.

Validation:

BΣ ↑
exit boundary defined
forced reentry blocked

Phase 3 — Preserve Auditability

Purpose: Ensure decoupling does not erase the causal or contractual record.

Actions:

• preserve logs, records, terms, contracts, permissions, decisions, and state changes;
• document the coupling reduction;
• document access revocations;
• preserve affected-node verification;
• maintain reviewability of exit conditions.

Validation:

Au preserved
terms and state changes traceable
future dispute path remains inspectable

Phase 4 — Reduce Coupling and Dependency

Purpose: Lower connection intensity without causing collapse.

Actions:

• reduce access;
• reduce dependency;
• reduce data, tool, labor, financial, identity, or symbolic coupling;
• create replacement pathways where needed;
• decouple nonessential interfaces first;
• avoid sudden removal of survival-critical supports.

Validation:

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

Phase 5 — Repair Host / Affected Node / Successor Path

Purpose: Prevent decoupling from becoming abandonment.

Actions:

• repair damage caused by invalid coupling;
• provision replacement support or successor topology;
• restore boundary capacity;
• restore slack;
• restore safe participation elsewhere if needed;
• close extraction channels.

Validation:

R ↑
H ↓
affected-node capacity preserved
successor path viable

Phase 6 — Block Recapture

Purpose: Prevent old coupling geometry from returning under a new name.

Actions:

• identify recapture paths;
• block proxy relays;
• reduce dependency hooks;
• monitor renewed access requests;
• enforce scope limits;
• prevent symbolic, procedural, or emergency reattachment.

Validation:

recapture paths named
relay hooks reduced
old coupling cannot silently reactivate

Phase 7 — Temporal Proof

Purpose: Confirm separation remains stable over time.

Actions:

• monitor recurrence;
• monitor hidden debt;
• monitor snap-back;
• monitor affected-node stability;
• test whether exit remains viable;
• validate successor topology.

Validation:

BΣ(t+n) ≥ BΣ(t)
d⊗/dt remains reduced or stable
τ_m ↓
recurrence ↓
recapture risk ↓

7. Gates

7.1 Required Gates

7.2 Gate Failure Rule

If any required gate fails:

∅ — Controlled Decoupling cannot validly proceed in that form.

The system must either:

• return to stabilization;
• restore boundary integrity;
• increase auditability;
• reduce dependency gradually;
• provide successor support;
• route to safe decoupling;
• route to contract release;
• route to supersession.

8. Diagnostics

8.1 Required Diagnostic Trends

8.2 Arc-Specific Diagnostic Thresholds

Suggested thresholds:

Λ assessed before coupling continues
d⊗/dt < 0 for invalid coupling
BΣ(t+n) ≥ BΣ(t)
Au preserved through exit
K / σ ↑
H_coupling ↓
recapture risk ↓
recurrence ↓ across U7

Controlled Decoupling is not complete if:

coupling remains active through dependency
exit is symbolic
auditability is lost during separation
affected node is abandoned
old coupling returns through proxy relay
Λ is assumed instead of tested
Φ improves through retention while O declines

9. Anti-Patterns / False Restorations

9.1 Common False Versions

This arc is being simulated, not executed, if:

• separation is announced but dependency remains unchanged;
• exit exists formally but is materially punitive;
• access is revoked without replacement support where support is required;
• the harmed node is made responsible for maintaining the transition;
• coupling returns through an informal proxy;
• evidence is erased during separation;
• the system frames abandonment as “healthy boundary”;
• the system frames continued dependency as “stability”;
• symbolic distance replaces actual access reduction;
• the old contract continues under new language;
• compatibility is assumed from silence after exit.

9.2 Named Anti-Pattern Links

10. Completion Criteria

10.1 Post-State Signature

10.2 Temporal Proof

Controlled Decoupling cannot be declared complete until separation remains stable after delay, pressure, and recurrence testing.

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:

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

10.3 Completion Statement

Canonical format:

This arc is complete only when invalid coupling has been reduced, exit is viable, boundary integrity is preserved, auditability remains intact, dependency pressure is lower, and the old coupling geometry does not recur through snap-back or proxy recapture.

11. Cross-Links

11.1 Related Restoration Arcs

11.2 Related Failure Modes

11.3 Related Diagnostics

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

11.4 Related Laws / Invariants

INV — Boundary integrity is required for valid coupling.
INV — Coupling requires compatibility.
INV — Exit must be real for consent-like participation to remain valid.
LAW — Forced coupling accumulates hidden debt.
LAW — Invalid coupling must be reduced before recoupling can be tested.
LAW — Recoupling before compatibility recreates failure geometry.
LAW — Hidden dependency can preserve apparent stability while degrading coherence.
LAW — Φ improvement is not O restoration.

12. Domain Notes

12.1 AI / Cognitive Infrastructure

Check:

• tool access;
• memory coupling;
• API permissions;
• delegated agency;
• persistent context;
• automated workflows;
• model-to-user dependency;
• platform lock-in;
• appeal and export pathways;
• whether old coupling persists through hidden state.

AI controlled decoupling requires reducing invalid memory, tool, agent, data, or policy coupling while preserving auditability and rollback.

12.2 Justice / Governance / Legitimacy

Check:

• whether harmed nodes can exit process without losing protection;
• whether institutions depend on participation to preserve legitimacy;
• whether public process coerces continued exposure;
• whether contract or role ties remain valid;
• whether rank immunity preserves invalid coupling;
• whether separation is used as retaliation.

JGL controlled decoupling must distinguish protective separation from abandonment, retaliation, or legitimacy management.

12.3 Biology / Medicine

Conceptual systems mapping only.

Controlled Decoupling in biological systems means reducing exposure, signal coupling, dependency loops, trigger density, or maladaptive recurrence pathways without collapsing necessary support or repair capacity.

Not diagnosis.

Not treatment.

Not medical advice.

12.4 Economy

Check:

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

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

12.5 CMS / Meaning / Archetypes

Check:

• identity fusion;
• symbolic dependency;
• role capture;
• sacred obligation;
• pressure to remain connected for meaning, loyalty, duty, or spiritualized unity;
• whether separation is framed as betrayal.

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

13. Machine-Readable Metadata

id: "RA-010"
title: "Controlled Decoupling"
aliases:
  - "Decoupling"
family_primary: "Coupling"
families_secondary:
  - "Core"
  - "Boundary"
  - "Contract"
  - "Security"
  - "Cybernetics"
  - "Justice / Governance / Legitimacy"
  - "AI Governance"
  - "Economy"
  - "CMS"
treatment: "Canon Parent Arc"
status: "Canon-Ready"
scope:
  - "Local"
  - "Relational"
  - "Institutional"
  - "AI"
  - "Economic"
  - "Civilizational"
  - "Cross-Domain"
u_layers:
  failure_origin:
    - "often U2 boundary / interface / permission"
    - "often U1 dependency / capacity"
    - "often U3 control path"
    - "often U4 role / narrative"
  symptom_visible:
    - "U4 relationship / legitimacy narrative"
    - "U6 field instability"
    - "Φ continuity / retention / cooperation"
  repair_required:
    - "same or lower than dependency, boundary, access, or coupling layer"
  validation:
    - "U5"
    - "U6"
    - "U7"
operators:
  scaffold: "Λ reassessment → ⊗↓ coupling reduction → Π exit boundary → Σ invariant lock → Au preservation → Θ dependency/gain reduction → ℛ host repair → Τ recapture validation"
  sequence:
    - "Λ"
    - "⊗↓"
    - "Π"
    - "Σ"
    - "Au"
    - "Θ"
    - "ℛ"
    - "Τ"
state_variables:
  primary:
    - "Λ"
    - "⊗"
    - "BΣ"
    - "H"
  secondary:
    - "O"
    - "Au"
    - "K"
    - "R"
    - "Φ"
diagnostics:
  - "𝓓(t)"
  - "τ_m"
  - "recurrence"
  - "recapture risk"
  - "Φ/O divergence"
gates_required:
  - "FI-Gate"
  - "HR-Gate"
  - "MS-Gate"
  - "Au-Actuation"
  - "BΣ-Gate"
  - "Λ-Gate"
  - "☷ᵢ"
linked_failure_modes:
  - "Invalid Coupling"
  - "Forced Coupling"
  - "Coercive Dependency"
  - "Parasitic Extraction"
  - "Silent Extraction"
  - "Fusion Collapse"
  - "Boundary Collapse"
  - "Exit Denial"
  - "Dependency Capture"
  - "Interface Capture"
  - "Contract Drift"
  - "Recapture After Exit"
linked_restoration_arcs:
  - "RA-005"
  - "RA-006"
  - "RA-007"
  - "RA-011"
  - "RA-018"
  - "RA-019"
  - "RA-020"
  - "RA-021"
  - "RA-027"
  - "RA-045"
  - "RA-079"
anti_patterns:
  - "Abandonment Theater"
  - "Symbolic Decoupling"
  - "Proxy Recapture"
  - "Punitive Exit"
  - "Evidence Erasure"
  - "Dependency Preservation"
  - "Retention Theater"
completion_tests:
  - "Λ assessed before coupling continues"
  - "d⊗/dt < 0 for invalid coupling"
  - "BΣ(t+n) ≥ BΣ(t)"
  - "Au preserved through exit"
  - "K / σ increases"
  - "H_coupling decreases"
  - "recapture risk decreases"
  - "recurrence decreases across U7"
summary: "Controlled Decoupling reduces invalid or compatibility-negative coupling while preserving boundary integrity, auditability, exit viability, identity continuity, and post-separation repair capacity."

Final Calibration Rule

Controlled Decoupling answers six questions:

What hidden debt is being generated by invalid coupling?
What boundary, access, dependency, or exit path must be repaired during separation?
What auditability proves the coupling reduction is traceable?
What coupling must be reduced, paused, revoked, or redesigned before compatibility can be retested?
What trajectory becomes viable once dependency and recapture risk decrease?
How is decoupling proven over time without becoming abandonment, snap-back, or proxy recapture?