Skip to content

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.”

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.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Also references 9 related abstractions

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.