Critical Dependency Disconnect¶
Procedure — instantiates Rupture Containment
A controlled disconnection or pause of a dependency path that would otherwise transmit overload, contamination, compromise, or conflict into adjacent systems.
Critical Dependency Disconnect is the procedure of deliberately cutting a coupling — a feed, a link, a supply, an interconnection — before the trouble on one side of it flows through into the other. Its defining feature is that the object of the intervention is not a region or a compartment but a dependency edge: the wire, pipe, contract, or interface along which overload, contamination, or compromise would travel. The procedure maps which couplings carry the danger, sheds them in a controlled order, and — because severing a live dependency starves whatever relied on it — arranges an alternate feed and a clear handoff of who now owns the disconnected side. It is a planned kill-switch pull, not a wall.
Example¶
A regional electricity grid is hit by a fault that trips a major generator; frequency starts to sag and the disturbance begins rippling outward, threatening to drag interconnected areas down with it in a cascading blackout. The grid operator's containment move is a controlled disconnection: rather than let the sick region keep pulling on its neighbors, they intentionally open the tie-lines and split the network into self-contained islands — the "controlled islanding" playbook.[n1]
They do it in a mapped order — which interconnections, in which sequence, to leave each island roughly balanced between its own generation and load. The affected island is allowed to shed load or go dark, but its neighbors, now electrically separated, keep their own generation matched to their own demand and ride through. Critical loads inside the troubled island are transferred to local backup generation — a temporary service path — while a designated regional control desk takes ownership of the islanded segment until the tie-lines can be safely re-closed. The disturbance stops at the cut, not at a wall.
How it works¶
- Map the couplings that carry the danger. Enumerate the dependency edges — interconnections, feeds, shared queues, supply links — and identify which ones would transmit the overload or compromise, and in what order they must be shed to avoid making things worse.
- Cut in a controlled sequence. Open or pause the mapped couplings deliberately, timed and ordered, rather than letting them trip chaotically or severing them all at once.
- Feed the orphaned side. Because disconnection starves whatever depended on the cut link, stand up an alternate route — backup generation, a substitute supplier, a manual process — for the function that must survive.
- Hand off ownership of the severed side. Name who now operates and answers for the disconnected segment while it runs detached.
The move is edge-oriented and active: it protects by breaking a specific coupling and re-routing around it, not by closing a pre-built compartment or drawing a line across a continuous region.
Tuning parameters¶
- Cutoff severity — whether the dependency is fully severed or merely throttled/paused. A hard cut stops transmission decisively but strands the far side; a soft throttle preserves some flow but risks leaking the disturbance.
- Shed sequence and timing — the order and speed of disconnection. A well-ordered shed keeps each side balanced; the wrong order can trip protective systems and widen the blackout.
- Alternate-path capacity — how much function the temporary feed can carry. More backup preserves continuity but costs standing reserve; too little means the disconnect saves the neighbors by sacrificing the disconnected side.
- Reconnection guard — how conservatively the cut is re-closed. Cautious reconnection avoids re-transmitting the fault; hasty reconnection re-couples before the far side is stable.
When it helps, and when it misleads¶
Its strength is precision: where the danger travels through identifiable couplings, cutting exactly those edges stops the cascade while leaving everything not on those edges running — far less collateral than a blanket shutdown. It shines when the coupling is the propagation route and an alternate feed exists.
Its failure mode is a mismapped or hidden dependency: cut the wrong edges, or miss a back-channel coupling, and the disturbance transmits anyway — or the disconnect itself strands a critical load that had no alternate feed and creates a new failure. The classic misuse is pulling the plug without arranging the temporary path or the handoff, so the "contained" side simply dies and no one is left owning it. The guarding discipline is to validate the dependency map against real topology (including the informal couplings that never make the diagram) and to confirm the alternate feed and the ownership handoff are in place before the cut.
How it implements the components¶
Critical Dependency Disconnect fills the coupling-severing, continuity-preserving side of the archetype:
dependency_shed_map— the ordered map of which couplings carry the danger and in what sequence to shed them is the procedure's core artifact.temporary_service_path— the alternate feed (backup generation, substitute supplier, manual fallback) keeps essential function alive on the starved side.authority_handoff— the procedure names who takes ownership and control of the disconnected segment while it runs detached.
It does not seal a pre-built compartment behind a physical partition (rupture_boundary, isolation_rule, propagation_barrier) — that is Bulkhead Isolation, its procedure-type twin, which closes a fixed cell rather than cutting a coupling. Nor does it triage and time entry/exit across a fresh line (damage_triage_rule, release_and_exit_rule) — that is Quarantine or Firebreak.
Related¶
- Instantiates: Rupture Containment — supplies the controlled coupling-cut that stops transmission through a dependency path.
- Sibling mechanisms: Bulkhead Isolation · Quarantine or Firebreak · Service Fault Isolation · Blast or Fire Containment · Crack Arrester · Financial Ring Fence · Incident Containment Zone · Conflict Containment Agreement · Trust Stabilization Message
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: Critical Dependency Disconnect operates as a direct treatment or transformation intended to change the target state or representation because it a controlled disconnection or pause of a dependency path that would otherwise transmit overload, contamination, compromise, or conflict into adjacent systems.
Independent corroboration: The frozen evidence defines Critical Dependency Disconnect as 'A controlled disconnection or pause of a dependency path that would otherwise transmit overload, contamination, compromise, or conflict into adjacent systems', so its operative form is Intervention, Treatment & Transformation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Safety engineering cohered isolation and controlled shutdown of a dependency path to prevent overload, contamination, or fault propagation.
Related originating lineages:
- Disaster Management & Risk Reduction — Containment doctrine supplies deliberate firebreaks and quarantine boundaries under spreading hazards.
- Security Studies & Intelligence Analysis — Network defense supplies segmentation and disconnection of compromised dependencies.
Review resolution: Controlled islanding, quarantine, and cyber isolation are genuine convergent engineering, disaster, and security lineages; multi-domain reach is safer than claiming literal universality.
Attribution caveat: Isolation procedures recur independently in electrical, process, biological, and security systems.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Controlled islanding is the power-system practice of intentionally splitting an interconnected grid into self-sustaining islands during a severe disturbance, so a fault in one area cannot cascade across the whole network. It is the grid-scale example of deliberately shedding a coupling in a planned order rather than letting protective relays trip chaotically. ↩