Dependency Concentration
Critical functions migrate into a shrinking number of operators, components, or jurisdictions until alternatives become difficult to sustain.
How Critical Dependencies studies governance, resilience, and dependency in critical systems.
Critical Dependencies studies systems rather than the organizations that operate within them. Companies, regulators, and suppliers appear in our research where relevant, but they are not the primary subject of analysis.
The primary subject is the system itself: how it functions, evolves, maintains resilience, and accumulates dependency over time.
Organizations change. Technologies change. Systems persist. The system provides a more durable foundation for analysis than any single participant within it.
Every system studied by Critical Dependencies is examined through three complementary lenses.
How authority is exercised within a system: oversight, accountability, regulation, and the processes through which decisions are made and enforced. The question is not whether governance exists, but how it behaves as systems become larger and harder to change.
A system's capacity to continue functioning under stress: redundancy, repair capacity, adaptability, and institutional learning. Resilience is not measured by the absence of incidents, but by how systems respond when incidents occur.
The extent to which societies rely upon a system and the difficulty of replacing it. Dependency grows through use, investment, and institutional adaptation. As it accumulates, the range of realistic alternatives narrows.
Critical Dependencies organizes its research around six recurring patterns observed across critical systems. They provide a common language for comparing very different systems without reducing them to identical problems.
Short summaries appear below. Each pattern has a dedicated page with the full analysis.
Critical functions migrate into a shrinking number of operators, components, or jurisdictions until alternatives become difficult to sustain.
Backup systems gradually come to share the same dependencies and assumptions as the primary systems they are meant to protect.
Systems evolve continuously while the institutions that govern them evolve in episodes, leaving a persistent gap between operation and oversight.
Reliable systems become invisible. Renewal is postponed in favour of more visible priorities until structural debt accumulates.
Interfaces, exceptions, and dependencies accumulate beyond what any single operator or institution can fully comprehend.
Institutions retain, lose, or distort the lessons of past failures, shaping the resilience of future generations of the system.
Critical Dependencies has a deliberately limited scope.
The purpose of this publication is understanding rather than advocacy.
Four principles govern how analysis is selected, framed, and written. They are intended to outlast any individual study.
The unit of analysis is the system itself rather than any individual participant within it.
Events matter because they reveal patterns. Patterns matter because they persist after events are forgotten.
Critical systems evolve slowly. Understanding them requires patience, historical context, and attention to structural change.
The publication exists to improve understanding, not to promote particular institutions, policies, technologies, or outcomes.
Critical Dependencies does not predict outcomes, advocate positions, rate institutions, or recommend policy. It exists to improve understanding of how critical systems evolve, how resilience is maintained, and how dependency shapes the choices available to institutions over time.
The purpose of this work is not certainty.
It is clarity.