Circuit Breaker¶
Interrupt or restrict a coupled flow when overload signals indicate cascade risk, then re-open cautiously under feedback.
The Diagnostic Story¶
Symptom: One overloaded component is dragging everything coupled to it down with it. Load keeps pouring into the part that is already failing, latency and errors climb, and the damage spreads outward faster than anyone can intervene by hand. Throughput is no longer the problem; survival is.
Pivot: Put a controllable seam between the failing component and its callers, and let an observed overload signal open it, cutting or shedding inbound flow instead of forwarding it into the fire.
Resolution: The cascade stops at the seam; the protected component gets room to stabilize, then flow is re-admitted cautiously under feedback rather than restored all at once. You have traded some throughput and fairness for continued viability of the whole.
Reach for this when you hear…¶
[on-call SRE] “The database is melting and every retry is making it worse: stop sending it traffic before the whole site goes down.”
[markets] “Prices are in free fall and the order flow is feeding the panic; halt trading before it cascades.”
[power grid] “That line is overloaded: trip the relay and shed it before it takes the substation with it.”
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
Continued connection under a detectable danger state can propagate a local fault or overload into a larger cascade.
Show the applicability expression
Applicability expression1 distinct condition
groundedpartly groundedopen
1 condition, all required.
1Required in every casenumbered 1–1
These hold no matter which pattern applies.
Threshold-detectable fault propagation · open
A connected flow can propagate a local fault or overload after a detectable danger threshold is crossed.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this condition set, the requirement is: A connected flow can propagate a local fault or overload after a detectable danger threshold is crossed.
Other requirements and context (2)
Why these sit outside the expression
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Application gateA bounded local interruption is preferable to the prospective cascade.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this archetype, the relevant application gate is: A bounded local interruption is preferable to the prospective cascade. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Solution feasibilityThe connection can be isolated and later reset under a governed policy.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this archetype, the relevant feasibility condition is: The connection can be isolated and later reset under a governed policy. It identifies something that must be possible or available for the intervention to be workable.
Coverage
0 of 1 conditions grounded · 1 open.
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 (3)
- Boundary: Defines system limits.
- Feedback: Outputs influence inputs.
- Sampling (Representativeness): Representative subset selection.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Half-Open Recovery · risk or failure variant · likely subtype
A cautious recovery state in which limited flow is reintroduced after a breaker has opened.
Editorial Notes¶
Problem Classification¶
Classification: Instability, Runaway Feedback & Cascades → Coupled-Network Cascade & Spread
Problem kernel: coupled overload propagates until the flow pathway is interrupted
Rationale: Both reviewers identify the same causal center, and the frozen essence explicitly describes overload propagating through a coupled flow until temporary interruption becomes necessary. Fault containment is nearby when a failed component eliminates a whole function, but this record centers pathway-borne amplification and cascade risk rather than absence of alternate service or bounded failure domains.
Boundary considered: Fragility, Failure & Continuity Risk → Fault Containment & Bounded Service Loss
Why this classification prevailed: Cascade failure concerns disturbance spread and amplification along coupled pathways; fault containment concerns preserving essential function when a local component or partner fails.
Review outcome: Reconciled after independent review; high confidence.