Dependency¶

Version: v4 · 2026-09-28 · History · 1 correction
Prime #: 1289
Domain group: Applied Sciences & Engineering
Origin domain: Computer Science & Software Engineering
Also from: Organizational & Management Science, Philosophy, Biology & Ecology
Aliases: Reliance, Directed Reliance

Core Idea¶

Dependency is the directed relation in which the state, action, availability, meaning, or success of one element relies on another being present, prior, compatible, or supplied. It names the asymmetry where A cannot proceed, function, be interpreted, or retain its value unless B is met. Dependencies can be material, informational, temporal, logical, social, or institutional — but the core commitment is directed reliance: A depends on B, where removing or violating B impairs A in a specifiable failure mode. Dependencies compose into chains, graphs, cycles, bottlenecks, and layered architectures wherever multiple elements interact.

How would you explain it like I'm…

Needs Something Else

If you want to draw, you need a crayon. The drawing depends on the crayon — without it, you can't draw. That's a dependency: one thing needs another thing first. If you stack blocks, each block depends on the one underneath to hold it up.

Relies On

A dependency is when one thing needs another thing to work or exist. The relationship has a direction: A depends on B, but B might not depend on A. If B isn't there, or is broken, then A can't function. You see this everywhere: a recipe step needs the previous step done first, a sentence needs a noun before a pronoun can refer to it, and an animal needs a particular plant to live. When you chain dependencies — A needs B, B needs C — then A secretly needs C too.

Directed Reliance

Dependency is the directed relation in which one element relies on another being present, prior, compatible, or supplied. A depends on B means A cannot proceed, function, or hold its value unless some condition on B is met — and the relation has a direction (asymmetric reliance), not just correlation. The same shape shows up across domains: production needs upstream parts, calculations need input values, theorems need lemmas, sentences need referents, contracts need triggering conditions. What unifies them isn't the content but the shape: a directed reliance with a specifiable failure mode if the relied-on condition fails. Dependencies compose: a chain (A depends on B depends on C) makes A also depend on C, even when no direct link was named.

Dependency is the directed relation in which one element relies on another being present, prior, compatible, or supplied. A depends on B means A cannot proceed, function, be interpreted, or retain its value unless some condition on B holds. The relation is asymmetric — reliance flows one way — and is accompanied by a specifiable failure mode when the condition on B fails. The same structural shape recurs across domains: material (downstream production needs upstream parts), informational (a calculation needs an input), temporal (a later event needs an earlier one), logical (a theorem needs a lemma), semantic (a referring expression needs a referent), and institutional (a contractual obligation needs a triggering condition). What unifies them isn't content but shape. Dependencies compose: a chain A depends on B depends on C makes A transitively depend on C, even with no direct link named. A graph of dependencies produces architecture — layered, modular, hierarchical, or cyclic — with topological sort as the canonical linearization.

Broad Use¶

Software engineering: import/library dependency graphs, build systems, transitive dependency resolution; "a depends on b" is foundational.
Project management / operations: task interdependence, critical-path analysis, bottlenecks, the theory of constraints.
Supply chains: upstream component availability gates downstream production.
Logic / language: logical entailment ("A requires B to be true"), semantic presupposition ("the king of France is bald" presupposes a French king).
Biology: obligate mutualism (one species cannot survive without another), biochemical pathway precursors, host-parasite interactions.
Institutions / contracts: legal consideration, regulatory preconditions, treaty ratification chains.

Clarity¶

Dependency names the asymmetric reliance relation itself, distinct from the things it gets confused with. It is not the graph of relations (that is Network); it is not the productive mechanism that links cause to effect (that is Causality); it is not a limit on what is permissible (that is Constraint); it is not the historical accumulation that shapes which relations exist now (that is Path Dependence). What Dependency adds: a directed arrow A→B with a failure-mode commitment — there is a specifiable way A breaks, stalls, or becomes ambiguous when B is unmet. That commitment is what separates a real dependency from a mere correlation, association, or co-occurrence.

