Path Redundancy Provisioning¶
Create multiple viable paths so flow or connection can continue when one path is blocked, degraded, or unavailable.
The Diagnostic Story¶
Symptom: A critical flow depends on a single path, and when that path is disrupted — by outage, absence, closure, provider failure, or intentional interference — the flow stops entirely. Incident teams discover that backup arrangements exist in documentation but are stale, untested, or dependent on the same underlying chokepoint. Continuity plans assume someone will improvise a route under pressure, but no viable alternate path has been qualified, rehearsed, or maintained. System owners have confused duplicated endpoints with true path redundancy, leaving the same route dependency untouched.
Pivot: The structural move is to add, qualify, and actively maintain one or more alternate paths capable of carrying the critical flow when the primary path fails, degrades, or is taken offline. Redundancy requires that the alternate paths have been tested, are operable under realistic failure conditions, and do not share the hidden dependencies that make the primary path fragile.
Resolution: Critical flows survive single-path failures without requiring improvisation under pressure. Incident response is faster because alternate routes are known and ready. Dependency visibility improves — the act of mapping redundancy forces examination of shared failure domains — and degradation becomes graceful rather than total.
Reach for this when you hear…¶
[network operations] “Our backup fiber route runs through the same conduit as the primary — we don't have two paths, we have one path with two labels.”
[humanitarian logistics] “The border crossing we've been using for six months just closed and we have no qualified alternate route into the northern region — this should have been mapped before we became dependent on one crossing.”
[executive succession] “Our CISO is the only person with admin credentials to the security platform and she's going on parental leave in three weeks — we need a second authorized operator before she leaves.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
A critical flow, relationship, communication, authority chain, supply route, or connection depends on one path whose failure would sever reachability or continuity.
What this problem means
The structural problem is a **single-path dependency**. A system needs continuity, but the route that carries the critical flow has no credible substitute. A local failure becomes system-level disconnection because the topology has no alternate way through.
This problem often hides behind ordinary success. A single route can look efficient when nothing is wrong. It is cheaper, easier to explain, and easier to govern. The weakness becomes visible only under stress: a provider outage, a road closure, a person’s absence, a platform failure, a legal blockage, a compromised channel, or an overloaded approval queue.
A second problem is false redundancy. Systems often believe they have backups because they have multiple names, channels, vendors, or tools. But if every path depends on the same login system, bridge, cloud region, contract broker, manager, or social gatekeeper, the topology is still fragile.
Show the applicability expression
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Single critical path · grounded
A critical destination is reachable through only one path.
The source archetype describes the situation as follows: The system has a single path to a critical destination. The normalized requirement above isolates the load-bearing portion used in this condition set.
Credible primary-path failure · open
The primary path has credible failure, overload, blockage, or capture scenarios.
Path redundancy should be evaluated against the failure scenarios it is meant to survive. The narrower requirement in this condition set is: The primary path has credible failure, overload, blockage, or capture scenarios.
Unsafe improvised rerouting · open
Improvising a replacement route during failure would be too slow or risky.
The source archetype describes the situation as follows: Improvising a new route during failure would be too slow or risky. The normalized requirement above isolates the load-bearing portion used in this condition set.
Correlated alternate paths · open
Nominal alternate paths may share hidden dependencies.
The source archetype describes the situation as follows: The apparent redundancy may share hidden dependencies. The normalized requirement above isolates the load-bearing portion used in this condition set.
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 gateThe continuity requirement is stronger than the cost-minimization requirement.
Solution feasibilityAlternate paths can be made usable without destroying governance or safety.
Some alternate paths create more risk than they remove. In this archetype, the relevant feasibility condition is: Alternate paths can be made usable without destroying governance or safety. It identifies something that must be possible or available for the intervention to be workable.
Coverage
1 of 4 conditions grounded · 3 open.
Mechanisms / Implementations¶
- Alternate Supplier Route: Qualifies a second route, logistics provider, or supply path so critical inputs can still reach the system if the main route is blocked.
- Backup Route Plan: Predefines alternate physical, procedural, or organizational routes for movement, access, approval, or evacuation.
- Dual-Homing: Connects a node to two upstream paths or providers so the node is not isolated by a single upstream failure.
- Multi-Channel Communication: Maintains more than one viable channel for reaching people or systems, especially when one channel may be unavailable during disruption.
- Out-of-Band Channel: Provides a separate channel for control, diagnosis, or emergency coordination that does not depend on the ordinary communication path.
- Parallel Service Path: Creates more than one way for users, patients, clients, or incidents to reach the same service outcome.
- Path Readiness Drill: Exercises alternate paths under realistic conditions to reveal stale configurations, missing permissions, insufficient capacity, or confused ownership.
- Redundant Escalation Path: Ensures that support, authority, review, or safety reporting can proceed if the normal chain is unavailable, conflicted, overloaded, or unsafe.
- Redundant Network Link: A standing parallel link that carries no unique load until a primary path is cut, congested, or misconfigured — then it keeps the two sides connected without interruption.
- Standby Transport Corridor: Keeps a pre-qualified alternate route between the reserve and the fronts continuously ready and health-checked, so a redeployment can still complete inside its window when the primary path fails.
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)
- Network: Models interactions between components.
- Redundancy: Duplicate critical components.
- Topology: Studies properties preserved under deformation.
Also references 5 related abstractions
- Boundary: Defines system limits.
- Constraint: Limits possibilities to guide outcomes.
- Fault Tolerance: Continue operating under failure.
- Indirection: Introduces intermediary references.
- 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.
Disjoint Path Redundancy · subtype · recognized
Provides alternate paths that avoid shared links, nodes, providers, geography, authority chains, or failure domains.
Dual-Homing · implementation variant · recognized
Connects a node to two upstream paths, providers, networks, authorities, or channels so loss of one upstream connection does not isolate it.
Out-of-Band Path · communication variant · recognized
Maintains a secondary communication or control path that does not rely on the same channel as ordinary operation.
Parallel Supply Pathing · domain variant · recognized
Maintains more than one viable path by which a needed material, service, input, or capability can reach the point of use.
Load Preserving Alternate Path Reconfiguration · temporal variant · recognized
Reconfigure an active path without interruption by transferring load to a temporary alternate path, changing the unloaded primary path, and handing load back along a controlled trajectory.
Time-Offset Redundancy · temporal variant · recognized
Redundancy becomes robust to time-correlated failures when copies are separated in time and realigned only at consumption.
Duty-Rotated Redundant Path Switching · lifecycle balancing variant · recognized
Rotate duty among redundant paths to distribute deterioration, then switch around a failed path without interrupting the protected output.
Editorial Notes¶
Problem Classification¶
Classification: Fragility, Failure & Continuity Risk → Fault Containment & Bounded Service Loss
Problem kernel: single-path failure severs critical reachability without an alternate
Rationale: A critical flow or connection depends on one path, so a local path failure severs reachability and whole-function continuity unless an alternate can activate. Common-mode loss requires multiple nominal paths that share a cause and fail together; this record begins one step earlier with no alternate path at all.
Boundary considered: Fragility, Failure & Continuity Risk → Dependency Concentration & Common-Mode Loss
Why this classification prevailed: Fault containment governs absence of an alternate after one path fails; common-mode loss governs several nominal alternatives sharing enough concentration or correlation to fail together.
Review outcome: Adjudicated after independent review; high confidence.