Flow Diversion / Rerouting¶
Redirect flow through an alternate viable path when the current route becomes blocked, overloaded, or harmful, rather than stopping the flow.
The Diagnostic Story¶
Symptom: The flow needs to continue, but the current path has become blocked, overloaded, hazardous, or unavailable. Stopping the flow entirely would be worse than a detour. The failure is not that total demand is too high; it is that this particular path cannot be used right now while another viable route may exist.
Pivot: Detect the path impairment, identify a viable alternate route, and redirect flow through it while monitoring whether the diversion preserves the intended function without shifting harm or overload to another bottleneck. The alternate path must be checked for capacity and safety before major redirection begins.
Resolution: Flow reaches its destination or a safe holding state through the alternate route, and the path-specific failure is bypassed without stopping the system or shedding load. Routing decisions are auditable, the original path can be reentered when conditions change, and affected parties are informed when the path change matters.
Reach for this when you hear…¶
[network operations] “The primary link is congested so we reroute around it, but if we push everything onto the secondary we will just overload that one instead.”
[logistics coordinator] “The port is jammed so I need to redirect through the secondary port fast, but I need to know it has the capacity before I commit the shipments.”
[emergency management] “Route A is blocked by the incident so we push evacuation traffic through the residential streets, but we have to monitor for gridlock before it cascades.”
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
A flow's current path is blocked, congested, hazardous, compromised, unavailable, or strategically unacceptable while the flow's purpose must continue.
Show the applicability expression
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Current path unusable · open
The currently used path for a flow is blocked, congested, hazardous, compromised, failing, or unavailable.
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: The currently used path for a flow is blocked, congested, hazardous, compromised, failing, or unavailable.
Destination continuity required · open
The transported quantity or service must continue reaching its destination.
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: The transported quantity or service must continue reaching its destination.
Other requirements and context (1)
Why these sit outside the expression
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Solution feasibilityA viable alternate route exists or can be created.
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: A viable alternate route exists or can be created. It identifies something that must be possible or available for the intervention to be workable.
Coverage
0 of 2 conditions grounded · 2 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 (9)
- Alternate Path
- Boundary: Defines system limits.
- Constraint: Limits possibilities to guide outcomes.
- Feedback: Outputs influence inputs.
- Flow Control
- Observability: Infer internal state externally.
- Path Health Signal
- Path Selection
- Routing Rule
Also references 10 related abstractions
- Coupling: Interdependence among subsystems.
- Flow: Structured movement of energy, matter, or information.
- Indirection: Introduces intermediary references.
- Network: Models interactions between components.
- Path Dependence: Outcomes are shaped by the specific historical sequence of past choices, which lock in consequences and foreclose alternatives that persist despite present incentives to change.
- Resilience: Absorb shocks and adapt.
- Resource Management: Allocation of finite assets.
- Robustness: Maintain functionality under stress.
- Teleconnection: Distant relationships via shared dynamics.
- Topology: Studies properties preserved under deformation.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Bypass Routing · implementation variant · recognized
Route flow around a constrained, damaged, or inappropriate path through an alternate pathway.
Carrier-Branch Premixing Before Main Recombination · implementation variant · recognized
Divert a bounded carrier branch, mix or condition the difficult minority input within that branch, and promptly recombine the conditioned branch with the main flow so final integration starts from a reduced mismatch.
Side-Stream Expansion Subcooling and Recombination · thermodynamic side stream rerouting variant · recognized
Divert and expand a side stream to subcool the main high-pressure stream, then recompress the side vapor into the primary path to preserve capacity at high ambient temperature.
Editorial Notes¶
Problem Classification¶
Classification: Congestion, Backlog & Flow Breakdown → Routing, Distribution & Endpoint Failure
Problem kernel: routing cannot shift flow around a blocked or overloaded segment
Rationale: Both reviewers identify the same routing failure: flow stops, overloads, or remains harmful because the system cannot redirect it around an impaired segment to an available viable path. Fault containment concerns preserving a protected function after component failure; this record specifically centers route selection and use of alternate network capacity while flow continues.
Boundary considered: Fragility, Failure & Continuity Risk → Fault Containment & Bounded Service Loss
Why this classification prevailed: Routing failure governs alternate path selection for ongoing flow; fault containment governs bounded service loss and alternate functional activation after a local failure.
Review outcome: Reconciled after independent review; high confidence.