Manages Complexity¶

Dependency gives a system a structure to walk: from any element A, you can ask what does A depend on? and traverse to its prerequisites, then their prerequisites, and so on. This converts an opaque tangle of elements into a navigable graph with five named roles: a dependent element, a relied-on element, a dependency condition (what the relied-on must satisfy), a direction (asymmetric), and a failure mode (what breaks when the condition fails). Once those roles are present, downstream phenomena fall out by topology: chains become transitive reliance; cycles become circular dependencies; many-to-one becomes Bottleneck; layered DAGs become architecture. Naming the relation lets the analyst see the topology instead of the elements.

Abstract Reasoning¶

Dependency supports the counterfactual "if B were removed or violated, A would fail in this specific way." That is the move that lets engineers compute critical paths, lawyers identify contract preconditions, biologists predict cascading extinctions, and logicians track entailment. Across substrates, the same abstract operations apply: take the transitive closure (everything A indirectly depends on), find roots (elements with no upward dependencies), find bottlenecks (single nodes many things depend on), and detect cycles (mutual reliance, which is often a modeling error worth fixing). These operations are substrate-independent because the relation itself is.

Knowledge Transfer¶

The vocabulary travels intact across domains. A software engineer reading about supply-chain disruption recognizes a build-graph problem; a biologist reading about technology lock-in recognizes obligate mutualism; a lawyer reading about logical entailment recognizes contractual consideration. The transfer is structural, not metaphorical — these are all instances of directed reliance with a failure mode. The biological case (obligate symbiosis, biochemical precursor chains) is especially clean: it shows the pattern with no human institutions in the picture at all, ruling out the suspicion that "dependency" is a software-engineering specialty.

Example¶

Consider a research paper whose argument depends on Lemma 2. Lemma 2 is the relied-on element; the paper's main result is the dependent element; the dependency condition is that Lemma 2 be true; the direction is asymmetric (the main result needs the lemma, not vice versa); and the failure mode is specifiable — if Lemma 2 has a counterexample, the main result collapses in a documented way. This is a dependency without any causal mechanism: nothing physically causes anything; the reliance is logical. The same five-role pattern applies to a software build (the binary depends on a library), a contract (the obligation depends on a signature), and a food web (the predator depends on the prey). Dependency is the umbrella; causality is the physical-mechanism subtype.

Relationships to Other Abstractions¶

Current abstraction Dependency Prime

Foundational — no parent edges in the catalog.

Children (42) — abstractions linked here by typed relations

Agreement (linguistics) Domain-specific is a kind of Dependency

It remains its own entry because its identity is fixed by the language and construction, controller and target, syntactic relation and domain, agreement feature and possible values, overt exponents, direction and locality, default or resolution rules, semantic or notional exceptions and corpus or elicited evidence.
Antecedent-Contained Deletion Domain-specific is a kind of Dependency

Dependency is the strict parent by composition.
Cometabolism Domain-specific is a kind of Dependency

It remains its own entry because its identity is fixed by the organism or community, primary growth substrate, induced enzyme and cofactor, secondary compound, transformation product and rate, absence of growth benefit, toxicity and mass-balance and alternative catabolism evidence.
Data dependency Domain-specific is a kind of Dependency

It remains its own entry because its identity is fixed by operations, memory objects or aliases, read and write events, execution order, path feasibility, dependence type, loop distance, and transformation claim.
Domestic Liability Dollarization Domain-specific is a kind of Dependency

The dependent elements are domestic deposits, bank borrowing, and loans whose repayment values are fixed outside the home unit; the relied-on element is the selected foreign hard currency and its externally governed unit of account.

▸ Show 37 more

