Temperature gradient → Electrical work
Temperature gradientMarangoni effectFluid flowAerodynamic and hydrodynamic liftMechanical motionElectromagnetic inductionCharge carriersElectrical work
Epistemic state of the route
- known constituent relations
- 7 / 7 established or replicated · weakest constituent established
- constituent maturity floor
- K4 · experimentally observed
- search for this exact route
- Not assessed — complete composition not searched.
- recorded-pathway overlap
- none recorded
- route-level evidence
- 0 sources for the complete composition · 8 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.
D.01 × C.34 · Temperature gradient × Marangonifamily: MarangoniD.01 × C.24 · Temperature gradient × Turbomachineryfamily: TurbomachineryD.01 × C.14 · Temperature gradient × Electromagnetic inductionfamily: Electromagnetic induction
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, applies to this routeη ≤ 1 − T_c/T_h for any heat engine between reservoirs at T_h and T_c
- Betz limit · upper-bound · hard, filtered out by its applicabilityC_p ≤ 16/27 ≈ 59.3% of the kinetic power through the rotor disc
Steps
- 01thermal → kinetic · loss to thermal
- thermocapillary case: surface tension falls with temperature, so a temperature gradient along the interface drives flow toward the cold side
liquid · temperature gradient requiredrefs [1] [2] - 02
- 03kinetic → mechanical · loss to thermal
- a rotor or vane in the produced stream at a working angle of attack; the driven flow must carry a directed momentum flux for a blade to load
bulk flow requiredrefs [3] [4] - 04mechanical → mechanicalrefs [4]
- 05mechanical → electrical · loss to thermal
- a magnet moving relative to a coil
conductor required · magnetic field requiredrefs [5] [6] - 06electrical → electrical · loss to thermalrefs [5] [7]
- 07electrical → electrical · loss to thermal
- carriers driven through an external load at the potential difference the source maintains
refs [8]
Evidence for the complete composition · 0
No source on record for this exact composition. The sources below support the individual steps, not the route as a whole.
Evidence for the constituent relations · 8
- [1]L. E. Scriven, C. V. Sternling. The Marangoni Effects (1960)
- [2]Q. Dai et al.. Directional interfacial motion of liquids: Fundamentals, evaluations, and manipulation strategies (2021)
- [3]A. Betz. Das Maximum der theoretisch möglichen Ausnützung des Windes durch Windmotoren (1920)
- [4]S. L. Dixon, C. A. Hall. Fluid Mechanics and Thermodynamics of Turbomachinery (7th ed.) (2014)
- [5]M. Faraday. Experimental researches in electricity (1832)
- [6]S. P. Beeby, et al.. A micro electromagnetic generator for vibration energy harvesting (2007)
- [7]L. D. Landau, E. M. Lifshitz, L. P. Pitaevskii. Electrodynamics of Continuous Media (Course of Theoretical Physics, Vol. 8, 2nd ed.) (1984)
- [8]N. W. Ashcroft, N. D. Mermin. Solid State Physics (1976)
Cite this route
Physical Transformation Atlas (2026). route p-f4ed68056a: Temperature gradient → Marangoni effect → Fluid flow → Aerodynamic and hydrodynamic lift → Mechanical motion → Electromagnetic induction → Charge carriers → Electrical work. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/f4ed68056a
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.