Nuclear binding-energy difference → Mechanical work
Nuclear binding-energy differenceRadioactive decayAlpha particlesRadioisotope heatingTemperature gradientMarangoni effectMechanical motionMechanical work
Epistemic state of the route
- known constituent relations
- 7 / 7 established or replicated · weakest constituent replicated
- constituent maturity floor
- K4 · experimentally observed
- search for this exact route
- Not assessed — complete composition not searched.
- recorded-pathway overlap
- shares relations, in order, with Radioisotope heater unit · 4/7 relations shared
- route-level evidence
- 0 sources for the complete composition · 7 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.20 × C.27 · Nuclear binding-energy difference × Nuclear heatfamily: Nuclear heatD.20 × C.34 · Nuclear binding-energy difference × Marangonifamily: Marangoni
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
Steps
- 01nuclear → nuclearradioisotope requiredrefs [1]
- 02nuclear → nuclear
- alpha emitters such as Pu-238, Am-241, Po-210
refs [1] [2] - 03nuclear → thermal
- alpha particles stopped within the source pellet and its cladding (the RTG case)
radioisotope requiredrefs [1] - 04thermal → thermalrefs [1]
- 05thermal → 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 [3] [4] - 06kinetic → mechanical · loss to thermal
- a floating or interface-bound body whose asymmetry (shape, or where it emits a surfactant or absorbs heat) leaves a net surface-tension force or torque on it
- the body must be free to move on the interface; a rigid wall only sets up a flow
liquidTwo independent groups: thermocapillary microgears (Maggi et al. 2015, light-heated, up to 300 r.p.m.) and solutocapillary camphor rotors carrying magnets past a coil (Frenkel et al. 2019, 10–20 h). Distinct from Marangoni flow turning a rotor: here the Marangoni stress acts on the moving body directly.refs [5] [6] - 07mechanical → mechanical · loss to thermalrefs [7]
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 · 7
- [1]M. A. Prelas, et al.. A review of nuclear batteries (2014)
- [2]M. G. Spencer, T. Alam. High power direct energy conversion by nuclear batteries (2019)
- [3]L. E. Scriven, C. V. Sternling. The Marangoni Effects (1960)
- [4]Q. Dai et al.. Directional interfacial motion of liquids: Fundamentals, evaluations, and manipulation strategies (2021)
- [5]C. Maggi et al.. Micromotors with asymmetric shape that efficiently convert light into work by thermocapillary effects (2015)
- [6]M. Frenkel et al.. Mini-Generator of Electrical Power Exploiting the Marangoni Flow Inspired Self-Propulsion (2019)
- [7]A. Bejan. Advanced Engineering Thermodynamics (4th ed.) (2016)
Cite this route
Physical Transformation Atlas (2026). route p-0097b4ed0f: Nuclear binding-energy difference → Radioactive decay → Alpha particles → Radioisotope heating → Temperature gradient → Marangoni effect → Mechanical motion → Mechanical work. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/0097b4ed0f
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.