1. Identity & Scope
Pattern Name:
Chokepoint Dependency
Pattern Type:
Proto-Pattern
Maturity Status:
Proto-Pattern
Problem / Opportunity Addressed:
Chokepoint Dependency describes a structural condition in which critical system function depends disproportionately on one or a very small number of nodes, routes, suppliers, institutions, or decision points.
Applicable Contexts:
- supply chains
- energy grids
- transportation systems
- communications infrastructure
- governance bottlenecks
- payment systems
- regulatory approval systems
- critical leadership roles
Non-Goals / Explicit Exclusions:
- Chokepoint Dependency does not require failure to exist.
- It does not mean concentration is always bad.
- It does not describe the external shock itself.
- It describes dependence on constrained throughput or control points that can amplify disruption when stressed.
2. Observed Structural Signal
Chokepoint Dependency appears when:
- a small number of components or pathways carry disproportionate system load
- substitutions are difficult or slow
- failure or disruption at one point propagates widely
- throughput depends on high-centrality nodes with limited fallback options
The structural issue is not simply centralization, but fragile dependence on concentrated critical pathways.
Common signals include:
- single-source procurement
- limited transport corridors
- single points of institutional approval
- critical infrastructure nodes without failover
- concentrated decision authority that cannot be bypassed
3. Open Questions
- When does Chokepoint Dependency function as a standalone anti-pattern versus a consequence of Thin Buffers or Efficiency Fragility?
- Should chokepoints be categorized by type:
- physical
- institutional
- informational
- financial
- How should this proto-pattern relate to existing concepts like Redundancy and Failover?
- Is the true anti-pattern the existence of a chokepoint, or dependence on it without compensating resilience?
Optional Notes
Why this likely deserves pattern status:
Chokepoint Dependency appears repeatedly in cross-domain fragility analysis and seems to explain why otherwise stable systems experience disproportionate disruption from localized failure.
Relationship to existing anti-patterns and patterns:
Likely related to:
- Buffer Depletion
- Institutional Load Failure
- Redundancy and Failover
- Load Sink Saturation