Physical Transformation AtlasPTA
Pathway · p-e6101d69e3 · demonstrated

Forced-circulation heat-delivery loop

Temperature gradientAdvective heat transportHeat flowUseful heat

A pumped fluid carries enthalpy from a hot region to a cold one and delivers it as useful heat — forced convection in the DOE handbook's sense, the fluid motion caused by an outside force such as a pump, with the pumped heat exchanger as its canonical example and a reactor's primary coolant loop as a commercial one. A transport subsystem, not a converter: thermal in, thermal out.

Epistemic state of the route

known constituent relations
3 / 3 established or replicated · weakest constituent established
constituent maturity floor
K4 · experimentally observed
search for this exact route
A recorded pathway or a reviewed search records a demonstration of this composition.
recorded pathway
Forced-circulation heat-delivery loop · commercial
composition maturity
K8 · commercial technology
recorded-pathway overlap
this route is the recorded pathway Forced-circulation heat-delivery loop
auxiliaries off the route
  • external input · mechanical · circulation pump — establishes flow:bulk-fluid-motion: external pump or equivalent circulation machinery maintains bulk motion of the heat-carrying fluid through the hot and cold regions (mechanical because that is the work supplied to the fluid; an implementation may obtain the shaft work electrically (the PWR's reactor coolant pumps do))
Loads the named implementation needs that no linear route carries (pass 36); a whole-cycle or net efficiency includes them, the enumerated route is the useful-output causal spine.
route-level evidence
2 sources for the complete composition · 3 cited by the constituent steps
boundaries and interfaces
BOUNDARY compatible · no region transition

Explorematrix context · physics checks · steps · route evidence · constituent evidence · cite

Matrix context

D = disequilibrium row · C = coupling family column. A cell reads the state of the atlas for that pair.

No coupling family recorded for this route's phenomena.

Typed bounds on this route

Every limit the atlas holds for this route, as constraint records: reached through bounded_by claims on the route's own entities. Hard bounds (an upper bound or a formula) decide the thermodynamic-bound check above; benchmarks, constitutive relations and resource limits are listed and never decisive. No prose limit exists anywhere (pass 42).

  • Carnot limit · formula-bound · hard, filtered out by its applicability
    η ≤ 1 − T_c/T_h for any heat engine between reservoirs at T_h and T_c

Steps

  1. 01
    thermal → thermal
    • a bulk fluid flow connects the hotter and colder regions
    • for forced circulation the flow may be supplied by an external pump rather than generated by buoyancy
    refs [1] [2] [3]
  2. 02
    thermal → thermal
    refs [1] [2]
  3. 03
    Heat flow —converts into→ Useful heatestablishedclaim record
    thermal → thermal
    • heat delivered at a temperature above the point of use
    refs [1]

Evidence for the complete composition · 2

  1. [3]
    U.S. Department of Energy. DOE Fundamentals Handbook: Thermodynamics, Heat Transfer, and Fluid Flow, Volume 2 of 3 (DOE-HDBK-1012/2-92) (1992)
  2. [2]
    U.S. Nuclear Regulatory Commission. Pressurized Water Reactors — how a typical commercial PWR works (2025)

Evidence for the constituent relations · 3

  1. [1]
    A. Bejan. Advanced Engineering Thermodynamics (4th ed.) (2016)
    Wiley · doi:10.1002/9781119245964 · crossref ✓ 2026-09-19 · record
  2. [2]
    U.S. Nuclear Regulatory Commission. Pressurized Water Reactors — how a typical commercial PWR works (2025)
  3. [3]
    U.S. Department of Energy. DOE Fundamentals Handbook: Thermodynamics, Heat Transfer, and Fluid Flow, Volume 2 of 3 (DOE-HDBK-1012/2-92) (1992)

Cite this route

Physical Transformation Atlas (2026). route p-e6101d69e3: Forced-circulation heat-delivery loop. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/e6101d69e3

Ids and matrix addresses are stable across revisions; the revision hash identifies the exact canonical files the record was compiled from and is meta.data_hash in every /api export. Reuse terms: see the license field in any export.