Memory distrust syndrome Domain-specific is a kind of Dependency
The person's reported account becomes asymmetrically reliant on an external source being supplied and credited: low confidence in accessible autobiographical recollection supplies the dependency condition, the external account is the relied-on element, and revision or disavowal of the original recollection is the failure mode when that source conflicts or misleads.
Non-local variable Domain-specific is a kind of Dependency
A non-local reference literally depends on a binding supplied outside the current local environment and fails if that binding cannot be resolved or retained; What makes it its own entry: the reference-to-outer-binding relation viewed from a particular unit, not the variable's intrinsic type, a global variable by definition, or the complete closure value that may capture it.
Operator (linguistics) Domain-specific is a kind of Dependency
What makes it its own entry: The term is theory-relative and does not cover every mathematical or programming operator; empty operators require independent syntactic diagnostics.
Participation (philosophy) Domain-specific is a kind of Dependency
What makes it its own entry: A metaphysical relation in which a particular or dependent being has a form, property or reality through an asymmetric dependence on what it participates in.
Sequential Coupling Domain-specific is a kind of Dependency
**Dependency** is the strict parent because the later operation relies on the prior operation's state contribution and has a concrete failure mode when it is absent.
Causality Prime is a kind of Dependency
Causality is a specialization of dependency in which one event productively brings about another with counterfactual modal robustness.
Cross-Boundary Subsidy Prime is a kind of, typical Dependency
Cross-boundary subsidy is a directional resource flow creating donor-coupling reliance, matching dependency's asymmetric-reliance definition.
Entanglement Prime is a kind of Dependency
Entanglement is a kind of dependency: subsystems acquire a directed reliance such that one's state cannot be specified without the other's.
Infinite Regress Prime is a kind of Dependency
An infinite regress is a kind of dependency chain in which each element depends on a further element of the same kind without termination.
Inheritance Prime is a kind of, typical Dependency
Inheritance is the specific dependency of a derivative on a parent ALONG A LINEAGE, with default carry-over and substitutability — a specialization of bare dependency ('not dependency in general').
Task Interdependence Prime is a kind of Dependency
Task interdependence is a specialization of dependency in which the directed reliance is between coupled tasks in a work system.
Teleconnection Prime is a kind of Dependency
A teleconnection is a kind of dependency in which distant regions are not independent because a shared mechanism couples them.
Begging the Question Domain-specific includes Dependency
Directed premise-to-conclusion and conclusion-back-to-premise reliance edges are internal constituents of the fallacy's justification graph.
Betrayal Domain-specific presupposes Dependency
Betrayal presupposes a directed reliance relation whose relationship-defining expectation is violated.
Dependency Grammar Domain-specific presupposes Dependency
Dependency grammar **presupposes Dependency** as its closest portable structural relative: syntactic analyses orient an asymmetric relation from a head to a dependent and compose those relations.
Dependency Hell Domain-specific presupposes Dependency
Dependency hell presupposes a directed reliance graph whose transitive closure gathers the conflicting requirements.
DLL Hell Domain-specific presupposes Dependency
DLL Hell requires multiple clients to depend on a shared mutable library slot whose winning version can violate one client's assumed interface.
Ecosystem Mismatch Domain-specific includes Dependency
A directed reliance of the innovation's deployed function on the absent contextual asset is an internal constituent of Ecosystem Mismatch.
Immaterial Spatial Entity Domain-specific presupposes Dependency
An immaterial spatial entity presupposes material bearers whose arrangement or absence supplies the conditions on which its existence depends.
Radical monopoly Domain-specific includes Dependency
Radical monopoly contains a directed reliance on the industrial product type for ordinary satisfaction of the need.
Reverse echo Domain-specific includes Dependency
The wet response and its pre-onset alignment require directed input and reference dependencies inside the reverse-echo procedure.
Shared-image stateless nodes Domain-specific includes Dependency
A node's directed reliance on the centrally supplied system base is an identity-bearing part of this architecture.
Variable Cost Domain-specific presupposes Dependency
Variable Cost presupposes Dependency because membership in the category is defined by how cost changes with a declared activity or output driver.
Bottleneck Prime presupposes Dependency
A bottleneck presupposes dependency because the slowest-element-governs-the-whole pattern only obtains in a chain of dependent operations.
Caldera Collapse Prime presupposes Dependency
Caldera collapse presupposes a load-bearing structure that depends on a support medium whose withdrawal supplies the failure mode.
Coordination Prime presupposes Dependency
Coordination presupposes dependency because alignment of independently controlled actors is only required when their actions are mutually contingent.
Dependency Distribution Concentration Prime 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).
Inherited-Substrate Risk Prime presupposes Dependency
Inherited-substrate risk operates on a borrowed substrate the system relies on without re-deriving it; it presupposes a dependency relation and adds the audit-boundary asymmetry and latent origin condition.
Legacy Integration Prime presupposes Dependency
Legacy integration presupposes dependency because preserving institutional knowledge across rupture requires explicit linkage between new and prior systems.
Operational Reach Prime presupposes, typical Dependency
Effective reach is set by a tip's DEPENDENCY on a support tail whose capacity decays with distance/duration (the tip can act only as far as the tail reaches).
Path Dependence Prime presupposes Dependency
Path dependence presupposes dependency because outcomes constrained by historical trajectory require the present to rely on prior decisions and states.
Sequencing Prime presupposes Dependency
Sequencing presupposes dependency because the order in which steps are arranged is dictated by which steps require which others as prerequisites.
Single Point of Failure Prime presupposes Dependency
An Single Point of Failure is a serial articulation node on the operational DEPENDENCY graph whose removal disconnects it; it presupposes a dependency topology and names the node every critical path runs through with no parallel route.
Systemic Risk Prime presupposes Dependency
Systemic risk presupposes dependency because component-failure cascades require a directed relation in which one element relies on another.
Quality inherence Domain-specific is a decomposition of Dependency
Quality inherence is the upper-ontology form of existential dependency in which a property-token cannot exist without its bearer.
Supporting Effort Domain-specific is a decomposition of Dependency
Supporting effort is defined over a directed enabling relation: the main effort relies on a condition or capability the supporting activity supplies, with a specifiable failure if that support is absent or cut below its functional floor.
Preparatory Field Conditioning Prime is a decomposition of Dependency
The focal action relies on the intermediate condition supplied upstream, with a specifiable failure or cost increase when it is absent.

