Nuclear binding-energy difference → Electrical work
Nuclear binding-energy differenceNuclear fusionTemperature gradientThermionic emissionCharge carriersElectrical work
Epistemic state of the route
- known constituent relations
- 3 / 5 established or replicated · weakest constituent demonstrated
- constituent maturity floor
- K4 · experimentally observed
- search for this exact route
- Not assessed — complete composition not searched.
- recorded-pathway overlap
- shares its closing relations with Thermionic converter · 3/5 relations shared
- route-level evidence
- 0 sources for the complete composition · 6 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.02 · Nuclear binding-energy difference × Thermionicfamily: Thermionic
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
- Space-charge limit · formula-bound · hard, applies to this routeJ ≤ (4ε₀/9)√(2e/m) V^{3/2}/d² (Child–Langmuir)
Steps
- 01nuclear → kinetic · loss to radiative
- for a power-producing D–T thermonuclear plasma: ion temperatures of order 10 keV and a sufficient density–confinement product (Lawson); these are power-balance conditions, not prerequisites for an individual fusion reaction
plasma · above ~700 KFusion reactions and target-level fusion energy release are experimentally demonstrated (target gain > 1 at NIF, 2022–2024); net electrical output from a fusion power plant is not.refs [1] [2] [3] - 02kinetic → thermal · loss to radiative
- energetic products (neutrons, alphas) deposit their kinetic energy in a blanket or the plasma, which then runs hotter than its surroundings
refs [2] [3] - 03thermal → electrical · loss to radiative
- cathode hot enough that kT is a useful fraction of the work function (typically > 1500 K for metals, lower for low-work-function coatings)
- a cooler anode across a vacuum or caesium-vapour gap
vacuum required · above ~700 K · solidrefs [4] [5] - 04electrical → electrical · loss to thermal
- emitted electrons collected at the anode at a potential difference set by the work-function difference
refs [5] - 05electrical → electrical · loss to thermal
- carriers driven through an external load at the potential difference the source maintains
refs [6]
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 · 6
- [1]H. A. Bethe. Energy production in stars (1939)
- [2]J. D. Lawson. Some criteria for a power producing thermonuclear reactor (1957)
- [3]H. Abu-Shawareb, et al. (Indirect Drive ICF Collaboration). Achievement of target gain larger than unity in an inertial fusion experiment (2024)
- [4]O. W. Richardson. On the negative radiation from hot platinum (1901)
- [5]G. N. Hatsopoulos, E. P. Gyftopoulos. Thermionic Energy Conversion, Vol. 1: Processes and Devices (1973)
- [6]N. W. Ashcroft, N. D. Mermin. Solid State Physics (1976)
Cite this route
Physical Transformation Atlas (2026). route p-255c251ab2: Nuclear binding-energy difference → Nuclear fusion → Temperature gradient → Thermionic emission → Charge carriers → Electrical work. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/path/255c251ab2
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.