Flow¶
Core Idea¶
Flow is the continuous, directional transfer of some conserved or quasi-conserved quantity — matter, energy, information, money, people — through a system, from a source to a sink along channels shaped by gradients, constraints, and network topology. The essential commitment is that flow is characterized by rate, direction, and conservation: what enters one region leaves another, minus any storage or loss, and the flow field obeys laws that tie local rates to global structure. Every flow specifies (1) the quantity being transported, (2) the field or network through which it moves, (3) the driving gradient or pressure that pushes it, and (4) the conservation and continuity relations that govern how rates at different points in the system connect.
The mathematical foundations of fluid flow rest on the balance between pressure and inertia, formalized by [1] Bernoulli's principle relating flow velocity to pressure drop in 1738 [1], and extended to the general equation of motion for inviscid flow via [2] Euler's equations (1755), which express momentum conservation for fluid parcels in the absence of viscous forces [2]. When viscous effects become significant, the framework expands to include [3] Navier's 1822 treatment of viscous fluid motion, establishing the precursor to the full Navier-Stokes equations [3], which [4] Stokes completed in 1845 with a rigorous formulation of internal friction in fluids in motion [4]. The transition from orderly laminar flow to chaotic turbulent regimes is quantified by [5] Reynolds's 1883 dimensionless number, which predicts the onset of instability and turbulence via the ratio of inertial to viscous forces [5] (see cross-link with dimensional_analysis). In flows dominated by rotation, [6] Helmholtz's 1858 vorticity dynamics equations govern the evolution of rotational structures, linking wave propagation to swirling fluid motion [6]. The confined region near solid boundaries—where velocity drops to zero—is captured by the boundary-layer theory developed by [7] Prandtl in 1904, explaining drag and separation in practical flows [7]. The periodic wake left behind a bluff body exemplifies flow instability: [8] von Kármán's 1911 vortex-street analysis explains how alternating vortex shedding emerges from steady upstream flow [8].
Classical comprehensive treatments unite these perspectives: [9] Lamb's 1932 Hydrodynamics remains the authoritative foundation for classical fluid theory, and [10] Batchelor's 1967 Introduction to Fluid Dynamics provides modern pedagogical depth in this same tradition [10]. Porous-media flows obey [11] Darcy's law (1856), relating flow rate to pressure gradient through a permeable material, underpinning groundwater and geological transport [11]. In the turbulent regime—high Reynolds number with complex multi-scale structure—[12] Frisch's 1995 Turbulence: The Legacy of A. N. Kolmogorov traces how energy cascades across scales and dissipates at smallest eddies [12] (cross-link: turbulence G3 sibling). Detailed practical insights on flow measurement and control are synthesized by [13] Tritton's 1988 Physical Fluid Dynamics, emphasizing experimental and physical reasoning [13]. Transport phenomena across multiple domains—momentum, heat, and mass transfer—are unified by [14] Bird, Stewart, and Lightfoot's 1960 Transport Phenomena, connecting flow to broader continuum-physics frameworks (cross-link: diffusion and convection DP-11 G4) [14]. Finally, compressible flow—where density changes are significant—obeys modified continuity and energy equations; the interplay of pressure, temperature, and velocity in high-speed regimes is systematized in advanced treatments building on Euler's foundation.
How would you explain it like I'm…
Stuff Moving Through
Continuous Movement of Stuff
Directional Transfer Along a Network
Structural Signature¶
A process is a flow in the structural sense when each of the following holds:
- Transported quantity. A definite substance, magnitude, or signal is being moved — mass, heat, charge, fluid, traffic, data, money.
- Direction. At each point and time, the flow has a direction — a vector or discrete routing choice — not merely a presence.
- Rate. A rate (per unit time, per unit area, per unit of the carrying substrate) is specifiable and measurable.
- Driving gradient or pressure. A difference in some potential (pressure, temperature, concentration, voltage, price) drives the flow, or a continuous source-sink arrangement does.
- Channel or medium. The flow occurs through a substrate that shapes it — pipes, vessels, conductors, supply chains, network links, open space with boundary conditions.
- Conservation and continuity. What flows in equals what flows out, up to storage and dissipation terms; continuity equations link local and global rates.
What It Is Not¶
- Not displacement of a static object. Moving a rigid body is not flow; flow requires a continuous field or stream of the quantity through the medium.
- Not Csikszentmihalyi's flow state. The
psychological "flow" — a state of absorbed,
skilled engagement — is a distinct concept and
is documented separately as
flow_state. The two share only metaphor, not structure. - Not process in general. A process is any sequence of changes; flow is a specific kind of process characterized by continuous directional transfer of a conserved quantity.
- Not mere correlation or co-movement. Two quantities may move together without one flowing into the other; flow requires material or signal transfer along a channel.
- Not equilibrium. Equilibrium is the condition where net flow is zero; studying flow generally means studying non-equilibrium situations. Flows can be steady (rates constant) without being zero.
- Common misclassification. Labeling any time-varying quantity or trend as "flow" without a continuity or conservation structure — diluting the concept; confusing flow with transport-of-information-interpreted-as-a-flow (information can flow but is not always conserved in the physical sense; the analogy requires care).
Broad Use¶
- Physics and fluid mechanics
- Fluid flow (laminar, turbulent); heat conduction and convection; charge transport in circuits; diffusion.
- Biology and physiology
- Blood and lymph flow; axoplasmic transport; water and nutrient flow in plants; flux through metabolic pathways.
- Environmental science
- Atmospheric circulation; ocean currents; hydrological flow (rivers, groundwater); mass balances in ecosystems.
- Economics and operations
- Money flow and cash flow; trade flows; supply chain flow; material flow analysis.
- Information and computer systems
- Network traffic flow; data pipelines; control flow and data flow in programs; message queues.
- Graph theory and operations research
- Max-flow / min-cut; network flow optimization; transportation problems; flow-based formulations of problems.
Clarity¶
Flow clarifies by converting static descriptions into transfer-rate descriptions: a system "does X" resolves into "X units per time move from A to B along this channel, driven by this pressure, limited by this capacity." That framing surfaces the quantitative structure (source, sink, rate, channel) and the conservation relations that tie the pieces together. The clarifying force is to stop reasoning about "amount somewhere" and start reasoning about "rate along a path," which usually exposes the bottleneck or leverage point.
Manages Complexity¶
- Replaces the high-dimensional state of every particle with the low-dimensional field of rates and directions — fluid mechanics over individual molecules.
- Exposes bottlenecks: maximum flow through a network is limited by the minimum capacity cut, locating the binding constraint.
- Supports conservation-based reasoning: if flow into a region exceeds flow out, storage must change or a leak must exist — a diagnostic lever.
- Enables network-level optimization: routing, scheduling, capacity planning become formal problems with rich algorithmic support.
- Separates transient from steady state: many systems reach flow equilibrium where rates stabilize and structural reasoning becomes tractable.
Abstract Reasoning¶
Flow trains a reasoner to ask:
- What is flowing — what is the transported quantity, and is it conserved?
- Where are the sources and sinks, and what drives the flow (gradient, pressure, demand)?
- What is the channel structure, and where are the capacity limits (bottlenecks)?
- Is the flow steady or transient? If transient, what sets the timescale of approach to steady state?
- Are there storage terms (buffers, reservoirs, capacitances) that decouple instantaneous in/out rates from long-run balance?
- Where does the flow leak, branch, or recombine, and are those accounted for in the balance?
Knowledge Transfer¶
Role mappings across domains:
- Flowing quantity ↔ fluid / heat / charge / information / money / people / material
- Channel ↔ pipe / vessel / conductor / link / pathway / edge / route
- Source and sink ↔ reservoir / producer and consumer / supplier and demander / origin and destination
- Driving gradient ↔ pressure difference / potential difference / concentration gradient / price differential / demand pull
- Capacity ↔ maximum throughput / bandwidth / diameter / headcount / lane count
- Conservation ↔ continuity equation / mass or energy balance / accounting identity / flow equilibrium
- Bottleneck ↔ minimum cut / binding constraint / rate-limiting step / congestion point
- Storage / buffer ↔ reservoir / capacitor / inventory / queue / working capital
A fluid dynamicist analyzing pipe network pressures, a supply chain engineer tracing materials from supplier to customer, and a data engineer tracing events through a streaming pipeline are all doing the same structural work: identify the flowing quantity, map the network, find the bottleneck, and write the conservation equations. The same diagnostic — "what flows, through what channel, at what rate, limited by what capacity?" — applies across their disparate domains, with the same failure modes (unaccounted-for storage, hidden leaks, missed bottlenecks) in each.
Example¶
- Formal example — Poiseuille flow in a cylindrical pipe. Water flows through a circular pipe of radius R and length L, driven by a pressure difference ΔP between inlet and outlet. The governing equation is the balance between the pressure-gradient force and the viscous shear stress acting on the fluid. The velocity profile develops in the boundary-layer region (length ~0.05 Re D, where Re is the Reynolds number and D is the pipe diameter), after which a fully developed laminar flow is established. The velocity varies parabolically across the pipe radius: v® = (ΔP / 4ηL)(R² − r²), where η is the dynamic viscosity. The volumetric flow rate is Q = πR⁴ΔP / (8ηL), famously called [15] Poiseuille's law (formalized by Hagen and Poiseuille in the 1840s), relating flow rate to the fourth power of pipe radius [15]. This example shows how the structural signature is fully instantiated: the flowing quantity is mass (or volume) of water; the direction is along the pipe axis; the rate is Q (volume per time); the driving gradient is ΔP; the channel is the cylindrical pipe; and continuity holds at every cross-section. The bottleneck is determined by viscosity and geometry. The timescale for developing fully developed flow is the residence time πR²L / Q. Damping (see cross-link:
dampingG1) arises from viscous dissipation: the pressure drop is converted entirely to heat.
Mapped back: Poiseuille flow is a canonical example where the theory (Euler + Navier + Stokes momentum equations) yields an exact closed-form solution applicable to real pipe networks, medical (blood-flow arterioles), and industrial transport.
- Applied example — Atmospheric circulation and the jet stream. Air flows horizontally around the Earth due to differential solar heating (equator warm, poles cold), creating large-scale pressure gradients. The Coriolis effect deflects moving air, creating geostrophic balance where the pressure-gradient force balances the Coriolis deflection. In the mid-latitudes, the balance produces the jet stream: narrow, fast-moving currents of air (typical velocity 100 m/s) that separate tropical and polar air masses. The jet stream is highly unstable (see cross-link:
instabilityG3 sibling) to perturbations—small wave-like disturbances grow into Rossby waves, which are large-scale meanders in the jet driven by the interplay of convection (warm air rising, cold air sinking) and rotation. These waves control mid-latitude weather: high-amplitude waves trap cold air southward or warm air northward, causing blocking patterns and extreme temperature anomalies. The jet-stream system obeys the same structural logic as Poiseuille flow: the flowing quantity is air mass; the direction is primarily zonal (east-west); the rate is the mass flux (kg/s per unit area); the driving gradient is the temperature difference between equator and pole; the channel is the atmosphere's horizontal layer; and conservation is enforced by the continuity equation for air. The damping mechanism is not viscosity (air is too frictionless at large scales) but radiative cooling and the conversion of potential energy to kinetic energy and back. Unlike Poiseuille, the jet stream is inherently unsteady and chaotic at small scales while remaining quasi-steady at basin scale.
Mapped back: Atmospheric circulation illustrates how flow principles transcend simple pipe networks: the jet stream is a planetary-scale flow system where rotation, stratification, and wave propagation (wave G1 cross-link) couple to the fundamental flow dynamics, producing complex patterns that govern global weather.
Structural Tensions and Failure Modes¶
-
T1 — Continuum vs. Molecular Description:
- Structural tension: Fluid mechanics assumes a continuum approximation: the fluid is infinitely divisible, with properties (density, velocity, pressure) defined at every point. At very large Knudsen numbers (Kn = mean-free-path / characteristic-length > 0.1), the molecular structure becomes visible, and the continuum description breaks down. Rarefied gases (like air at very high altitude or in vacuum chambers) require kinetic-theory treatments where individual molecular collisions, not continuous shear stress, dominate transport.
- Common failure mode: Applying continuum Navier-Stokes to ultra-low-pressure flows (vacuum pumps, space-vehicle re-entry) where free-molecular-flow regime dominates; ignoring that the Knudsen number sets the validity boundary.
-
T2 — Inviscid vs. Viscous Flow (Idealization vs. Reality; d'Alembert Paradox):
- Structural tension: The [2] Euler equations (inviscid) are simpler and often give insight, but real fluids always have viscosity. Inviscid theory predicts zero drag on a cylinder in steady cross-flow—the d'Alembert paradox—yet experiments show substantial drag. The resolution: boundary layers form near solid walls, where viscosity is not negligible, even if the bulk flow is nearly inviscid. Accounting for boundary-layer separation (the point where flow reverses direction near the wall) requires viscous analysis. The thin boundary layer still dissipates energy and produces drag.
- Common failure mode: Using inviscid approximations to estimate drag without accounting for boundary-layer separation; assuming that viscosity is unimportant because the Reynolds number is large globally, ignoring that viscous effects are localized to thin, high-shear regions.
-
T3 — Laminar vs. Turbulent Regime (Reynolds-Number Transition):
- Structural tension: The [5] Reynolds number Re = ρ V D / η (density × velocity × length / viscosity) predicts the flow regime. At low Re (< 1000 in pipes), flow is laminar: orderly, predictable, dominated by viscous forces. At high Re (> 4000 in pipes), flow becomes turbulent: chaotic, with eddies and mixing. The transition region (1000–4000) is intermittent and sensitive to disturbances. Methods designed for one regime (e.g., laminar Poiseuille flow) fail catastrophically in the other (turbulent drag increases nonlinearly with velocity). Cross-link with
turbulenceG3 sibling for detailed treatment. - Common failure mode: Extrapolating laminar-flow formulas to turbulent conditions; under-estimating drag in the transition zone; ignoring that even "smooth" pipes have roughness that triggers turbulence earlier at moderate Re.
- Structural tension: The [5] Reynolds number Re = ρ V D / η (density × velocity × length / viscosity) predicts the flow regime. At low Re (< 1000 in pipes), flow is laminar: orderly, predictable, dominated by viscous forces. At high Re (> 4000 in pipes), flow becomes turbulent: chaotic, with eddies and mixing. The transition region (1000–4000) is intermittent and sensitive to disturbances. Methods designed for one regime (e.g., laminar Poiseuille flow) fail catastrophically in the other (turbulent drag increases nonlinearly with velocity). Cross-link with
-
T4 — Compressible vs. Incompressible (Mach-Number Regime):
- Structural tension: When fluid velocity is much smaller than the speed of sound (M = V/c << 1, where M is the Mach number), density variations are negligible and the flow is incompressible: the continuity equation simplifies to ∇·v = 0. At high Mach numbers (M > 0.3), compressibility effects become significant: shock waves form, density varies sharply, and the energy equation couples to the momentum equation. The incompressible assumption breaks down, and compressible Euler or Navier-Stokes must be used.
- Common failure mode: Applying incompressible formulas to high-speed flows (transonic aircraft, rocket nozzles) where shocks and density jumps dominate; ignoring that at M > 1 (supersonic), entirely new phenomena (shock-boundary-layer interaction, shock-shock interaction) emerge.
-
T5 — Steady vs. Unsteady (Time-Dependence; Transient Effects):
- Structural tension: Many flow analyses assume steady state: ∂/∂t = 0 (no time-dependence). This is valid after transient startup effects decay. However, many flows are inherently unsteady: pulsating flows (blood in arteries), oscillating boundary conditions (vibrating plates), or flow instabilities (vortex shedding from cylinders). In unsteady flow, the storage and dynamics of the flow field matter: a large buffer (inertia, elasticity) can decouple inflow from outflow transients, changing the response timescale dramatically.
- Common failure mode: Designing a pipe system assuming steady-flow capacity, then operating it with transient demand (e.g., pump startup surge); ignoring that acceleration terms (ρ ∂v/∂t) can dominate early in transients and require different control strategies than steady-state analysis suggests.
-
T6 — Newtonian vs. Non-Newtonian (Constitutive Law; Rheological Complexity):
- Structural tension: The Navier-Stokes equations assume a Newtonian fluid: viscous shear stress τ is proportional to strain rate: τ = η dv/dy, where η is constant. But many real fluids are non-Newtonian: blood is viscoelastic (viscosity decreases with shear rate, an effect called shear-thinning); polymer solutions exhibit memory effects (past deformation affects current stress); and suspensions can show yield stress (they don't flow until a threshold stress is exceeded). Using the Newtonian assumption in these regimes can lead to dramatically incorrect flow predictions.
- Common failure mode: Assuming constant viscosity when designing systems for blood flow, paint rheology, or slurry transport, where non-Newtonian effects dominate; ignoring that viscoelastic fluids can exhibit die swell (expansion beyond the nozzle diameter) and secondary flows (circulatory patterns perpendicular to the main flow) that Newtonian theory misses.
Structural–Framed Character¶
Flow sits at the structural end of the structural–framed spectrum: it is a pure relational pattern, the same in any domain where it appears, and nothing about its meaning depends on a particular field's vocabulary or assumptions. It describes the directional transfer of a conserved quantity from source to sink along channels shaped by gradients and constraints.
The diagnostics are unanimous. The pattern applies unchanged to mass through a pipe, charge through a circuit, traffic on a road, money through an economy, or data through a network — no home vocabulary needs to accompany it. It carries no evaluative verdict; flow is simply rate, direction, and conservation. Its origin is a formal relation expressing that what enters one region leaves another minus storage or loss, definable with no reference to human institutions. And it is something you recognize as already operating in a system rather than a perspective imported from outside. On every diagnostic, it reads structural.
Substrate Independence¶
Flow is about as substrate-independent as a prime can be — composite 5 / 5 on the substrate-independence scale. Its signature is purely structural — a transported quantity with a direction, a rate, and a conservation constraint — and the very same mathematical and conceptual logic governs water, electricity, money, information, and people. It spans physics, systems engineering, ecology, economics, and information systems with equal ease. This is a core anchor of the scale: maximum transfer evidence and universal reasoning leverage across every substrate, a canonical 5.
- Composite substrate independence — 5 / 5
- Domain breadth — 5 / 5
- Structural abstraction — 5 / 5
- Transfer evidence — 5 / 5
Relationships to Other Abstractions¶
Current abstraction Flow Prime
Foundational — no parent edges in the catalog.
Children (83) — more specific cases that build on this
-
Axonal Transport Domain-specific is a kind of Flow
Axonal Transport is the neuronal specialization of Flow in which motor proteins carry material and signals bidirectionally along polarized microtubule tracks.It inherits directional transfer, transported quantities, rates, paths, and failure under interrupted movement, while fixing the substrate to an axon, the carriers to kinesin and dynein, and the endpoints to soma and synaptic terminal.
-
Balanced Flow Domain-specific is a kind of Flow
Flow. Balanced Flow is literally a geophysical-fluid flow regime, so Flow is the strict subsumption parent.Flow. Balanced Flow is literally a geophysical-fluid flow regime, so Flow is the strict subsumption parent.
-
Beam bridge Domain-specific is a kind of Flow
The proposed strict upward parent is
prime:flow.prime:flow is the nearest broader Prime; the source-domain carrier and recognition invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Beam bridge adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the span and support layout, beam and deck geometry, material system, connection and moment-release assumptions, load cases, bending and shear path, lateral bracing, continuity and serviceability or capacity criteria are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Beam bridge. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge toprime:flow. No live DAG mutation is authorized.
- Coastal sediment transport Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.The identity is a mass flow of sediment driven by coastal forces; morphodynamic feedback supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Coastal sediment transport adds domain-specific constraints. The entry does not collapse into that parent because morphodynamic coupling of coastal hydrodynamics, grain response and landform evolution across alongshore and cross-shore pathways It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Coastal sediment transport. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Confluence Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.A confluence combines multiple flows into one downstream path; fluvial junction geometry supplies the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Confluence adds domain-specific constraints. The entry does not collapse into that parent because river-network junction with coupled hydrodynamic, sedimentary and ecological effects It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Confluence. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Cumulative flow diagram Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Cumulative flow diagram adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by workflow states are ordered and exhaustive, counting and entry/exit rules are stable, time scale is explicit, and interpretations distinguish inventory thickness from cumulative totals It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Cumulative flow diagram. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Curl (mathematics) Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Curl (mathematics) adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by orientation, coordinates, differentiability and metric conventions yield the stated circulation-density relation It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Curl (mathematics). This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Density Current Domain-specific is a kind of Flow
Density current is a flow subtype whose direction and rate are selected by gravitational adjustment of a density contrast.Both require directional transport of matter at a rate through a medium under a driving gradient and continuity constraints. Density current additionally requires a denser moving body, lighter ambient medium, gravity-driven front, and stratified interface.
- Downwelling Domain-specific is a kind of Flow
Downwelling is the vertical-transfer specialization of flow in which convergence or buoyancy loss moves surface fluid and its tracers into a lower interior reservoir.It preserves transported quantity, rate, direction, driver, and continuity while fixing the vertical sign and rotating-stratified-fluid setting. Flow supplies the genus: Structured movement of energy, matter, or information. Downwelling preserves that general structure while adding its differentia: The oceanographic process by which surface fluid converges and sinks under mass conservation, carrying heat, oxygen, and carbon into the interior — the paired complement of upwelling, splitting into gentle gyre subduction and rapid deep convection. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Ekman Transport Domain-specific is a kind of Flow
Ekman transport is the rotating-boundary-layer specialization of flow in which sustained wind stress drives a depth-integrated mass flux perpendicular to the wind.It preserves rate, direction, transported matter, driving force, and continuity while adding the Coriolis-friction balance and latitude sign rule. Flow supplies the genus: Structured movement of energy, matter, or information. Ekman Transport preserves that general structure while adding its differentia: Predict where sustained wind drives ocean water by deflecting the net depth-integrated flux 90° from the wind — right in the Northern Hemisphere, left in the Southern — set by the balance of wind stress against the Coriolis force, magnitude τ/(ρf). The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Electric power Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Electric power adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the circuit or field boundary, voltage and current reference directions, passive or source sign convention, waveform and frequency, instantaneous or averaged interval, DC or AC definition, phase and RMS convention, losses, and units are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Electric power. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Energy current Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Energy current adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the declared flux integrated over an oriented surface yields the corresponding energy-transfer rate under the governing conservation law It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Energy current. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Exergonic process Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Exergonic process adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the system boundary, reaction direction, thermodynamic state and standard convention are declared and the Gibbs free-energy change for that direction is negative It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Exergonic process. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Exothermic process Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Exothermic process adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by system boundary, path, thermodynamic constraints, heat sign convention, and measured or calculated outward heat transfer are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Exothermic process. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Export Domain-specific is a kind of Flow
The minimal prospective placement is a composition/instantiation relation to live `prime:flow`.An export is an outward economic flow across a declared international boundary, while the node adds product, counterparty, accounting, customs, and regulatory semantics. Composition avoids treating a classified trade transaction as a taxonomic subtype of every physical or informational flow. `prime:exchange` applies to reciprocal sales and barter but is not strict coverage because aid or gifts can have goods-and-services entries with corresponding transfers. `prime:source_sink_role` can classify an economy by net transfer over an interval, but an individual export is a directional transaction, not the time-aggregated source role. Frozen semantic top `domain_specific:open_innovation` is false coverage: using external and internal knowledge channels does not entail international product supply or trade accounting.
- Geological Lava Flow Domain-specific is a kind of Flow
A geological lava flow is directional matter flow specialized to cooling, crystallizing molten rock moving from a volcanic vent across terrain.It inherits transported matter, direction, rate, driving potential, path, and continuity. The child fixes the material to erupted lava, the principal drive to gravity and supply pressure, and adds evolving temperature-dependent viscosity, crystallization, crust formation, topographic confinement, and arrest when resistance exceeds driving stress.
- Information Flow (Information-Flow Security) Domain-specific is a kind of Flow
**Flow** is the strict parent because the construct tracks structured movement of information from sources through program channels to observations.Data Leakage is a possible prohibited instance, not the neutral parent. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Insufflation (Medicine) Domain-specific is a kind of Flow
**Flow** is the strict parent because clinical insufflation is a directed, rate-governed movement of matter from a source into a receiver, driven through a bodily or procedural pathway whose medium and boundaries shape the transfer.Channel and Transformation are related, but Flow most literally captures the procedure as an introduction event rather than the conduit or resulting state. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Intramolecular vibrational energy redistribution Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Intramolecular vibrational energy redistribution adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the molecule and electronic state, initial vibrational excitation, normal-mode basis, energy and angular-momentum constraints, anharmonic couplings, state density and resonances, redistribution observable and timescale, coherence, environment, competing reaction or relaxation, and statistical-limit assumption are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Intramolecular vibrational energy redistribution. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Isentropic Nozzle Flow Domain-specific is a kind of Flow
**Flow.** The node strictly instantiates structured transport: a material stream has direction, rate, channel, driving pressure difference, and continuity.This is the strongest genus-level parent.
- Law of the wall Domain-specific is a kind of Flow
**Flow** (`prime:flow`).The abstraction describes the mean motion of fluid relative to a solid boundary.
- Maritime transport Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.The candidate literally organizes movement of passengers or goods through linked waterborne channels and interfaces; vessels, routes, ports, custody, and maritime regimes provide the domain-specific residual. The edge is proposal-only and points to a frozen prior-baseline Prime. The entry does not collapse into the parent because the waterborne mode architecture linking carriage to vessel, navigable route, port interface, and maritime governance, not the shipping industry generally or every activity occurring at sea A thematic neighbor is declined whenever it does not literally subsume that rule. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Mass injection flow Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow supplies the nearest cross-domain structural operation, while Mass injection flow retains a constitutive identity specific to compressible flow. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Mass injection flow adds domain-specific constraints. The entry does not collapse into that parent because Heat-addition Rayleigh flow and frictional Fanno flow approach choking through different constitutive changes; real injection devices can violate the one-dimensional idealization. It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Mass injection flow. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Mass transfer Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and stated invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Mass transfer adds domain-specific constraints. The entry does not collapse into that parent because the autonomous transport phenomena identity defined by species balances close and flux laws, frames, interfaces, and transfer coefficients use consistent conventions It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Mass transfer. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Mass Wasting Domain-specific is a kind of Flow
Mass wasting is matter flow specialized to gravity-driven downslope transfer without a carrying medium.Both are structured movement of matter with direction and rate. The child fixes rock, regolith, or soil moving downslope under gravity as the sole transport agent.
- Material derivative Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Material derivative adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the continuum domain, velocity and target field regularity, Eulerian coordinates, pathline, local and convective terms, scalar or tensor transformation, compressibility and frame convention, and distinction from flux divergence are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Material derivative. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Material Flow Analysis Domain-specific is a kind of Flow
**Flow** is the strict parent because material quantities move among sources, processes, stocks, and sinks.Conservation Laws are also presupposed, but Flow best captures the node-edge-stock representation. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Mesoscale Eddy Domain-specific is a kind of Flow
A mesoscale eddy is a coherent rotating and translating flow specialized to trapping a parcel.Both are structured movement of matter with a velocity field, direction, and transport rate. The child fixes closed streamlines, coherent rotation, a trapped interior, finite lifetime, and translation across the mean ocean flow.
- Ocean Current Domain-specific is a kind of Flow
An ocean current is the rotating-seawater specialization of flow: persistent directional bulk transfer carries water and entrained heat, salt, nutrients, and matter from source regions along structured paths.The child supplies the geostrophic, Ekman, thermohaline, tidal, and basin-geometry force balances that select the marine path. Flow supplies the genus: Structured movement of energy, matter, or information. Ocean Current preserves that general structure while adding its differentia: A large-scale, persistent, directionally organized flow of seawater — set by a force balance among wind, pressure gradient, Coriolis, and friction — that advects heat, nutrients, and matter along a known path, wiring distant ocean basins into one coupled system. The parent can occur without those added commitments, whereas removing the parent structure leaves no basis for classifying the child as this subtype. That asymmetry establishes subsumption rather than mere association.
- Passive solar building design Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Passive solar building design adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the site and climate file, building use and loads, orientation, glazing and shading geometry, envelope and air leakage, thermal mass, ventilation, moisture, comfort criteria, seasonal energy balance, overheating test, and code compliance are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Passive solar building design. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Poynting Vector Domain-specific is a kind of Flow
Poynting Vector strictly specializes **Flow**: it is structured directional transport of electromagnetic field energy with a local rate, medium, boundary, and continuity relation.**Conservation Laws** explains Poynting's theorem, but the vector is a flux term rather than itself a conservation law. **Boundary** explains the conversion from local flux to net surface power. **Momentum** is quantitatively related in vacuum but remains a distinct physical quantity. Only Flow is proposed as the minimal DAG parent. Conservation Laws, Boundary, and Momentum are explanatory relations rather than parallel taxonomic genera.
- Process (Engineering) Domain-specific is a kind of Flow
**Flow** is the proposed immediate parent.Transformation, Procedure, Feedback, Constraint, Interface, Standardization, Traceability, and Quality Control are related. Stage Gate Process is one particular governance shape, not coverage of the general engineering identity. The prospective queue contains one strict edge to `prime:flow`. No live DAG mutation is authorized.
- Reaching definition Domain-specific is a kind of Flow
Reaching Definition instantiates Flow because assignment facts propagate along control-flow edges subject to local generation and removal.The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Schwarzschild's equation for radiative transfer Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Schwarzschild's equation for radiative transfer adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the ray geometry and wavelength or frequency, absorption coefficient and density, path coordinate, local temperature and Planck function, no-scattering and LTE assumptions, boundary intensity and optical-depth convention are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Schwarzschild's equation for radiative transfer. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Social support Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Social support adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the recipient and providers, relationship and network structure, support type, perceived, available or received status, need and stressor, timing and matching, reciprocity, measure, confounding and selection, cultural context, unwanted or harmful support, outcome, and uncertainty are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Social support. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Solar Jet Domain-specific is a kind of Flow
Solar Jet strictly instantiates **Flow**: matter and energy move in a spatially organized direction through a magnetic channel.It relates to Transient Response because the outflow has an onset, growth, and decay; to Tension and Release because magnetic stress accumulates and releases; and to Channel because field geometry constrains the transport path. The minimal proposed DAG parent is `prime:flow`. Effusive and Explosive Eruption are volcanic domain-specific nodes and are not parents. Greenhouse Effect is a frozen semantic false neighbor with no shared mechanism.
- Space-based solar power Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Space-based solar power adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the full collection-conversion-transmission-reception chain closes an energy balance and addresses orbital, beam, lifecycle, and governance constraints It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Space-based solar power. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Statistical energy analysis Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Statistical energy analysis adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the physical system and frequency band, subsystem partition and modal density, stored energies, input powers, damping and coupling loss factors, reciprocity and diffuse-field assumptions, balance matrix, solution and validation range are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Statistical energy analysis. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Stefan adhesion Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Stefan adhesion adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the plate geometry and alignment, fluid rheology and viscosity, gap and rate, boundary and inertia assumptions, force sign and units, validity regime and corrections are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Stefan adhesion. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Stellar Wind Domain-specific is a kind of Flow
The minimal prospective placement is a strict `subsumption/specializes` edge to live `prime:flow`.A stellar wind is literally structured movement of stellar matter, energy, and momentum; it specializes Flow with an atmospheric source, escaping regime, and astrophysical consequences. `prime:escape` is related to overcoming stellar gravity, but the live catalog's Flow identity is the more direct genus. `prime:feedback` describes evolutionary and environmental consequences, not the outflow itself. Frozen semantic neighbor `domain_specific:coastal_upwelling` is false coverage. Both move fluid, but coastal upwelling is wind-driven ocean transport toward a surface, not stellar atmospheric escape.
- Strainer arch Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Strainer arch adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the structure and support geometry, observed movement and load case, arch form and material, interfaces and abutments, compression and thrust path, construction sequence, evidence of structural purpose and present condition are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Strainer arch. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Subduction Domain-specific is a kind of Flow
Subduction is the negative-buoyancy specialization of directional matter flow, carrying lithosphere from a surface boundary into the mantle.Both specify transported matter, direction, rate, a driving potential, a path, and conservation across source, transit, transformation, and sink regions. The child fixes the transported matter to coherent lithosphere, the driver to negative buoyancy and slab pull, and the path to a convergent plate boundary descending into mantle.
- Submodular flow Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Submodular flow adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the directed graph, edge lower and upper bounds and costs, submodular function and its oracle or representation, excess sign convention, all-subset feasibility inequalities, integrality assumptions, objective and optimality certificate are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Submodular flow. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Subsurface Flow Domain-specific is a kind of Flow
water has a direction, rate, driving potential, medium, and continuity balance.water has a direction, rate, driving potential, medium, and continuity balance.
- Taylor–Culick flow Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Taylor–Culick flow adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the cylindrical or analogous geometry, closed and open ends, uniform sidewall injection, incompressible inviscid or declared approximation, axisymmetry, boundary conditions, similarity velocity field and domain limits are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Taylor–Culick flow. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Thermogenesis Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Thermogenesis adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the organism or tissue, environmental and physiological state, heat-production mechanism, metabolic substrate and oxygen use, measured heat or temperature, thermoregulation distinction and uncertainty are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Thermogenesis. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Thermophotovoltaic energy conversion Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Thermophotovoltaic energy conversion adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the heat source and emitter temperature and spectrum, geometry and view factor, filter and photon-recycling design, photovoltaic material and bandgap, cell temperature and electrical operating point, input heat boundary, output power, efficiency definition and loss balance are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Thermophotovoltaic energy conversion. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Unidirectional data flow Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime; the source domain and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Unidirectional data flow adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity determined by the state owner, event and action types, one-way transition path, mutation boundary, reducer or update semantics, derived views, side-effect handling and replay or debugging guarantees are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Unidirectional data flow. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Walker Circulation Domain-specific is a kind of Flow
**Flow — proposed parent.** Walker Circulation is structured movement of atmospheric mass, heat, moisture, and momentum with direction, rate, and approximate continuity.It strictly specializes Flow to a tropical zonal–vertical overturning geometry. **Feedback — related.** In the Pacific, winds, thermocline, upwelling, SST gradient, and convection participate in Bjerknes feedback. Feedback helps maintain and vary the cell but is not required as the taxonomic parent of every diagnosed circulation state. **Gradient — related.** Zonal heating, SST, and pressure contrasts organize the branches. A gradient without coherent overturning is insufficient. **Teleconnection — related.** Walker anomalies couple distant tropical sectors and excite wider climate responses. Teleconnection names the remote relationship; Walker Circulation names the intervening tropical overturning.
- Waterspout Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.A waterspout is structured movement of air and entrained spray organized into a rotating vertical column. Water contact, vortex geometry, cloud coupling, and typed genesis provide the autonomous meteorological residual. The edge is proposal-only and points to a frozen prior-baseline Prime. The entry does not collapse into the parent because the water-contact phase of a vertically organized atmospheric vortex, with a typed fair-weather or tornadic genesis and distinct visual and operational evidence, not generic cloud funnels, ocean spray, or any tornado photographed near a coast A thematic neighbor is declined whenever it does not literally subsume that rule. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Work Output Domain-specific is a kind of Flow
**Flow** is the strict parent because work output is energy crossing a system boundary outward.Conservation and Efficiency are related constraints, but neither alone defines the directional transfer. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Wormhole switching Domain-specific is a kind of Flow
The proposed strict upward parent is `prime:flow`.prime:flow is the nearest broader Prime while the source-domain carrier and invariant supply the autonomous residual. This is a proposal-only workspace relationship: the accepted Prime supplies a genuinely instantiated structural prerequisite or superclass, while Wormhole switching adds domain-specific constraints. The entry does not collapse into that parent because the domain-specific identity fixed by the network topology and routing function, packet and ordered flits, header routing state, router input and output channels, buffer depth, channel reservation, backpressure and stall propagation, tail release, latency and throughput and deadlock and virtual-channel conditions are explicit It also declines a nearby thematic catalog node: the neighbor does not literally subsume the constitutive identity of Wormhole switching. This explicit assert-and-decline pattern keeps the proposed DAG narrow and prevents a merely thematic edge. The prospective workspace queue contains one strict upward edge to `prime:flow`. No live DAG mutation is authorized.
- Convection Prime is a kind of Flow
Convection is a specialization of flow whose transport is carried by buoyancy-driven bulk motion of the fluid itself.Convection is a specialization of flow in which the transported quantity, typically heat or mass, is carried by coherent bulk-fluid displacement driven by density contrasts arising from temperature or composition gradients. It inherits the general flow commitment of directional transfer of a conserved quantity through a system with rates, conservation, and a driving gradient, and specializes by fixing the transport mechanism to self-organized buoyant circulation rather than diffusion, pressure-driven channel flow, or advection by an externally imposed velocity field.
- Diffusion Prime is a kind of Flow
Diffusion is a specialization of flow in which net transport arises from microscopic stochastic motion down a concentration gradient.Diffusion is a specialization of flow in which the transport mechanism is the aggregate of microscopic random walks rather than coherent bulk motion, and the driving gradient is in concentration of the transported quantity itself. It inherits the general flow commitment of directional transfer of a conserved quantity from source to sink along a gradient, and specializes by fixing the mechanism to stochastic redistribution that yields Fick's-law proportionality between flux and gradient, with no central agent directing the movement.
- Absorption Phase Domain-specific is part of Flow
Absorption Phase contains directed, rate-bearing drug flow from an administration reservoir across physiological barriers into circulation.The phase is the rising limb generated while matter moves from a dose site to the systemic compartment. The absorption constant measures that flow rate; permeability, dissolution, transporters, and blood supply shape its channel; incomplete survival appears as loss or diversion before the destination.
- Divergence Zone Domain-specific is part of Flow
A divergence zone contains surface outflow and compensating replacement flow.Remove structured movement away from the primary plane and movement from an adjacent reservoir into the deficit, and the three-part divergence mechanism disappears. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Divergence Zone requires that role within this mechanism: A geophysical-fluid pattern in which surface material flows apart, opening a deficit that mass conservation forces to be filled by inflow from an adjacent reservoir — so the consequence is set not by the separation but by the replacement reservoir's properties. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Elimination Pathway Domain-specific is part of Flow
An elimination pathway contains the directed flow of a drug, toxin, or metabolite from the body's internal stock toward an excretory sink.The pathway's defining clearance rate is the throughput of a transported quantity along a physiological route. Without directed, rate-bearing movement from an entrant or circulating stock to a sink, there is neither elimination nor a route whose clearance can be measured.
- Fluency Domain-specific is part of Flow
Output Fluency contains the forward flow of a speech stream whose rate, direction, and interruptions can be measured separately from the content transported.Speech production moves linguistic information through a temporally ordered output channel. Fluency is the clinical description of how smoothly that movement proceeds; without a stream that can advance, stall, repeat, or resume, the disfluency morphology has no carrier.
- Just-in-Time Domain-specific presupposes Flow
JIT presupposes a staged flow whose adjacent production or delivery stages can be coupled through consumption-triggered replenishment.The chain of stages can exist under push or buffered production without JIT and is therefore enabling substrate rather than an internal policy object. Flow supplies the prerequisite condition: Structured movement of energy, matter, or information. Just-in-Time operates against that background: Replenish each production stage only when the next one consumes its input, deliberately shrinking buffers so disruption propagates instead of hiding — a coupling that pays off only when paired with the variability-reduction work that earns it. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Karst Domain-specific is part of Flow
Karst contains fast channelised groundwater flow through its conduit network.Without matter moving from sinkholes through subsurface conduits to discrete springs, the hydrologic behavior that distinguishes karst from porous media disappears. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Karst requires that role within this mechanism: Diagnose a landscape where acidic groundwater has dissolved soluble bedrock into a self-reinforcing hidden conduit network, so the surface no longer maps the subsurface drainage and porous-media terrain rules are suspended. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Larval Dispersal Domain-specific is part of Flow
Larval dispersal contains flow because moving water carries larval matter from spawning sources toward settlement sinks.Currents, tides, eddies, and fronts supply structured material transport; larval behavior modulates which flow layer is used but does not eliminate the water-borne source-to-sink movement.
- Line of Operation Domain-specific is part of Flow
Movement of forces and sustainment along the axis is a constituent of the line-of-operation structure.A line of operation is not static geometry alone: it carries structured movement of personnel, materiel, and operational effects toward the objective. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Line of Operation requires that role within this mechanism: Organise a campaign along physical or force-orientation axes converging on an objective, collapsing an undifferentiated theatre into a few geometric rails on which decisive points, culminating points, and convergences do the planner's bookkeeping. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Meander Cutoff Domain-specific is part of Flow
Meander cutoff contains river flow whose gradient advantage captures the shorter route.Without moving water selecting and enlarging the shorter steeper path, the breach cannot capture routing or abandon the old loop. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Meander Cutoff requires that role within this mechanism: Read a river's sinuous life cycle as a single feedback in which outer-bank erosion both lengthens the loop and narrows its neck until a flood breaches it, abruptly capturing flow through a shorter steeper path and abandoning the loop as an oxbow. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Scavenger Domain-specific is part of Flow
Scavenging is most directly related to live `prime:flow`: each feeding link moves carcass-derived matter and chemical energy from a finite resource into consumer biomass and, through excretion, caching, mortality, and subsequent.Scavenging is most directly related to live `prime:flow`: each feeding link moves carcass-derived matter and chemical energy from a finite resource into consumer biomass and, through excretion, caching, mortality, and subsequent consumption, onward through an ecosystem. The proposed DAG relation is composition rather than subsumption because a scavenger is an ecological role, not itself a generic flow. Rates and conservation become explicit when the role is analyzed at population or food-web scale. Live `prime:network` is also conceptually related because scavenging adds resource-consumer links to food webs, often connecting detrital and grazing channels. It is not proposed as a second parent: almost every ecological role participates in a network, so that edge would add little locality. Live `prime:source_sink_role` can describe a scavenger as a local sink for carcass biomass over a chosen interval, but the sign can change with boundary and export, and source-sink status does not define scavenging. Live `domain_specific:trophic_subsidy` is a neighbor, not a parent. Carrion can cross habitat boundaries and subsidize recipient consumers, but scavenging requires neither cross-habitat transport nor recipient abundance above local productivity. Conversely, a trophic subsidy may consist of live migrants, plant material, guano, or other imports with no scavenging.
- Sediment Transport Domain-specific presupposes Flow
Sediment transport presupposes flow because a moving carrier with rate, direction, field, and continuity supplies the shear that entrains and conveys the load.Water, wind, ice, and density current change the force laws but not the dependency on a directed carrier movement from source toward sink. Flow supplies the prerequisite condition: Structured movement of energy, matter, or information. Sediment Transport operates against that background: Loose grains are entrained by a moving fluid once shear exceeds their threshold of motion, carried in a mode set by the ratio of shear to settling velocity, and deposited as the carrier loses energy — sorting coarse-to-fine along the gradient into a graded deposit that records the flow. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Space syntax Domain-specific presupposes Flow
Space syntax presupposes flow because its defining empirical claim maps graph configuration to the directional rate and distribution of pedestrian movement through the layout.Its graph can be computed before observation, but the method's distinctive interpretation includes aggregate movement or co-presence as the predicted transported quantity. Flow supplies the prerequisite condition: Structured movement of energy, matter, or information. Space syntax operates against that background: Represent a spatial layout as a graph of sight-and-movement lines and compute centrality measures like integration and choice, so a space's pedestrian use, vitality, and encounter rates are predicted from its configurational position rather than its local design. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Transport Convergence Zone Domain-specific presupposes Flow
A transport convergence zone presupposes directed flow fields whose opposing or converging velocities create the region.Without directed transport there is no convergence geometry, delivery flux, reduced export, or moving front to locate the zone. The zone is a spatial concentration feature produced by interacting flows; flow is the general movement and can occur without convergence or concentration.
- Velocity of money Domain-specific is part of Flow
Velocity contains nominal spending as the rate-bearing flow in its numerator, paired with the money stock that mediates that flow.V = PY/M cannot be formed without a nominal-output flow measured over a period. Flow is therefore a literal internal constituent rather than the taxonomic identity of a derived ratio. The child adds an institutionally defined money aggregate, stock normalization, equation-of-exchange role, and the separate empirical stability premise.
- Volcanism Domain-specific is part of Flow
Volcanism contains magma flow through buoyant ascent pathways, chambers, conduits, dikes, and vents.Remove directional mass transfer with measurable flux from melt source to emplacement or surface release and neither intrusion nor eruption can occur. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Volcanism requires that role within this mechanism: Explain how internally generated magma ascends and releases at a planetary surface by placing every eruption in a two-parameter space of silica (viscosity) and volatile content (explosivity), with melt generated by three solidus-crossing routes bound to tectonic setting. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Watershed Domain-specific is part of Flow
A watershed contains gravity-directed water and cargo flow toward a common outlet.Without movement of water, sediment, chemicals, and heat from contributing area to outlet, neither upstream-downstream coupling nor catchment contribution is defined. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Watershed requires that role within this mechanism: Bound the space of contributing sources for any point in a river to the terrain-defined area draining to a common outlet, then exploit the asymmetric upstream-downstream coupling — everything propagates down, nothing back up against gravity — to fix search direction and intervention shape. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Bioaccumulation Prime presupposes Flow
Bioaccumulation presupposes flow because it names the net retention that occurs when an inflow of a substance exceeds the organism's outflow capacity.Bioaccumulation presupposes flow because it describes the structural condition in which a substance enters an organism faster than it is metabolized, excreted, or otherwise eliminated, producing net buildup over time. The very notion of accumulation requires the prior availability of directional transfer of a quantity across the organism's boundary, with rates of entry and exit, conservation, and sinks. Flow supplies that general transport apparatus; bioaccumulation is what happens when inflow systematically outruns outflow in a biological compartment.
- Blockage Release Dynamics Prime is part of Flow
Blockage-release dynamics contains a flow that would otherwise pass continuously through the system.Without a moving quantity intercepted by the barrier, there is nothing to impound, accumulate, temporally compress, or discharge downstream. Flow supplies an internal constituent: Structured movement of energy, matter, or information. Blockage Release Dynamics requires that role within this mechanism: A barrier stores accumulating flow until it fails, converting steady load into a single discontinuous release far larger than the original flow. Remove the parent-role and the child loses a required internal operation, even though the parent can exist outside the child. The child is therefore built from the parent rather than being a taxonomic kind of it.
- Mixing Prime is part of Flow
Mixing contains transport flows that exchange constituents among regions while conserving the total amount being redistributed.Flow is the movement constituent inside Mixing. Whether the carrier is advection, diffusion, circulation, shuffling, or exchange, distinguishable material or information must cross local partitions for composition to become less dependent on original position. Mixing adds repeated interpenetration and the resulting reduction of spatial or sequential segregation; a flow can transport without mixing.
- Network Flow Models Prime presupposes Flow
Network flow models presuppose flow because they formalize routing and allocation as directed transport with capacity limits and conservation at every node.Network flow models presuppose flow because their entire formulation imports flow's structural commitments: a conserved quantity moves through directed edges with capacity limits, conservation at internal nodes equates inflow with outflow, and the objective is to maximize or cost-minimize a directional throughput from source to sink. Without the prior availability of flow as continuous directional transfer obeying conservation and gradient-driven movement through a structured channel network, max-flow, min-cost flow, and multi-commodity flow have no substrate on which their LP structure can rest.
- PK/PD Modeling (Pharmacokinetics / Pharmacodynamics) Prime presupposes Flow
PK/PD modeling presupposes flow because pharmacokinetic transport of drug across body compartments is structurally a flow of matter through a network.PK/PD modeling characterizes how drug concentration moves through body compartments — absorption, distribution, metabolism, excretion — which is structurally a flow process: a conserved quantity transported through a network along gradients, governed by rate and continuity equations. Without flow's machinery of directional transport with conservation, rate, and channel structure, the compartmental pharmacokinetic representation would have no transport-dynamics framework to deploy. Flow supplies the conserved-quantity transport substrate that pharmacokinetic modeling instantiates for drug molecules in physiological compartments.
- Queueing Prime presupposes Flow
Queueing presupposes flow because waiting only arises when an inflow of work items meets a service capacity that constrains throughput.Queueing presupposes flow because its structural setting is a directional transfer of items from arrival to service to departure, with rates, conservation, and channel constraints all native to flow. Without the prior availability of flow as a continuous directional transfer through a system with defined source, channel, and sink, there is no inflow-and-outflow geometry against which finite service capacity can create accumulation. Little's law and the rest of queueing theory presuppose the flow conservation that ties arrival rate to throughput and time-in-system.
- Signature-Borne Provenance Prime presupposes Flow
Signature-Borne Provenance presupposes flow to transport a signed parcel away from its formation context.Without movement through a carrier or medium, the signature does not preserve origin across changing location and the downstream backward-inference problem does not arise. Flow supplies the prerequisite condition: Structured movement of energy, matter, or information. Signature-Borne Provenance operates against that background: A conservative property carries origin through transport, read back without a custody chain. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Source-Sink Dynamics Prime presupposes Flow
Source-sink dynamics is constituted by a DIRECTED FLOW between sites on which the sink depends ('the direction of the flow is load-bearing'); it presupposes flow.Flow supplies the prerequisite condition: Structured movement of energy, matter, or information. Source-Sink Dynamics operates against that background: A system persists across coupled sites with asymmetric net balance: net-producing sources export a surplus that sustains net-consuming sinks which would decline in isolation. If the parent condition is removed, the child relation becomes undefined or loses the mechanism asserted by this edge; the parent can obtain independently, so the relation is presupposition rather than subsumption.
- Topographic Forcing Prime presupposes Flow
Topographic forcing requires an incident flow whose path, momentum, and flux distribution can be reorganized by fixed relief.Flow supplies the moving medium in the interaction. Relief without incident flow is only geometry; once a current passes it, the boundary can deflect streamlines, create vertical motion, shed wakes, generate waves, and localize dissipation. Topographic Forcing adds the fixed spatial geometry and the resulting field reorganization.
- Circular Flow Domain-specific is a decomposition of Flow
Removing economic sector labels from circular flow leaves directed, rate-bearing movement of money, goods, and income through channels with sources, sinks, storage, and continuity.Every circular-flow model tracks definite carried quantities along directed sector-to-sector edges, distinguishes gross rates from net accumulation, and locates injections and leakages at system boundaries. The child adds households, firms, government, the rest of world, opposed real and monetary loops, and national-income identities.
- Quantity Theory of Money Domain-specific is a decomposition of Flow
Removing the monetary variables from MV = PY leaves Flow's stock-times-turnover-equals-throughput relation, while stable velocity and real-output exogeneity remain the theory's domain accent.The equation of exchange maps a circulating stock, its turnover rate, and the nominal throughput it supports onto the generic structure of Flow. Money, velocity, prices, and output are the monetary coordinates; the behavioral assumptions that velocity is stable and real output is set by real factors turn the identity into the domain theory. Stripping that frame leaves the same conserved-throughput relation used by other circulating stocks.
- Clearance Rate Prime is a decomposition of Flow
Clearance Rate is the internally governed outbound-flow specialization that removes a measurable stock from a bounded system per unit time.It separates removal from upstream input and adds first-, zero-, or mixed-order kinetics, pathway vulnerability, half-life, saturation, and clearance-side intervention. After the systems_cybernetics frame is stripped away, the retained structural roles are those of Flow: Structured movement of energy, matter, or information. Clearance Rate adds the local frame and commitments expressed in its identity: The rate at which a bounded system removes substrate is a control surface separable from input, with kinetic regime and vulnerability that input-side reasoning misses. The parent pattern remains recognizable without that vocabulary, while the child is the framed realization of it. That preservation test establishes decomposition rather than taxonomic subsumption.
- Input Pressure Prime is a decomposition of Flow
Input Pressure is the externally sourced, sustained-rate specialization of Flow acting as load on a bounded receiving system.Flow supplies quantity per time across a boundary; Input Pressure fixes source externality, persistence, rate distribution, bounded response, and driver-side factoring. After the systems_cybernetics frame is stripped away, the retained structural roles are those of Flow: Structured movement of energy, matter, or information. Input Pressure adds the local frame and commitments expressed in its identity: A sustained external input rate acts as the load variable a bounded receiving system must absorb or respond to. The parent pattern remains recognizable without that vocabulary, while the child is the framed realization of it. That preservation test establishes decomposition rather than taxonomic subsumption.
Neighborhood in Abstraction Space¶
Flow sits in a sparse region of abstraction space (80th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Unclustered & Miscellaneous (424 primes)
Nearest neighbors
- Diffusion — 0.76
- Convection — 0.71
- Oscillation — 0.70
- Stochastic Process — 0.69
- Adaptation — 0.68
Computed from structural-signature embeddings · 2026-09-10
Not to Be Confused With¶
Flow must be carefully distinguished from Equilibrium, its nearest structural neighbor (similarity 0.748), because they describe opposite temporal and causal modes. Equilibrium is a state condition—a system where opposing forces balance, gradients are flat or stationary, and net change has ceased (or reaches zero on average). A lake at rest, a market price where supply equals demand, a chemical reaction at steady state where forward and reverse rates match—these are equilibrium. Flow, by contrast, is a dynamic process—the movement of a conserved quantity along channels and through a system, typically driven by the very gradients that equilibrium would eliminate. A flowing river is anti-equilibrium: the gradient of height (potential energy) drives the flow, and the flow persists because that gradient exists. In equilibrium, there is no net flow (the net flux is zero); in flow, there is directional, continuous movement. The confusion arises because some systems reach "flow equilibrium"—a steady state where the rate of flow in equals the rate of flow out, but flow continues (e.g., a river at steady discharge, a pipe system at constant flow rate). This is still flow, not equilibrium in the thermodynamic sense: the flow is steady (rates don't change over time) but not zero. The key distinction: equilibrium is the absence or cancellation of flow; steady flow is a flowing system with constant parameters. Understanding which is present changes the analysis: equilibrium thinking asks "what forces balance here?"; flow thinking asks "what drives movement and at what rate?"
Flow is also distinct from Conservation Laws, though the two are frequently conflated. Conservation laws are principles that constrain how quantities can change—energy is conserved (it cannot be created or destroyed, only transformed); mass is conserved in closed systems; momentum is conserved in isolated systems. These are meta-laws: they apply across all substrates and bound what is possible. Flow, by contrast, is a mechanism by which conserved quantities move from one place to another. Conservation laws describe what cannot change globally; flow describes how quantities do change locally (increasing in one region, decreasing in another) while respecting conservation globally. A mass-balance equation (conservation of mass) states that the mass entering a region equals the mass leaving plus the change in stored mass: in = out + storage. Flow is the "in" and "out" terms—the actual transport rates. A Hamiltonian system conserves energy (conservation law); the energy sloshes between potential and kinetic forms (flow of energy between modes). The distinction matters because a conservation-law perspective answers "what must be true?"; a flow perspective answers "what is actually moving and at what rate?" Many systems violate conservation if you forget to account for flow: a region's temperature rises (violating energy conservation) until you account for the heat flow entering from neighboring regions.
Nor is flow identical to Convection, though convection is a specific type of flow. Convection is the transfer of heat (or more generally, a thermodynamic property) via the bulk motion of a fluid—hot air rises, carrying thermal energy upward; ocean currents carry warmth from equator to poles. Convection is heat transported by fluid flow. Flow is the broader structural category: any conserved or quasi-conserved quantity moving through a system along channels shaped by gradients. Convection is a particular application of flow to thermal transport in fluids. Water flowing through a pipe due to pressure difference is flow but not convection (unless the water is being heated and we care about thermal transport). A sediment plume spreading through an estuary is flow (suspended particles moving with water), and it can couple with convection if density gradients drive circulation. The distinction clarifies scope: convection is specifically about heat or mass transfer by fluid motion in response to density gradients; flow is the general transport principle applicable to heat, mass, momentum, money, information, people, or any conserved quantity along any channel. A financial capital flow through a banking system is flow but not convection (no fluid, no heat). An electrical current through a circuit is flow but not convection. The term "convective derivative" in fluid mechanics (∂/∂t + v·∇) applies the flow perspective to any quantity advected with the fluid, not just heat.
These distinctions are essential for practitioners because conflating flow with equilibrium leads to mistaking dynamic transport for static balance; conflating flow with conservation leads to losing sight of rates and bottlenecks (conservation says "what enters must leave," but flow analysis asks "how fast?"); and conflating flow with convection narrows focus to thermal transport when the structural insight applies much more broadly. Clarity separates the constraint (conservation) from the mechanism (flow) from the absence of mechanism (equilibrium).
Cross-Links¶
The entry flow is central to the DP-12 G3 fluid dynamics triad:
turbulence(G3 sibling): High-Reynolds-number regime where flow becomes chaotic; [12] energy cascades across scales and dissipates at small eddies (Kolmogorov's legacy) [12].instability(G3 sibling): Flow transition mechanism; the conditions under which steady laminar flow loses stability to growing perturbations.wave(G1): Waves in flow; surface waves on water, gravity waves in stratified fluids, Rossby waves in geophysical flows; see Format A example of atmospheric jet stream.damping(G1): Viscous damping of oscillations and waves; energy dissipation in flow.diffusion(DP-11 G4): Random-walk transport; heat diffusion and mass diffusion are governed by diffusivity analogous to kinematic viscosity.convection(DP-11 G4): Heat and mass transport by bulk fluid motion; combines flow field with diffusion gradients.dimensional_analysis(DP-10 G4): Reynolds number and other dimensionless groups scaling flow regimes; see Tension T3.
Solution Archetypes¶
Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.
Built directly on this prime (28)
- Batch Size Calibration: Set batch size as a controllable design variable, not a habit: make the batch large enough to amortize setup cost but small enough to preserve flow, safety, responsiveness, and timely feedback.▸ Mechanisms (10)
- Batch Quality Review Window — A recurring review of grouped work sized to balance signal reliability against correction delay.
- Batch Release Gate — A release-control protocol that checks batch size, rollback capacity, risk, and downstream absorption before release.
- Batch Size Guardrail Dashboard — A dashboard tracking lead time, queue age, setup utilization, defect discovery delay, and batch-risk exposure.
- Batch Size Tuning — Sets how many items are grouped before they move to the next stage, trading per-item overhead against the residence time and pile-up that large batches create.
- Economic Order Quantity Model — A formulaic inventory mechanism for balancing ordering or setup cost against holding cost.
- Production Lot Size Review — A review procedure for comparing production lot sizes against changeover, storage, quality, and downstream-flow costs.
- Queue Simulation Sweep — A simulation that evaluates candidate batch sizes under stochastic arrivals, service times, and capacity.
- Rolling Batch Size A/B Test — A controlled comparison of candidate batch sizes using operational metrics.
- Setup Time Reduction and Recalibration — A workflow that lowers setup or switching cost and then recalculates the batch-size operating band.
- Transfer Batch Split — A mechanism that decouples production batch size from the smaller batch moved to the next stage.
- Bottleneck Identification and Relief: Find the stage, resource, role, queue, or transition that limits whole-system throughput, then relieve, protect, redesign, or prioritize around it.▸ Mechanisms (11)
- Automation of Bottleneck Stage — Relieves the binding stage by replacing its manual work with machine or software execution — changing the kind of capacity at the constraint, not just the amount.
- Bottleneck Analysis Workshop — A facilitated cross-functional session that builds one shared flow map and reconciles the competing local views of different teams into a single, agreed system constraint.
- Bottleneck Buffer — A deliberately maintained reserve of ready work staged just before the constraint, so upstream variability never leaves the binding stage idle.
- Bottleneck Priority Rule — A prioritization policy that decides, when demand exceeds the constraint's capacity, which work the scarce stage takes first — aligned to the system objective, not to whoever shouts loudest.
- Capacity Expansion — Relieves the constraint by investing in more of the same binding capacity — additional units, hours, machines, or licensed throughput at the stage that limits the whole.
- Input Quality Check — Screens incoming work at the door of the constraint, admitting only complete, correct, and relevant items so scarce capacity is never spent on avoidable clarification or rework.
- Process Mining / Trace Analysis — Reconstructs the real process from event traces — discovering the actual control flow, its variants, and where reality deviates from the intended path — that the log reveals but no diagram admits.
- Queue Analysis — Reads queue length, wait time, and service rate across a flow to locate the binding station and size how far work is backing up behind it.
- Staffing Relief / Cross-Training — Widens the constraint by adding people or cross-skilling existing ones, so more qualified hands can serve the bottleneck when it binds and flex away when it moves.
- Theory of Constraints Cycle — Runs Goldratt's five focusing steps as a loop — define system throughput, find the constraint, exploit it, subordinate everything else, elevate it, then repeat because the constraint moves.
- Work-in-Progress Limit — Caps how many items may be in a stage or flow at once, so upstream work can't flood the constraint and cycle time stays short.
- Boundary Permeability Control: Regulate what may cross a boundary so the system can exchange what it needs while limiting harmful intrusion, leakage, contamination, or overload.▸ Mechanisms (12)
- API Gateway — A single programmable entry point in front of backend services that authenticates, throttles, routes, and reshapes every request before it reaches anything real.
- Border Checkpoint — A staffed crossing point where people and vehicles are identified, inspected, and then admitted, referred to secondary, or refused entry according to their documents and risk.
- Cleanroom or Airlock — A physical staging boundary that lets people and materials enter a controlled space only after gowning, cleaning, and pressure transition strip the contamination they carry.
- Clinical Screening — A pre-entry assessment that sorts people by symptom, risk, or eligibility so each is admitted to the right care pathway, deferred, or safely referred elsewhere.
- Content Moderation Gate — A platform boundary that reviews user-generated content and allows, removes, labels, or downranks it by safety, legality, and community rules — with a path to appeal.
- Customs Process — An institutional apparatus that classifies goods crossing a jurisdictional boundary, assesses duty, and decides seizure or release — leaving a documentary record for every consignment.
- Data Import Validator — A gate on data entering a system that checks each record against a schema and rules, then coerces what it can safely fix and rejects or dead-letters what it cannot.
- Data Loss Prevention — An egress control that watches data leaving an organization and blocks, encrypts, or logs any movement of sensitive material that isn't authorized.
- Firewall — A rule-based gate on network traffic that permits or blocks each connection by matching it against an ordered policy of source, destination, port, and behavior.
- Intake Filter — A front-door screen that sorts incoming requests, cases, or applications and routes each to the right queue, defers it, or redirects it before it consumes a service's capacity.
- Quarantine Process — A holding buffer that separates uncertain or risky crossing objects for a defined period until they are tested, cleared, treated, expired, or rejected.
- Semipermeable Membrane — A material boundary that admits selected substances by their physical properties alone — no inspector, no decision, just a structure whose geometry lets some things pass and blocks the rest.
- Circulation Loop Design: Create or tune circulation loops so resources, information, heat, attention, or capability are redistributed rather than stagnating.▸ Mechanisms (10)
- Air or Water Circulation System — Moves a physical medium — air, water, or heat — along an engineered path driven by a pressure or temperature gradient, so it refreshes stale or overheated regions instead of pooling.
- Capital Circulation Pool — Recycles recovered funds back into a shared pool under return and eligibility rules, so capital is redeployed to new needs instead of being spent once and gone.
- Cross-Team Rotation — Moves people or review duty across team boundaries with explicit handoffs and receiver-capacity checks, so context and load spread between silos rather than pooling in one team.
- Information Circulation Routine — Turns recurring briefings into a loop that carries information back to stale or underinformed zones and returns it to the decisions it should update — not just broadcasts it outward.
- Inventory Rotation — Moves stock through storage and use in a freshness-ordered sequence, gated on quality and paced to demand, so items are consumed before they expire or go idle.
- Knowledge Rotation — Circulates lessons, examples, and expertise through translation points so know-how is reused in new contexts rather than stranded where it was first learned.
- Recirculating Review Loop — Sends documents or cases back through reviewers until explicit quality and closure criteria are met, with monitoring to stop the loop before it becomes endless rework.
- Returnable Container Loop — Runs reusable containers on a closed loop — out to use sites and back through inspection and redeployment — with loss accounting so the fleet circulates instead of leaking away.
- Round-Robin Assignment — Cycles incoming tasks through receivers in turn, subject to capacity skips and priority overrides, so work spreads evenly instead of piling on whoever is nearest or fastest.
- Staff Rotation — Cycles people through roles or sites on a set cadence, with handoffs and monitoring, so capability and burden spread instead of concentrating in a few incumbents.
- Conserved Reservoir-Flux Balancing: Name the reservoirs, name the conserved fluxes between them, and close the balance so interventions change the whole stock-flow network rather than merely moving imbalance out of sight.▸ Mechanisms (14)
- Capacity Headroom Alert — Watches each reservoir's level against its capacity and fires before the headroom runs out, turning a slow fill or drain into a warning with lead time to act.
- Compartment Model — Abstracts a system into a few well-bounded compartments linked by transfer rates, so accumulation and turnover follow from residence times instead of being watched flow by flow.
- Data Lineage Balance Check — Asserts that every step of a data pipeline conserves its records and totals — what enters equals what leaves plus what was intentionally dropped — and flags any hop where the count silently breaks.
- Flow Gate or Valve Rule — A control rule that opens, throttles, or closes a flux channel on a defined trigger, steering the network's balance by adjusting flows in real time rather than cleaning up after.
- Inventory Reconciliation Workflow — A recurring workflow that brings recorded stock back into agreement with a physical count, assigns each discrepancy a cause and an owner, and closes the books on a set cadence.
- Loss-Sink Audit — Hunts the gap between what should be in the system and what is, tracing the missing quantity to the leak or unmonitored sink absorbing it — and to whoever quietly bears the loss.
- Mass-Balance Table — Lays every measured inflow and outflow of a conserved quantity into one ledger so inputs minus outputs must equal the change in stock — and any residual is flagged, not buried.
- Material Flow Analysis — Traces a conserved substance across a defined system — inputs, stocks, transfers, and outputs — so every unit is accounted for from source to sink.
- Reservoir Balance Dashboard — Puts the current level, headroom, and net flow of every reservoir on one live display, so drift and an impending fill-or-drain are seen while there is still time to act.
- Sankey Flow Map — Draws the whole flow network as ribbons whose width is proportional to quantity, so you see at a glance where a conserved flow concentrates, splits, and disappears.
- Stock-and-Flow Diagram — Draws the conserved quantity as stocks (accumulations) connected by flows (rates), exposing the reservoir-and-pipe structure — and the feedback loops — behind a flow problem.
- System Dynamics Simulation — Turns a stock-and-flow structure into equations and runs it forward in time, so you can watch reservoirs fill, drain, and oscillate under a policy before trying it for real.
- Unit Conversion Crosswalk — A shared table of equivalences that converts every flow and stock into one common unit, so quantities measured differently can actually be added, balanced, and compared.
- Water or Resource Budget — Balances a specific resource over a defined boundary and period — sources in versus uses and losses out, against available storage — to see whether the account closes and whether it is over-committed.
- Controlled Stress Relief: Release accumulated tension in a controlled way before it ruptures destructively.▸ Mechanisms (9)
- Conflict Mediation — A neutral third party helps two parties in an active dispute discharge accumulated tension face-to-face, at a paced tempo, and rebuild a working relationship.
- Controlled Burn — A deliberately ignited, bounded fire that consumes accumulated fuel under chosen conditions so a landscape cannot later feed a catastrophic wildfire.
- Debt Restructuring — A negotiated rewrite of the timing, size, and priority of claims that releases mounting payment pressure before it forces a disorderly default.
- Deload Period — A pre-scheduled, dosed reduction in training or work intensity, written into the cycle in advance to bleed off accumulating strain before it becomes injury or burnout.
- Grievance Channel — A standing, accountable route through which one person can send a complaint into the institution — and trust it will be handled without reprisal — before pressure turns into exit or revolt.
- Maintenance Shutdown — A deliberate halt of a machine, line, or plant so accumulated wear, backlog, and error pressure can be actively repaired and renewed before it forces an unplanned failure.
- Pressure Relief Valve — A self-actuating mechanical device that opens a fixed outlet at a precise set pressure and reseats when the danger passes, needing no operator.
- Rest/Recovery Period — A protected interval of genuine non-work that lets an accumulated fatigue reservoir drain through the body's own recovery, restoring capacity before strain becomes injury or breakdown.
- Spillway Release Protocol — An operator-run procedure that meters reservoir discharge ahead of an unsafe level, pacing the release to what the channel below can safely absorb.
- Counterflow Gradient Preservation: Arrange two coupled streams to move in opposite directions along a shared interface so a useful local difference persists across the whole contact and cumulative exchange can approach its feasible maximum.▸ Mechanisms (12)
- Anti-Bypass Distributor and Baffle Set — Installed internals — distributors, redistributors, and baffles — that force both streams onto their intended opposed paths, spread each evenly across the full cross-section, and block the short-circuits and back-mixing that flatten the gradient.
- Capacity-Rate Balancing Control — Continuously trims the two streams' flow rates so their capacity rates stay matched, holding the local driving difference even from end to end as load varies.
- Clean-in-Place Interface Maintenance — Restores the exchange interface's conductance by circulating cleaning agents through the device in place, on a cadence driven by a fouling monitor, using a safe isolate-and-bypass path.
- Countercurrent Extraction Column — Contacts two immiscible liquids in continuous counterflow so a solute transfers selectively from one phase into the other while the concentration difference stays useful over the whole column height.
- Countercurrent Gas-Exchange Surface — Sweeps a respiratory medium past blood or fluid in the opposite direction across a gas-permeable surface so the partial-pressure difference persists the whole way and extraction can approach near-complete.
- Countercurrent Washing or Leaching Train — Cascades solids and wash liquid through a train of stages flowing in opposite directions so fresh liquid always meets the most-depleted solids, driving residual solute toward target with the least liquid.
- Counterflow Dialysis Circuit — Runs blood and dialysate in opposite directions across a semipermeable membrane so the concentration gradient for waste solutes persists the whole length while the two fluids stay strictly separate.
- Counterflow Heat Exchanger — Runs hot and cold streams in opposite directions across a conducting wall so a useful temperature difference persists end to end and the cold outlet can approach the hot inlet.
- Counterflow Membrane Module — Packages a selective membrane with feed and sweep flowing counter to each other so the transmembrane driving force stays high along the whole module and separation approaches its permeance-and-selectivity limit.
- Flow-Distribution Tracer Test — Injects a pulse of tracer and watches when it emerges to reveal how evenly a contactor's flow is distributed — exposing the bypass, channeling, and backmixing that quietly destroy a counterflow profile.
- Gradient and Flux Map — Lays out, for a coupled pair or a whole network, what quantity wants to move and which way, and where along the contact the useful driving difference is strong, collapsed, leaking, or spuriously amplified.
- Pinch Analysis and Heat Integration — Stacks all the hot and cold streams of a whole system into composite curves, reads off the pinch to fix a provable maximum-recovery target, and trades the minimum approach against area and cost.
- Countersettling Transfer Orientation: Orient useful transfer against the natural drift of an unwanted companion so the payload advances to the destination while the rejected fraction trails away.
- Displacement-Aware Capacity Admission: Before admitting or expanding one activity in a finite shared substrate, identify what it will displace and protect, resize, phase, offset, relocate, or reject the expansion accordingly.▸ Mechanisms (9)
- Capacity Reservation Rule — A rule that reserves part of the shared substrate for incumbent, public-good, safety, ecological, or vulnerable uses.
- Crowding-Out Monitoring Dashboard — A dashboard tracking substrate utilization, entrant growth, incumbent shrinkage, protected-floor violations, and mitigation status.
- Displacement Impact Assessment — A pre-admission assessment estimating which incumbent uses will shrink when a new activity consumes shared substrate.
- Incumbent Use Register — A register of existing formal and informal uses of a shared substrate, including protected functions and dependency strength.
- Moratorium and Reversal Gate — A stop rule that pauses or reverses expansion when observed displacement crosses protected thresholds.
- Offset or Relocation Plan — A plan for relocating displaced activity, expanding substrate, compensating affected parties, or substituting alternate capacity.
- Phased Admission Trial — A staged rollout of the entrant with measurement gates, rollback authority, and incumbent impact review.
- Shadow Displacement Accounting — A counterfactual accounting method that estimates what incumbent activity would have remained without the entrant.
- Substrate Capacity Budget — A budget stating total shared capacity, reserved floors, discretionary slack, phase-in allowance, and emergency reserve.
- Donor-Coupled Capacity Governance: When a recipient appears viable because a donor/source continuously sustains it across a boundary, make the subsidy explicit, test real capacity, and choose continuation, formalization, transition, or withdrawal safeguards.▸ Mechanisms (9)
- Capacity Milestone Agreement — Defines the recipient capabilities and evidence required before support changes or autonomy claims are accepted.
- Cross-Boundary Support Agreement — Formalizes rights, obligations, data sharing, support levels, review cadence, and exit/continuation rules.
- Donor Stress Test — Examines whether the donor can maintain the subsidy under shocks without degrading its own critical functions.
- Source-Sink Monitoring Dashboard — Tracks donor flow, recipient baseline, support share, donor stress, and autonomy-claim status over time.
- Subsidy Dependency Assessment — Assesses how much of recipient performance depends on donor flow and which functions would fail without it.
- Subsidy Ledger — Maintains a visible record of support flows, costs, beneficiaries, duration, and governance terms.
- Support Load Quota — Caps donor obligation or hidden subsidy share until support is diversified, repriced, or capacity is increased.
- Taper and Handoff Plan — Coordinates staged reduction, localization, substitution, or formalization of support with contingency buffers.
- Withdrawal Rebound Drill — Simulates or rehearses support loss to reveal rebound failure paths and needed buffers.
- Dose–Exposure–Response Trajectory Modeling: Model the time-varying path from input to internal exposure to observed response so intervention intensity can be predicted, individualized, and kept inside a usable operating window.▸ Mechanisms (9)
- Bayesian Dose Forecasting — A forecasting method that updates exposure-response predictions as new observations arrive.
- Compartmental PK/PD Model — A model that represents exposure as movement through one or more compartments before linking exposure to response.
- Effect-Compartment Lag Model — Inserts a hypothetical effect-site compartment so measured exposure and observed response can be separated by a modeled time lag.
- Exposure–Response Simulation — Runs candidate input regimens forward through the coupled exposure-response model to project their trajectories against the target window before any is tried live.
- Physiologically Based Exposure–Response Model — A mechanism-grounded model that uses explicit pathways or compartments to support exposure-response prediction and extrapolation.
- Policy Exposure–Response Sandbox — A what-if environment for testing how policy intensity and communication cadence translate into compliance, fatigue, and backlash before rollout.
- Population PK/PD Covariate Model — Represents systematic between-subject variability by tying model parameters to covariates, yielding population priors that individualize before any measurement.
- Therapeutic Drug Monitoring Model — A clinical measure-and-adjust protocol that compares observed drug levels against a target window and corrects the dose while a safety override guards the boundary.
- Training Load Response Forecast — Forecasts how training workload accumulates into fatigue and fitness before it shows up as performance or injury risk.
- Duration-Matched Commitment Design: Do not fund short-clock promises with only long-clock resources unless rollover loss, liquid coverage, and rebalancing paths are already designed.▸ Mechanisms (10)
- Asset-Liability Matching Policy — Requires long-duration commitments to be funded by sufficiently stable sources or paired with liquid coverage and contingency paths.
- Committed Backup Facility — Provides prearranged liquidity, capacity, staffing, inventory, or service access that can activate when normal refresh fails.
- Contingency Funding Playbook — Predefines the order, authority, communications, and tradeoffs for activating backup liquidity or shortening the long side during stress.
- Duration Gap Dashboard — Shows current and stressed duration gaps, rollover concentrations, coverage floors, and breach triggers.
- Liquidity Coverage Floor Metric — Tracks whether immediate and near-term liquid capacity covers modeled outflows over the chosen stress horizon.
- Maturity Ladder Analysis — Constructs the calendar of obligations, renewals, resource releases, conversion windows, and gap periods.
- Notice-Period or Lock-Up Alignment — Aligns withdrawal rights, cancellation terms, supplier replenishment terms, staffing commitments, or customer promises with the time needed to release resources safely.
- Rollover-Failure Stress Test — Tests survival if short-side funding, replenishment, renewals, or customer confidence cannot be refreshed on schedule.
- Staggered Maturity Refinancing Schedule — Spreads maturities and renewal windows so obligations do not cluster at one fragile rollover point.
- Triggered Maturity-Rebalancing Clause — Uses covenant, contract, governance, or operating triggers to lengthen short obligations, reduce long lockup, or throttle new commitments when mismatch exceeds limits.
- Effective-Input Delivery Assurance: Manage what becomes usable at the point of action, not merely what was supplied upstream.▸ Mechanisms (14)
- Advection-Diffusion or Transport Modeling — Predicts how much of an input reaches the target — and how much washes out or piles up along the way — by modeling its advective and diffusive transport through the delivery path.
- Availability Funnel Dashboard — Shows supply narrowing stage by stage into the fraction actually usable at the point of action, and tracks the response and off-target signals it produces over time.
- Dosage Window Protocol — Sets a standing acceptable range for a managed input — a floor for effect and a ceiling for harm — with codified rules for correcting back into it.
- Exposure Dose Curve — Maps how response changes across the full range of an input — from no effect, through the useful zone, to diminishing returns and harm — so any single level can be read off the curve.
- First-Pass Loss Audit — Isolates and books the loss at the first boundary the input must cross — the earliest, largest, most easily hidden drop, before any downstream stage can even see it.
- Mass Balance — Applies conservation bookkeeping across a declared boundary so a hazard that 'disappears' from one channel must reappear as an outflow somewhere — and the unaccounted gap localises the leak.
- Medication Dose Calibration — Dials an individual's dose to their own observed response and adverse signals, titrating under professional oversight until the effect lands in target without tipping into harm.
- Minimum Effective Dose Review — Periodically re-examines a standing input to find the lowest level that still works, deliberately shedding dose to reduce off-target burden without losing the effect.
- Route–Form–Timing Optimization — Raises the fraction that arrives usable by changing how the input is delivered — its route, its form, and its timing — instead of increasing the amount supplied.
- Sankey Loss Map — A flow diagram whose branch widths are drawn to scale, exposing where a supplied input is lost stage by stage and what fraction survives to do useful work.
- Stagewise Availability Assay — Measures how much of the input remains in usable form at each stage of the path, turning one supplied figure into a stagewise availability profile with error bars.
- Tagged Input Tracing — Attaches a distinguishable tag to a batch of the input and follows that same material through the system, mapping where it actually goes — and where it leaks or is diverted.
- Target-Site Sampling or Proxy Validation — Measures what is actually present at the point of action — by sampling the target directly, or by validating an accessible proxy that provably tracks it.
- Uptake Confirmation — Verifies that a supplied input actually arrived and was taken up in usable form at the point of action, rather than trusting that dispatch equals receipt.
- Endpoint Fan-Out Fulfillment: Design the deconsolidation, local staging, routing, service-mode, access, evidence, and recovery layer that turns efficient trunk flow into verified endpoint completion.▸ Mechanisms (21)
- Address or Endpoint Validation — Checks each endpoint's identity, location, eligibility, connectivity, and access prerequisites before anything is dispatched, so effort is only spent on endpoints that can actually be served.
- Community Access Point — Stands up a trusted local place — staffed with people who know the community — where endpoints can get assisted pickup, connectivity, identity help, or translation to complete a service they couldn't finish alone.
- Demand Aggregation Window — Briefly holds compatible low-density requests until enough accumulate to serve them together as one efficient cluster, instead of dispatching each sparse request on its own.
- Dynamic Route Optimization — Continuously recomputes routes and assignments from live demand, capacity, traffic, priority, and failure signals, so the fan-out adapts to conditions on the ground instead of following a fixed plan.
- Endpoint Completion Dashboard — Puts verified endpoint completion — not trunk throughput or dispatch — at the center of the view, exposing the gap between what was sent and what actually arrived, sliced by segment.
- Endpoint Cost-to-Serve Analysis — Estimates the full cost of successfully completing service at each class of endpoint — including the last-mile share that trunk-level accounting hides — so the true economics of the edge become visible.
- Exception Queue — Pulls the endpoint cases that don't fit the standard flow into a dedicated queue with its own capacity and clock, so the main line keeps moving and the oddballs still get resolved.
- Failed-Attempt Recovery Workflow — Turns a failed endpoint attempt into a classified, routed recovery — diagnosing why it failed and sending it to correction, an alternate mode, a reschedule, or escalation — so one miss doesn't become a permanent non-completion.
- Geospatial Service-Area Mapping — Turns endpoint locations, travel times, terrain barriers, and service deserts into one spatial picture that shows where the fan-out is hard and where local staging could sit.
- Local Dispatch or Field Team — Standing local operational capacity — people who know the ground — assigned to work the last leg, clear on-site obstacles, and close the exceptions no ticket can specify.
- Local Inventory or Edge Cache — A forward-placed buffer of the frequently-needed goods, data, or capability held close to endpoints, so the common request is served locally — fast, and still served when the trunk is slow or down.
- Local Partner or Agent Network — Delegates endpoint completion to trained third-party local actors under an explicit contract that defines what 'done' means and where the system's responsibility hands off to theirs.
- Long-Tail Support Tier — Runs a deliberately lower-volume but still reliable service mode for niche users, rare configurations, and low-frequency needs the mainstream offering drops.
- Micro-Hub or Pickup-Point Network — Local nodes where consolidated trunk flow is broken down and staged for short final legs or self-collection — relocating the handoff off the doorstep to a dense, efficient point.
- Mobile Service Unit — A self-contained unit that travels to sparse or hard-to-reach endpoint clusters, bringing the goods, equipment, or expertise to recipients instead of requiring them to come to a fixed point.
- Multimodal Delivery Switching — Maintains a portfolio of delivery modes and moves an endpoint from one to another — home, pickup, mobile, partner, assisted, remote — when its conditions, cost, or repeated failures change which mode fits.
- Proof-of-Completion Capture — Captures just enough verifiable evidence that an endpoint was actually served — a signature, photo, scan, or confirmation — proportionate to the stakes, so completion is provable without over-collecting.
- Route Clustering and Territory Design — Groups scattered endpoints into service clusters and territories that lift route density and balance workload, while protecting latency limits, capacity, equity, and the sparse tail that clustering tends to strand.
- Scheduled Service Window — Carves out protected, recurring time to repair, patch, replace, and clean up endpoints so upkeep never has to fight live demand for the same capacity.
- Targeted Outreach Campaign — Goes out and finds the specific endpoints that are stuck — missing information, blocked by an access barrier — and proactively removes the blocker so they can complete, instead of waiting for them to come to the system.
- Transparent Cross-Subsidy Schedule — An explicit, reviewable rule that funds high-cost or essential endpoints out of pooled system revenue, making the who-pays-for-whom of universal service visible instead of hidden.
- Equilibrium-Aware Capacity Intervention Design: Before adding an attractive path or capacity option to a self-optimizing network, test the equilibrium response and add pricing, routing, metering, access, or rollback controls so local choices do not make the whole system worse.▸ Mechanisms (9)
- Braess Paradox Scenario Test — A scenario test that asks whether an apparent capacity gain creates a worse equilibrium.
- Capacity Closure or Reversal Review — A workflow for reversing or constraining a capacity addition that causes systemic harm.
- Congestion Pricing or Toll Rule — A pricing rule that changes path payoffs to reduce selfish-routing externalities.
- Incentive-Compatible Routing Guidance — A guidance tool that makes individually attractive routes less harmful to the network.
- Paradox Risk Dashboard — A dashboard that shows whether the new capacity is improving local and aggregate outcomes.
- Route Access Metering Policy — A protocol that throttles or conditions access to a capacity option.
- Staged Capacity Pilot — A reversible rollout procedure for capacity additions in self-optimizing networks.
- Traffic Assignment or Flow Equilibrium Model — A model that compares decentralized path choice with coordinated network performance under capacity scenarios.
- User Equilibrium vs System Optimum Analysis — A method for measuring whether local choice incentives diverge from whole-network performance.
- Fast/Slow Path Routing: Route routine cases through a cheap, safe fast path while sending exceptional, ambiguous, risky, or high-value cases to a deliberately resourced slow path.▸ Mechanisms (9)
- Automated Pre-Screen with Manual Review — A workflow that uses cheap automated checks before routing flagged cases to human or specialist review.
- Cache with Authoritative Fallback — A system that serves common requests from a fast cache and routes misses or conflicts to an authoritative source.
- Confidence Threshold Router — A score- or uncertainty-based router that escalates low-confidence or high-risk cases.
- Deoptimization or Fallback Handler — A fallback routine that sends optimized fast-path execution back to a more general slower handler when assumptions fail.
- Escalation Playbook — Specifies who is notified, what decisions are opened, and what actions become available when a signal crosses an escalation boundary.
- Exception Queue Dashboard — A dashboard that tracks slow-path volume, age, causes, outcomes, and recurrence.
- Fast-Track Lane with Audit — A low-friction lane for eligible cases paired with sampling, appeal, and outcome review.
- Happy-Path / Exception Workflow — A process design that defines a streamlined normal route and an explicit exception route.
- Triage Rule Table — A documented set of routing criteria for sending cases to fast path, slow path, audit, pause, or return.
- Flow Channelization: Confine diffuse or chaotic flow into defined channels so it can be directed, measured, protected, or governed.▸ Mechanisms (10)
- Channel Monitoring Dashboard — Puts a channel's health — volume, load against capacity, and leakage — on one live surface, so overload is seen and acted on rather than discovered at failure.
- Controlled Corridor — Holds open one protected, admission-controlled passage between the closing zone and the destination, and keeps proving it is passable end to end while the space around it constricts.
- Data Conduit — Moves information through one defined stream that validates what enters and confirms what is delivered, replacing untracked point-to-point scripts with a governed, observable path.
- Drainage Channel — Confines diffuse runoff inside bounded banks and directs it along a rated path to a safe discharge, so it flows where intended instead of spreading into vulnerable ground.
- Intake Queue — Holds admitted work in an ordered, priority-ranked line with explicit rules for who advances, who may legitimately jump, and what 'done' means, so nothing waits invisibly or forever.
- Overflow Lane or Spillway — A normally-dormant surge path that opens only when the primary channel exceeds its capacity, carrying the excess along a planned route instead of letting it back up or spill.
- Service Channel Portal — One official front door that consolidates scattered requests behind a single governed intake, with defined submission requirements and an accessible alternate for those the standard path would exclude.
- Ticketing System — Turns each incoming request into a durable, owned, trackable record that moves through states from open to resolved, so nothing is lost and everyone can see where it stands.
- Traffic Lane — Separates incompatible flow classes into their own bounded routes, admitting only eligible traffic and granting priority classes a dedicated lane, so faster and slower movement stop colliding.
- Workflow Swimlane — A design diagram that assigns each strand of work to its own responsibility lane and exposes exactly where flow crosses a boundary or leaks between owners.
- Gradient-Guided Intervention: Use a gradient of stress, value, risk, need, or opportunity to decide where intervention should move, intensify, taper, or concentrate.▸ Mechanisms (9)
- Gradient Descent or Ascent Search — Reads the local slope of an objective surface and takes a step in the improving direction, repeating until the ground goes flat, to walk toward a better point without mapping the whole field.
- Heat Map — Renders a field's uneven intensity as a color-graded surface, so that where a variable runs hot or cold becomes legible at a glance.
- Hotspot Response Plan — Concentrates a surge of action in the spatial, temporal, or network regions where incidents cluster, with built-in guardrails against displacing the problem or over-burdening the place.
- Opportunity Scoring Model — Estimates, for every case in a field at once, the expected marginal benefit of acting on it, producing a comparable score so effort flows to where the upside is greatest.
- Risk-Band Treatment Matrix — Cuts a continuous gradient into a small set of named bands and assigns each band a fixed, predefined treatment, turning a slope into a lookup table anyone can apply.
- Risk-Based Inspection Schedule — Sets how often each asset is inspected in proportion to its failure risk, so high-risk items are checked frequently while a regulatory floor keeps low-risk ones from vanishing entirely.
- Sentinel Indicator Dashboard — Tracks a small set of leading indicators that reveal where a gradient is moving before lagging outcomes confirm it, so attention arrives ahead of the problem.
- Targeted Outreach Campaign — Goes out and finds the specific endpoints that are stuck — missing information, blocked by an access barrier — and proactively removes the blocker so they can complete, instead of waiting for them to come to the system.
- Triaged Maintenance Route — Orders a crew's work into a ranked route through a fleet of assets by failure risk and consequence, so the highest-stakes items are reached first within the cycle's capacity.
- Handoff Standardization: Standardize transitions between stages or actors so flow does not lose context, quality, state, or accountability at handoff points.▸ Mechanisms (9)
- Case Transfer Dossier — Bundles a continuing matter's history, obligations, deadlines, and next actions into one package so a new owner can carry it forward without reconstructing it.
- Chain-of-Custody Form — Records an unbroken, signed sequence of who held an item, when, and with what integrity check, so the transfer chain itself can be proven later.
- Deployment Release Handoff — Transfers a shipped software release from the team that built it to the team that will operate it, under an explicit contract of rollback, monitoring, and on-call ownership.
- Handoff Note Template — A reusable fixed-field form the sender fills at every handoff, so the same critical items are captured in the same shape every time.
- Incident Escalation Note — Packages a live incident's severity, timeline, attempted fixes, and current hypotheses with a specific ask, so a higher tier can take over the decision without re-triaging.
- Manufacturing Station Handoff — Passes a part and its state to the next workstation only after an inline check confirms the station's work is complete and within spec.
- Shift-Change Briefing — A scheduled, face-to-face turnover where outgoing and incoming crews talk through live state and confirm understanding by read-back before responsibility changes hands.
- Structured Handoff Checklist — A prompt list both parties run at handoff to confirm every must-transfer item was actually covered before the transfer is signed off.
- Support Ticket Escalation — Moves a support case across a queue or tier boundary to a better-equipped owner while carrying its context, with defined paths to reroute or bounce back a mis-sent case.
- Intermediate-State Throughput Control: Treat a named transient state as a controllable intervention surface: regulate how fast it forms, how long it persists, how its quality changes, and how reliably it converts into the desired next state.▸ Mechanisms (12)
- Batch Size Tuning — Sets how many items are grouped before they move to the next stage, trading per-item overhead against the residence time and pile-up that large batches create.
- Conversion Capacity Boost — Raises the throughput of the stage that converts the intermediate into the next state, so a growing in-process pool is drained rather than throttled at the source.
- Formation Throttle — Regulates how fast the intermediate is created, applying backpressure at the source so it forms no faster than the next stage can consume it.
- Holding Condition Control — Maintains the conditions under which the intermediate is held so its quality decays as slowly as possible during the time it must wait.
- Intermediate State Tagging — Attaches a machine-readable label to each in-process item recording which intermediate state it is in and since when, turning an invisible middle into something you can see and query.
- Priority by Age or Risk — Orders which in-process items are converted next by their age or their risk, so the oldest or most dangerous intermediates don't linger while newer, safer ones jump ahead.
- Quench or Stabilization Step — Deliberately arrests the intermediate's tendency to degrade or react further — freezing it into a stable, hold-able form — so its quality and hazard stop being a function of time.
- Residence-Time Dashboard — Makes the invisible dwell time of in-process items visible, tracking how long each has sat in a state against an acceptable residence-time window so aging is caught before it becomes failure.
- Side-Path Suppression — Raises the fraction of the intermediate that exits down the desired branch by blocking the competing side-paths that leak, divert, or spoil it.
- Stage Handoff Check — Gates each transfer between stages, verifying the in-process item meets the next stage's entry criteria and routing it forward or back for rework at the boundary.
- Stale Item Sweep — Periodically finds in-process items that have aged past usefulness and routes them out of the state via a defined disposition path, so stale work stops occupying and contaminating the pipeline.
- WIP Limit by Intermediate State — Caps how many items may occupy a named in-process state at once, so the ceiling itself becomes a backpressure valve that forces inflow to match outflow.
- Leakage Path Containment and Recapture: Prevent constrained resources, information, risks, contaminants, funds, or obligations from escaping through unintended paths by making leakage paths visible, bounded, sealed, and recoverable.▸ Mechanisms (12)
- Anomaly or Shrinkage Alert — Watches a loss signal against a threshold and fires the instant measured leakage deviates from expected, routing the alarm to whoever owns the path.
- Canary Token or Tracer Dye — Embeds a distinctive, trackable marker in the protected quantity so that any escape reveals itself — and reveals which path it took and where it surfaced.
- Controlled Release Valve — Gives a quantity under pressure a single sanctioned, rate-limited outlet — so the excess escapes through a channel you designed and can recover from, instead of finding its own unintended path.
- Exception Log Review — Periodically re-opens the standing log of granted exceptions and overrides to the containment rules, so bypasses that quietly became permanent leaks are re-decided, re-owned, or revoked.
- Leakage Budget Dashboard — Tracks cumulative loss against an explicitly allowed residual budget and shows the open repair backlog — turning 'are we leaking too much?' into a running balance with a limit.
- Leakage Path Walkthrough — Walks the actual boundary of a container end to end, with the people who operate it, to name every path a constrained quantity can escape through — before any of them starts losing.
- Mass-Balance Audit — Reconciles what entered, what legitimately left, and what remains across a bounded control volume, attributing the unexplained gap to leakage.
- Post-Seal Displacement Check — After a leak is sealed, verifies that total loss actually fell rather than merely relocating to the next-easiest path.
- Recapture or Recall Protocol — A standing procedure for retrieving or neutralizing a quantity that has already escaped, by tracing where it went and pulling it back through assigned owners.
- Red-Team Exfiltration Probe — A sanctioned adversary actively tries to smuggle the constrained quantity past the controls, discovering exploitable leak paths by attacking rather than surveying.
- Seal-and-Retune Patch — Closes an identified leak path and re-tunes the surrounding controls so the fix holds and residual loss lands within budget, working the repair off a prioritized backlog.
- Side-Channel Scan — Systematically sweeps for covert, unintended paths through which the quantity bleeds out indirectly — the routes the boundary model never listed.
- Network Flow Optimization: Route flow through a capacity-constrained network to maximize throughput, minimize cost, or avoid bottlenecks.▸ Mechanisms (8)
- Data Network Routing Policy — A standing rule set that steers packets, requests, and jobs across regions, links, and servers by class, compliance, and failover — deciding routes live as conditions change rather than solving one optimum.
- Logistics Routing Plan — The standing plan that decides which front the reserve flows to first and in what feasible sequence, encoding an explicit front-priority ranking against a map of the network's capacities and constraints.
- Max-Flow Analysis — Computes the greatest volume that can move from source to sink under edge capacities, and names the min-cut — the saturated links whose combined limit sets the ceiling.
- Min-Cost Flow Model — Routes a required flow from supplies to demands at least total cost, choosing the cheapest feasible allocation over a capacitated network subject to conservation.
- Multi-Commodity Flow Model — Represents several distinct flow classes over one shared network — each with its own sources and sinks — coupled only where they compete for the same edge capacity.
- Network Capacity Dashboard — A live topological view of a flow network that shows where capacity is saturated, where it sits idle, and where the binding bottleneck has moved.
- Patient Flow Pathway Review — A structured multidisciplinary walk-through of the care pathway that traces where patients stall, showing that an upstream jam is usually a downstream sink constraint — and reallocates flow while protecting safety and dignity.
- Traffic Assignment Model — Predicts how trips spread across a road or transit network by modeling travelers who each choose their own fastest route, until no one can gain by switching — a user equilibrium.
- Pipeline Staging: Divide a complex flow into ordered stages so each stage can specialize, coordinate handoffs, and preserve throughput, quality, and accountability.▸ Mechanisms (8)
- Assembly Line Workflow — Implements pipeline staging by arranging repeated physical or service transformations into specialized stations with defined movement between them.
- CI/CD Pipeline — Implements pipeline staging in software delivery by moving changes through build, test, review, deployment, and release stages with automated handoffs.
- Clinical Care Pathway — Implements pipeline staging in care delivery by sequencing intake, triage, diagnosis, treatment, monitoring, discharge, and follow-up while preserving patient state.
- Editorial Workflow — Implements pipeline staging for text or media by separating drafting, editing, fact-checking, approval, production, and publication responsibilities.
- ETL or Data Processing Pipeline — Implements pipeline staging for data by moving records through extraction, validation, cleansing, enrichment, and loading stages while quarantining records that fail and preserving lineage.
- Legal Procedure Sequence — Implements pipeline staging by ordering filings, disclosures, hearings, judgments, and appeals so process rights and evidentiary state are preserved.
- Onboarding Workflow — Implements pipeline staging by sequencing orientation, account setup, training, practice, verification, and handoff into regular participation.
- Research Review Pipeline — Implements pipeline staging by moving proposals, manuscripts, or evidence through screening, review, revision, decision, and archival stages.
- Reversible In-Flow Phase-Separation Measurement: Temporarily separate a flowing mixture into measurable phase paths, observe the cleared phases, and recombine them without stopping the main process.
- Service Rate Matching: Adjust service capacity, cadence, or throughput to match arrival patterns so queues remain stable rather than growing into unmanaged delay.▸ Mechanisms (10)
- Autoscaling Worker Pool — Keeps a pool of interchangeable workers sized to live demand — adding capacity as requests surge and releasing it as they ebb — so the service tracks load instead of over- or under-provisioning.
- Batch Size Tuning — Sets how many items are grouped before they move to the next stage, trading per-item overhead against the residence time and pile-up that large batches create.
- Cross-Trained Surge Pool — The pool must be trained enough to protect quality. Otherwise it shortens the queue by creating rework or unsafe variation.
- Dynamic Capacity Allocation — This can drift into Load Balancing if the primary act is routing work to equivalent capacity. It fits Service Rate Matching when resource level or cadence changes to stabilize a queue.
- Parallel Server Activation — Runs many interchangeable copies of the capability in parallel so requests are served concurrently — which requires pushing session state out of the instances so any copy can serve any request.
- Peak-Mode Service Protocol — This mechanism can be effective in emergencies and seasonal peaks, but it must not quietly normalize degraded service as ordinary operation.
- Processing Cadence Change — Useful when the service bottleneck is a recurring review, approval, pickup, dispatch, clinic, or batch operation.
- Queue-Based Feedback Controller — The controller is a mechanism; the archetype is the broader governance pattern that defines what is measured, what can change, and what invariants must be preserved.
- Service Window Adjustment — May overlap with scheduling or demand smoothing. It belongs here when the service side moves to meet arrivals, not when demand is primarily pushed elsewhere.
- Staffing to Demand — Works when labor is the binding service resource and enough lead time exists to change rosters, assignments, on-call activation, or cross-coverage.
- Source–Sink Viability Management: Manage asymmetric support networks by protecting sources, diagnosing sink dependency, and deciding when to sustain, restore, transform, or exit sinks.▸ Mechanisms (13)
- Connectivity or Corridor Plan — Designs and protects the actual pathways along which a source's surplus can reach a sink, and deliberately keeps more than one route open, so rescue can happen without leaving the sink hostage to a single link.
- Cross-Subsidy Budget — Makes the transfer from source to sink an explicit line item — how much surplus each source can spare after protecting itself, where it goes, and whether the resulting subsidy is fair — so support is a decision, not a leak.
- Dispersal or Transfer Tracer — Tags and follows the individuals or units that actually move between patches, turning assumed support flows into a measured map of who really feeds whom and what each patch's true net balance is.
- Metapopulation Model — Runs a network of coupled patches forward from their per-patch birth–death and dispersal rates to forecast whether the whole persists — and which patches are true sources versus occupied-but-doomed sinks.
- Minimum Support Schedule — Sets the smallest reliable support a sink needs to stay just above its viability threshold, delivered on a fixed cadence and adjusted by rule as conditions change — sparing the source without letting the sink slip under.
- Rescue-Effect Audit — Periodically tests whether a sink's apparent health is genuine local recovery or merely a rescue effect — persistence borrowed from a source — by asking what it would do if the support were removed.
- Restoration Priority Matrix — Ranks dependent sinks by how recoverable they are against how much they are worth keeping, sorting each into restore, convert, sustain, or exit — so scarce surplus goes where it can actually change a unit's fate.
- Role Reclassification Review — A standing review that watches for role-change triggers and, on a set cadence, formally re-labels any unit whose source or sink status has shifted — so the classification the whole system trusts never silently goes stale.
- Sink Dependency Dashboard — Tracks each sink's dependency in real time — how much support it draws, how close it sits to its viability threshold, and which flows it relies on — so hidden fragility and lock-in surface before an interruption exposes them.
- Source Depletion Dashboard — Continuously watches each source's health — how much exportable surplus is left, whether its viability guardrails are being breached, and how it holds up under stress — so stewardship never quietly slides into extraction.
- Source–Sink Patch Map — Lays out every unit as a labelled patch — source, sink, neutral, or contested — coloured by measured net balance, so the asymmetric structure of who is quietly carrying whom becomes visible at a glance.
- Support Flow Agreement — Turns an informal support flow into an explicit compact — stating why the support exists, until when it is promised, and on what fair terms — so a subsidy is a governed decision rather than an accreted habit.
- Support Taper Plan — A staged glide-path for reducing or ending support, paced to the sink's response and bounded by a do-no-harm guardrail, so withdrawal is a controlled landing rather than a cliff.
- Stock–Flow Accumulation Control: Manage buildup or depletion by treating the stock as the integral of net flow, not as another flow rate.▸ Mechanisms (7)
- Accumulation Threshold Alert — Watches an accumulating stock against preset bands and fires a warning the moment the level crosses a floor or ceiling.
- Clearance–Turnover Tuning — Tunes how fast a stock is drained and cycled — its clearance and turnover rates — to hold residence time and throughput where they belong.
- Delay-Compensated Control — Controls a stock whose response lags the lever, acting on where the level is headed rather than where it is now.
- Hidden Accumulation Probe — Hunts for stock that has quietly displaced across a boundary or piled up off the books, explaining a level that the visible flows cannot.
- Net-Flow Lever Adjustment — Steers a stock into its target band by choosing which inflow or outflow lever to move, and by how much, given the current net flow.
- Stock-Level Buffering — Holds a deliberate reserve so a stock can absorb swings in inflow or outflow without breaching its limits.
- Stock–Flow Balance Reconciliation — Closes the books on a stock by reconciling its measured level change against the net of every inflow and outflow, and flags the unexplained residual.
- Visual Flow Guidance: Guide a person's eye, attention, or orientation through a designed path so they encounter elements in the intended sequence.▸ Mechanisms (10)
- Annotation Trail — Lays labels, callouts, and captions along an existing path so each element's meaning is revealed at the moment the reader reaches it — in an order that stays accessible.
- Arrows and Connectors — Adds explicit arrows and connectors on top of a field so the eye is told, in notation, which element leads to which next — and where the path forks.
- Guided Tour Flow — Escorts a person step by step through a route, pausing at each stop, checking they actually followed, and bringing them back on track after any detour.
- Leading Lines — Uses the lines already in a scene — edges, perspective, sightlines, contours — to pull the eye along a continuous route from its entry point to the target, without labelling anything.
- Path Signage — Places fixed signs, floor markings, landmarks, and 'you are here' maps at the decision points of a physical space so people find the route, choose correctly at junctions, and recover when lost.
- Process Diagram Pathing — Lays a process out as a diagram whose numbered nodes and decision points make the intended reading order — branches and loops included — followable at a glance.
- Progressive Disclosure — Guides attention by withholding everything not yet relevant and revealing material in stages, so the path is set as much by what is hidden as by what is shown.
- Scroll Progression Design — Shapes a long vertical surface with sticky anchors and a source-order-aligned rhythm so a scrolling reader stays oriented, can always recover their place, and meets the sequence on any device.
- Slide Sequencing — Orders an explanation as a run of discrete slides that opens on a title and agenda and advances one frame at a time, so an audience follows the intended line of reasoning in step.
- Visual Storytelling Sequence — Chooses the order in which scenes and evidence are met so a narrative arc carries the viewer along the intended interpretive route to a resolved ending.
Also a related prime in 89 archetypes
- Accountable Gatekeeping Design: Design choke-point selection so passage decisions use explicit criteria, bounded discretion, traceable reasons, review paths, and distribution audits rather than opaque gatekeeper preference.
- Adaptive Scheduling: Continuously revise task timing and resource allocation as demand, priority, capacity, or risk changes.
- Backlog Visibility: Make waiting work visible by size, age, priority, ownership, and drain rate so the system can manage reality instead of hidden accumulation.
- Backpressure: Propagate downstream capacity pressure upstream so producers slow before overload accumulates into failure.
- Beneficial-Input Inversion Control: Keep a helpful input below the receiver's assimilation ceiling, and if it crosses, reduce the source, break the bloom, and restore the depleted secondary resource before a worse regime locks in.
- Bottleneck Capacity Shadowing: Identify which constraint most limits the objective and how much value is gained by relaxing it.
- Bounded Backlog: Limit backlog size so waiting work cannot accumulate beyond what the system can safely see, manage, or eventually serve.
- Buffering: Insert bounded temporary holding capacity between producer and consumer to preserve continuity across mismatched rates, bursts, or timing gaps.
- Bulkhead Isolation: Partition shared resources or failure domains into bounded compartments so local failure stays contained instead of spreading through coupling.
- Catalytic Pathway Enablement: Accelerate a permitted but slow recurring transformation by installing a selective facilitator that lowers the pathway barrier, returns ready for reuse, and is governed for capacity, inhibition, regeneration, and side effects.
Notes¶
Overloaded term: paired with flow_state (#76), the
Csikszentmihalyi psychological sense. The two share
only metaphor; the structural concepts are distinct
and cross-referenced in each entry's "What It Is
Not" section.
References¶
[1] Bernoulli, Daniel. Hydrodynamica, sive de viribus et motibus fluidorum commentarii. Strasbourg: Joannis Reinholdi Dulseckeri, 1738. Establishes the principle of energy conservation in fluid flow; the inverse relation of pressure and velocity (Bernoulli's principle, ch. 12). SUPPORTS FACT-100: confirmed by multiple sources that Hydrodynamica (1738) introduced the pressure-velocity relation; the book christened the field 'hydrodynamics.' registry ↩a ↩b
[2] Euler, Leonhard. "Principes généraux du mouvement des fluides." Mémoires de l'Académie des Sciences de Berlin, vol. 11 (1755): 274–315 (presented 1755, published 1757). Derives the momentum (and continuity) equations for inviscid fluid motion — the Euler equations. SUPPORTS FACT-101: confirmed the Euler equations first appeared here as the inviscid momentum/continuity system. registry ↩a ↩b ↩c
[4] Stokes, George Gabriel. "On the Theories of the Internal Friction of Fluids in Motion, and of the Equilibrium and Motion of Elastic Solids." Transactions of the Cambridge Philosophical Society, vol. 8 (1845): 287–319 (read 1845, published 1849). Completes the Navier-Stokes derivation with a rigorous viscous-stress tensor (Newtonian fluid). SUPPORTS FACT-103: confirmed Stokes (1845) gave the rigorous formulation of internal friction in fluids in motion. registry ↩a ↩b
[5] Reynolds, Osborne. "An Experimental Investigation of the Circumstances Which Determine Whether the Motion of Water Shall Be Direct or Sinuous, and of the Law of Resistance in Parallel Channels." Philosophical Transactions of the Royal Society of London, vol. 174 (1883): 935–982. Introduces the dimensionless Reynolds number Re = ρVD/η governing the laminar-to-turbulent transition. SUPPORTS FACT-104: confirmed Reynolds (1883) established the ratio of inertial to viscous forces predicting turbulence onset. registry ↩a ↩b ↩c
[6] Helmholtz, Hermann von. "Über Integrale der hydrodynamischen Gleichungen, welche den Wirbelbewegungen entsprechen." Journal für die reine und angewandte Mathematik (Crelle's Journal), vol. 55 (1858): 25–55. First analysis of vortex motion; establishes the Helmholtz vorticity theorems (vortex lines frozen into inviscid fluid). SUPPORTS FACT-105: confirmed Helmholtz (1858) gave the vorticity-dynamics equations governing rotational structures. registry ↩a ↩b
[7] Prandtl, Ludwig. "Über Flüssigkeitsbewegung bei sehr kleiner Reibung." Verhandlungen des Dritten Internationalen Mathematiker-Kongresses (Heidelberg: Teubner, 1905): 484–491 (delivered 12 Aug 1904). Introduces boundary-layer theory: viscous effects confined to a thin near-wall layer; explains drag and separation. SUPPORTS FACT-106: confirmed Prandtl (1904, published 1905) founded boundary-layer theory. registry ↩a ↩b
[8] von Kármán, Theodor. "Über den Mechanismus des Widerstandes, den ein bewegter Körper in einer Flüssigkeit erfährt." Nachrichten von der Königlichen Gesellschaft der Wissenschaften zu Göttingen, Mathematisch-physikalische Klasse (1911): 509–517. Analyzes the alternating double row of vortices (Kármán vortex street) shed behind a bluff body, with its geometric stability conditions. SUPPORTS FACT-107: confirmed von Kármán (1911) explained vortex shedding from steady upstream flow. registry ↩a ↩b
[9] Lamb, Horace. Hydrodynamics. 6th ed. Cambridge: Cambridge University Press, 1932. Monumental classical treatise on inviscid and viscous flow, waves, and vortex dynamics; the definitive reference work for classical fluid theory. SUPPORTS FACT-108: confirmed Lamb's Hydrodynamics (6th ed. 1932) is the authoritative classical foundation. registry ↩
[10] Batchelor, George Keith. An Introduction to Fluid Dynamics. Cambridge: Cambridge University Press, 1967. Modern rigorous introduction combining classical exact solutions with turbulence, boundary layers, and instability. SUPPORTS FACT-109: confirmed Batchelor (1967) is the standard modern pedagogical treatment in the classical tradition. registry ↩a ↩b
[11] Darcy, Henry. Les fontaines publiques de la ville de Dijon. Paris: Victor Dalmont, 1856. Empirical study of water flow through sand beds; establishes Darcy's law (Q ∝ pressure gradient × area / length) as an appendix. SUPPORTS FACT-110: confirmed Darcy's law (1856) relates flow rate to pressure gradient through a permeable material, underpinning groundwater/geological transport. registry ↩a ↩b
[12] Frisch, Uriel. Turbulence: The Legacy of A. N. Kolmogorov. Cambridge: Cambridge University Press, 1995. ISBN 0-521-45713-0. Modern account of fully developed turbulence via Kolmogorov's cascade hypothesis: energy injected at large scales cascades to and dissipates at the Kolmogorov scale. SUPPORTS FACT-111: confirmed Frisch (1995) traces how energy cascades across scales and dissipates at the smallest eddies. registry ↩a ↩b ↩c ↩d
[13] Tritton, David J. Physical Fluid Dynamics. 2nd ed. Oxford: Clarendon Press / Oxford University Press, 1988. ISBN 9780198544937. Emphasis on experimental method, physical insight, and measurement (flow visualization, hot-wire anemometry, PIV). SUPPORTS FACT-112: confirmed Tritton (1988) synthesizes flow measurement and physical reasoning. registry ↩a ↩b
[14] Bird, R. Byron, Warren E. Stewart, and Edwin N. Lightfoot. Transport Phenomena. New York: Wiley, 1960. The first textbook unifying momentum (viscous flow), heat (conduction/convection), and mass (diffusion/convection) transport via analogous continuum frameworks. SUPPORTS FACT-113: confirmed BSL (1960) unifies momentum, heat, and mass transfer across domains. registry ↩a ↩b
[15] Poiseuille, Jean-Louis-Marie. Empirical and theoretical studies of viscous flow through capillary tubes ("Recherches expérimentales sur le mouvement des liquides dans les tubes de très petits diamètres", Comptes Rendus / Mémoires, 1840–1846); the Hagen–Poiseuille law Q = πR⁴ΔP/(8ηL), derived independently by Hagen (1839) and Poiseuille (1840–41, 1846), relates flow rate to the fourth power of tube radius; theoretical justification by Stokes (1845). SUPPORTS FACT-114: confirmed Poiseuille's law (formalized by Hagen and Poiseuille in the 1840s) relates flow rate to the fourth power of pipe radius. registry ↩a ↩b