Rupture Containment¶
Limit damage after a break by containing fracture propagation and stabilizing adjacent structures.
The Diagnostic Story¶
Symptom: A break has occurred — a failure, a breach, a conflict, a contamination — and damage is beginning to travel through the connections between the broken part and the rest of the system. Everyone is focused on fixing the broken part while neighboring structures start to weaken. The system has no bounded containment response, so it swings between denial and total shutdown.
Pivot: Identify the rupture boundary, isolate the fracture paths, and stabilize adjacent elements — fast enough to stop propagation but without over-isolating, abandoning the affected zone, or destroying the continuity needed for later repair. Define what repair or replacement will look like before the containment boundary becomes permanent.
Resolution: A local rupture stays local rather than becoming a system-wide cascade. Stable regions remain protected, the distinction between affected, exposed, and unaffected areas becomes clear, and the transition from emergency containment to repair or recovery is accountable rather than indefinitely deferred.
Reach for this when you hear…¶
[incident response] “Before we try to fix anything, we need to isolate the affected services so the blast radius stops growing.”
[public health] “We don't have a cure yet but we can stop the spread by tracing contacts and quarantining the exposure ring before we work backward to the index case.”
[organizational crisis] “The division has real problems but pulling it into the parent company's operations right now will just contaminate the rest of the portfolio.”
When This Archetype Applies¶
Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.
Diagnostic problem
A component, relationship, structure, or process has ruptured or is about to rupture, and damage may propagate into adjacent systems.
What this problem means
A rupture is rarely only a local event. It travels through seams, dependencies, relationships, flows, trust, obligations, shared infrastructure, or shared meaning. The structural problem is that the broken part remains coupled to unbroken parts.
Without containment, the system may overreact with total shutdown or underreact by focusing only on the visible break. Both are dangerous. Total shutdown creates unnecessary collateral damage; narrow repair lets propagation continue through hidden paths.
Show the applicability expression
Applicability expression5 distinct conditions
groundedpartly groundedopen
5 conditions, all required.
5Required in every casenumbered 1–5
These hold no matter which pattern applies.
Rupture already occurred · grounded
A break, breach, fracture, conflict, overload, contamination, compromise, or trust failure has already occurred or is no longer realistically avoidable.
A local failure can become a cascade; a breach can become a system compromise; a conflict can become a feud; a crack can become structural failure; a loss can become panic; a trust rupture can become legitimacy collapse. The narrower requirement in this condition set is: A break, breach, fracture, conflict, overload, contamination, compromise, or trust failure has already occurred or is no longer realistically avoidable.
Connected propagation routes · grounded
The rupture is connected to other parts of the system through physical continuity, dependencies, communication channels, obligations, incentives, shared resources, reputation, or load transfer.
It travels through seams, dependencies, relationships, flows, trust, obligations, shared infrastructure, or shared meaning. The narrower requirement in this condition set is: The rupture is connected to other parts of the system through physical continuity, dependencies, communication channels, obligations, incentives, shared resources, reputation, or load transfer.
Propagation exceeds local damage · grounded
Damage propagation would be more costly, dangerous, or legitimacy-damaging than local damage alone.
Total shutdown creates unnecessary collateral damage; narrow repair lets propagation continue through hidden paths. The narrower requirement in this condition set is: Damage propagation would be more costly, dangerous, or legitimacy-damaging than local damage alone.
Actionable containment boundary · grounded
The system can define a temporary containment boundary and can act on at least some propagation routes.
Use Rupture Containment when a break is active, imminent, or unavoidable and the largest danger is propagation. The narrower requirement in this condition set is: The system can define a temporary containment boundary and can act on at least some propagation routes.
Protect adjacent essentials · grounded
Essential adjacent functions, relationships, flows, or people need protection while the rupture zone is isolated or stabilized.
A component, relationship, structure, or process has ruptured or is about to rupture, and damage may propagate into adjacent systems. The narrower requirement in this condition set is: Essential adjacent functions, relationships, flows, or people need protection while the rupture zone is isolated or stabilized.
Other requirements and context (1)
Why these sit outside the expression
Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.
Supporting contextImmediate repair is not possible, not yet safe, or would spread damage if attempted before stabilization.
It is especially useful when immediate full repair would be unsafe, slow, or impossible. In this archetype, the relevant contextual consideration is: Immediate repair is not possible, not yet safe, or would spread damage if attempted before stabilization. It helps interpret the situation or strengthens the practical case for examining the archetype.
Coverage
5 of 5 conditions grounded.
Mechanisms / Implementations¶
- Crack Arrester (
crack_arrester): This is a engineering_feature mechanism. - Bulkhead Isolation (
bulkhead_isolation): This is a structural_separation mechanism. - Incident Containment Zone (
incident_containment_zone): This is a operational_protocol mechanism. - Quarantine or Firebreak (
quarantine_or_firebreak): This is a boundary_control mechanism. - Financial Ring Fence (
financial_ring_fence): This is a governance_or_legal_structure mechanism. - Blast or Fire Containment (
blast_or_fire_containment): This is a physical_safety_feature mechanism. - Service Fault Isolation (
service_fault_isolation): This is a technical_architecture mechanism. - Conflict Containment Agreement (
conflict_containment_agreement): This is a social_or_governance_protocol mechanism. - Trust Stabilization Message (
trust_stabilization_message): This is a communication_protocol mechanism. - Critical Dependency Disconnect (
critical_dependency_disconnect): This is a emergency_control mechanism.
- Blast or Fire Containment: A safety mechanism that contains explosive, thermal, chemical, or fire damage within a defined boundary and protects adjacent structures.
- Bulkhead Isolation: A compartmentalization mechanism that prevents failure, flooding, fire, contamination, or overload in one compartment from spreading to others.
- Conflict Containment Agreement: A negotiated boundary that prevents a rupture in one relationship, faction, or issue from expanding into broader retaliation, polarization, or institutional breakdown.
- Crack Arrester: A structural feature that stops or slows fracture propagation by interrupting the path along which a crack can travel.
- Critical Dependency Disconnect: A controlled disconnection or pause of a dependency path that would otherwise transmit overload, contamination, compromise, or conflict into adjacent systems.
- Financial Ring Fence: A legal, accounting, or organizational mechanism that separates liabilities, assets, losses, or obligations so one rupture does not destabilize the wider system.
- Incident Containment Zone: An operational boundary that defines the affected scope, restricts propagation routes, assigns containment owners, and stabilizes adjacent operations during an incident.
- Quarantine or Firebreak: A boundary mechanism that separates affected from unaffected regions to slow biological, informational, cyber, ecological, or social spread.
- Service Fault Isolation: A software, infrastructure, or operational mechanism that isolates a failing service, dependency, queue, shard, or region so the fault does not cascade.
- Trust Stabilization Message: A communication mechanism that acknowledges the rupture, states containment boundaries, reduces rumor-driven propagation, and preserves enough confidence for stabilization.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (2)
- Fault Tolerance: Continue operating under failure.
- Stress and Rupture: Accumulated tension leads to break.
Also references 9 related abstractions
- Boundary: Defines system limits.
- Continuity vs. Rupture: Gradual vs abrupt change.
- Coupling: Interdependence among subsystems.
- Damping: Reduce oscillations.
- Fail-Safe: Default to safe state on failure.
- Flow: Structured movement of energy, matter, or information.
- Functional Redundancy (Degeneracy): Multiple pathways fulfill same function.
- Observability: Infer internal state externally.
- Resilience: Absorb shocks and adapt.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Cascade Rupture Containment · scale variant · recognized
Containment focused on preventing a local break from triggering sequential failures through dependent parts of a system.
Trust Rupture Containment · governance variant · recognized
Containment focused on keeping a breach of trust, conflict, scandal, or relationship break from spreading into broader legitimacy collapse or retaliation.
Physical Fracture Containment · domain variant · recognized
Containment of cracks, blasts, fires, floods, structural damage, or material failure so damage does not propagate physically.
Staggered Parallel Sacrificial Interruption · staged rupture variant · recognized
Offset the rupture thresholds or actuation positions of parallel sacrificial links so interruption proceeds sequentially rather than demanding simultaneous breakage.
Editorial Notes¶
Problem Classification¶
Classification: Fragility, Failure & Continuity Risk → Fault Containment & Bounded Service Loss
Problem kernel: local rupture can propagate damage into adjacent systems
Rationale: A component, relationship, structure, or process has failed or is near rupture, and that local break can propagate into adjacent systems unless the failed region is isolated. Source-pathway-receptor propagation requires a harmful source migrating, diffusing, transferring, or establishing in new targets; the broader evidence instead centers bounding service and damage loss after a local fault.
Boundary considered: Hazard Exposure & Uncontained Harm → Source–Pathway–Receptor Propagation
Why this classification prevailed: Fault containment bounds the consequences of a failed component or region; source-pathway-receptor control interrupts a hazard's migration or transfer from a source into new receptors.
Review outcome: Adjudicated after independent review; high confidence.