Not to Be Confused With¶

Not Causality: dependencies can be logical, contractual, or semantic without any productive causal mechanism. "This proof depends on Lemma 2" describes a logical reliance, not a causal process; "the contract depends on signature" is institutional, not physical causation. Causality is one specific kind of dependency (the physically-productive kind); dependency is broader. (Project-06 R21 unanimously committed causality → dependency as subsumption.)
Not Network: a network is the graph of relations among elements. Dependency is the directed relation that can populate such a graph. Many networks involve dependencies, but not all relations in a network are dependencies (some are correlations, similarities, or symmetric ties).
Not Constraint: a constraint restricts what is permissible; a dependency requires something be supplied. A dependency can create a constraint (B must hold, restricting the option space) but the two concepts foreground different things: constraints are limits on the search space; dependencies are incoming relations to specific elements.
Not presupposition: presupposition is a specific kind of dependency in language/logic (one proposition assumed by another); dependency is the broader structural pattern.
Not Path Dependence: path dependence is the historical-accumulation mechanism that explains how current dependencies came to exist; dependency is the current relation itself. Path dependence usually presupposes some dependency structure; dependency need not be path-dependent (a fresh logical entailment depends on its premises without any history of accumulation).

Notes¶

The case is strong: Task Interdependence, Bottleneck, Interface, Coordination, Path Dependence, and many software-architecture nodes use "dependency" as their structural vocabulary but no umbrella prime existed in the catalog.

The decisive case is the logical/semantic/institutional dependencies where there is no productive causal mechanism: those are dependencies but not causation, so the prime is doing distinct structural work.