Dependency Distribution Concentration

Prime #

790

Origin domain

Systems Thinking & Cybernetics

Subdomain

dependency structure and fragility → Systems Thinking & Cybernetics

Core Idea

When a system relies on an upstream network of providers, the shape of how its dependency weight is spread across them — concentrated on a few or spread broadly — bounds its fragility. Two systems with identical total dependency can be robust or brittle purely as a function of this distribution, not the binary fact of dependency.

How would you explain it like I'm…

One Cow or Ten Cows

Imagine all your milk comes from one cow. If that cow gets sick, you have no milk at all! But if your milk comes from ten different cows, one sick cow is no big deal. It's not just about needing milk — it's about how many cows you spread your needing across.

How Your Needing Is Spread

When something you rely on comes from outside suppliers, what matters isn't just *that* you depend on them — it's *how spread out* that dependence is. If one supplier provides almost everything you need, then one problem at that supplier becomes your whole problem. If many suppliers each provide a little, the same hiccup at any one of them barely touches you. Two systems can need the exact same total amount and yet one is fragile and one is sturdy, purely because of how the needing is shared out.

The Shape of Dependence

Dependency Distribution Concentration is the idea that when a system depends on a network of suppliers, the real structural fact isn't THAT it depends on them, it's how the dependency weight is distributed across them. If most of a critical input rides on one or two top providers, then your fragility is set by what happens at those few nodes, not by your own backup plans. The same total reliance can be robust or brittle purely as a function of this shape. Concentrated dependency turns a single upstream event into a system-wide event; spread-out dependency lets the same event land as harmless local noise. So 'how safe is our supply?' becomes a question about distribution shape, not just about whether any one provider is trustworthy.

 

This prime isolates a structural property of any dependent system that draws on an upstream network of providers: the distribution shape of its dependency weight across those providers. The load-bearing distinction is that the commitment is not the binary relation of depending — it's the skew of the weight distribution, concentrated on a few nodes versus spread broadly. Two systems with identical total dependency volume can be robust or brittle entirely as a function of this shape. Under concentration, a single upstream event at a top-weighted node propagates downstream as a system-wide event; under broad distribution, the identical event is absorbed as local noise. The fragility coupling therefore runs from the concentration of the weight distribution and the joint failure probability of the top-weighted nodes, not from whether any individual provider is reliable. Diversity at the upstream layer buys robustness at the cost of more relationships, higher unit cost, and coordination overhead, while concentration buys efficiency at the cost of systemic tail exposure — so the prime turns an implicit procurement, ecological, or platform-choice decision into an explicit, measurable trade between efficiency and tail risk.

Broad Use

• Supply chains: supplier concentration risk and single-sourcing trade-offs, with documented single-facility chokepoints.
• Information technology: single-vendor lock-in, single-CDN dependency, cloud-region concentration, OS monoculture.
• Ecology: keystone-species dependence and single-pollinator reliance concentrate ecosystem function on a few nodes.
• Agriculture: monoculture — the Cavendish banana, the 1840s potato — concentrates a crop's survival on one genome.
• Physiology: single-pathway metabolic dependence and single-receptor signaling concentrate function.
• Finance: single-counterparty concentration, single-CCP clearing, and too-big-to-fail banks as concentrated upstream nodes.
• Energy: single-fuel reliance and single-pipeline imports concentrate supply.

Clarity

Separates three fused questions — is there a dependency?, is the provider reliable?, and how is weight distributed? — and distinguishes concentration (the failure mode) from redundancy (the remediation), surfacing the efficiency-versus-tail-exposure trade.

Manages Complexity

Reduces a wide failure family to one diagnostic — what fraction depends on the top-k nodes, and what is their joint failure probability? — captured by a portable scalar (Herfindahl, top-k share, Gini).

Abstract Reasoning

Concentration is a system property, not a provider property; tail risk dominates expected loss; the "two of everything" heuristic is wrong by default (duplication that shares a common mode does not deconcentrate); and concentration drifts upward endogenously unless actively maintained.

Knowledge Transfer

• Finance: a firm clearing through twelve brokerages all routed to one CCP has apparent diversity, real single-node concentration.
• Ecology: an agricultural region with twelve crops all pollinated by one bee population is the same hidden common mode.
• Site reliability: twelve regional deployments all on one DNS provider recapitulate the procurement officer's playbook.

Example

A firm sourcing from twelve suppliers (Herfindahl ~0.08 by count) that all buy from one upstream plant has a true concentration of 1 at the hidden node — so the diagnostic is to compute the concentration scalar at the deepest shared layer, not the visible provider tally.

Relationships to Other Primes

Parents (1) — more general patterns this builds on

• Dependency Distribution Concentration presupposes Dependency — How a system's dependency WEIGHT is distributed across providers; it presupposes a dependency structure and characterizes the shape of that reliance (a graph-weight property).

Path to root: Dependency Distribution Concentration → Dependency

Not to Be Confused With

• Dependency Distribution Concentration is not a Single Point of Failure because this prime is the continuous distribution-shape measure (of which an SPOF is the extreme case at concentration = 1), capturing the graded middle that the binary predicate misses.
• Dependency Distribution Concentration is not Risk Pooling because risk pooling is a strategy assuming independent failures, whereas this prime is the structural property — plus the common-mode check — that determines whether the pooling actually worked.
• Dependency Distribution Concentration is not a Margin of Safety because this prime is about where the dependency weight sits, whereas a margin is how much buffer is held — generous headroom does not help if weight is concentrated on one node.