Physical Transformation AtlasPTA
Claim · claim:binding-drives-fission

Nuclear binding-energy difference —drives→ Nuclear fission

The atlas records this claim as established: a nuclear binding-energy difference drives nuclear fission under the conditions below.

establishedK8 · commercial technologyledger nuclear → kinetic · loss to radiativeno record-level review date

Exploreconditions · evidence · matrix context · uses · cite

2cited sources71enumerated routes using it3routes with composition evidence3recorded pathways

Conditions

  • for neutron-induced fission: a fissionable nuclide and an incident neutron in an energy range with non-zero fission cross-section
  • critical geometry is required only for a self-sustaining chain reaction; a moderator is reactor-design dependent

Evidence · 2

  1. [1]
    O. Hahn, F. Strassmann. Über den Nachweis und das Verhalten der bei der Bestrahlung des Urans mittels Neutronen entstehenden Erdalkalimetalle (1939)
    Naturwissenschaften 27, 11–15 · doi:10.1007/BF01488241 · crossref ✓ 2026-09-19 · record
  2. [2]
    O. R. Frisch. Physical evidence for the division of heavy nuclei under neutron bombardment (1939)
    Nature 143, 276 · doi:10.1038/143276a0 · crossref ✓ 2026-09-19 · record

Matrix cells this relation feeds

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

Uses of this claim

recorded pathways · 3
other enumerated routes · 68 (first 24 shown)

all 71 routes are in /api/paths.json filtered by claims ∋ claim:binding-drives-fission

Notes

About 200 MeV per event, almost all as fragment kinetic energy (Frisch 1939); thermalisation is a separate step.

Cite this claim

Physical Transformation Atlas (2026). claim claim:binding-drives-fission: Nuclear binding-energy difference —drives→ Nuclear fission. Dataset revision rbfbfcbb70e57 (hash of the canonical data). https://physical-transformation-atlas.wldud5192.workers.dev/claim/binding-drives-fission

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.