A registered result in its source context
Original ledger classification: Physical [C] (sharper scenario; both Boltzmann inputs share A_Lambda=10, no hidden seesaw scale) + [X] kill test
Recorded statement: LEPTOGENESIS SCALARON-DECUPLE BRANCH (2026-06-15): BOTH Boltzmann inputs share the decuple A_Lambda = 10 = |E(K5)| -- M_1 = M_scal phi0^2/A_Lambda ~ 8.65e9 GeV and m~1 = m_3/A_Lambda ~ 5 meV. A cleaner [C] route than FR.ETAB.03/v184's M_1…
Statement, assumptions and sources
Paper context: Frontier and open physical interfaces
The exact identifier, original classification and full claim are available below.
The source wording and classification below are preserved as recorded. A paper link, shared script or authored topic relation does not upgrade the claim or report a new proof run. Read later reviewed findings separately.
Read the exact registered claim and its dependencies
FR.ETAB.04
Original ledger classification: Physical [C] (sharper scenario; both Boltzmann inputs share A_Lambda=10, no hidden seesaw scale) + [X] kill test
Original claim text
LEPTOGENESIS SCALARON-DECUPLE BRANCH (2026-06-15): BOTH Boltzmann inputs share the decuple A_Lambda = 10 = |E(K5)| -- M_1 = M_scal phi0^2/A_Lambda ~ 8.65e9 GeV and m~1 = m_3/A_Lambda ~ 5 meV. A cleaner [C] route than FR.ETAB.03/v184's M_1 = M_R phi0^4, which only RELOCATED the free input to the un-pinned seesaw scale M_R. (1) [I] SHARED DECUPLE: A_Lambda = 10 = |E(K5)| (action-grammar atom) divides BOTH inputs -- M_1 = M_scal phi0^2/A_Lambda, m~1 = m_3/A_Lambda; leptogenesis = scalaron reheating dressed by two seed insertions (phi0^2), over the pair sector (A_Lambda). (2) [N] HEAVY MASS in the window: M_1 = M_scal phi0^2/A_Lambda = 8.65e9 GeV (M_scal = c3^{7/2} Mbar ~ 3.06e13 GeV, phi0 ~ 0.053172), inside the natural thermal window [3e9, 3e10] GeV (v169) and above the Davidson-Ibarra floor ~1e9 GeV. (3) [N] WASHOUT anchor: m~1 = m_3/A_Lambda ~ 5 meV (m_3 ~ sqrt(dm2_atm) ~ 0.05 eV), K = m~1/m_* ~ 4.6 (strong washout, m_* ~ 1.08 meV) -- the SAME A_Lambda = 10 as M_1. (4) [N] eta_B LANDS: Davidson-Ibarra eps_1 = (3/16 pi) M_1 m_3/v^2 ~ 8.5e-7; with kappa_f ~ 0.15 (strong washout) and sphaleron 28/79, eta_B ~ 0.96e-2 eps_1 kappa_f ~ 1.2e-9 -- O(1e-9), bracketing the observed 6.1e-10 (v169 band), no tuning. (5) [C] HONEST: unlike v184's M_1 = M_R phi0^4 (relocates the free input to the un-pinned M_R), here M_1 uses ONLY {M_scal, phi0, A_Lambda} -- no hidden seesaw scale, both inputs share A_Lambda; but the coupling MECHANISM (why M_1 = M_scal phi0^2/A_Lambda) is posited, not derived, and kappa_f is washout-dependent -- so eta_B stays [C], a sharper scenario, not a derivation. (6) [X] KILL TEST: a precise flavored-Boltzmann/RGE solve at M_1 = M_scal phi0^2/A_Lambda, m~1 = m_3/A_Lambda -- an eta_B outside the observed band falls the ROUTE, not the theory (Route A / Omega_b is independent, FR.ETAB.01). Python-only
Original classification detail
Physical [C]: M_1 = M_scal phi0^2/A_Lambda ~ 8.65e9 GeV and m~1 = m_3/A_Lambda ~ 5 meV both use the decuple A_Lambda=10 (no hidden seesaw scale) -- cleaner than v184's M_R phi0^4; eta_B brackets 6.1e-10 but stays [C] (coupling mechanism posited, not derived)
Dependencies as recorded
FR.ETAB.01; FR.ETAB.02; FR.ETAB.03; v169_etaB_boltzmann_interface.py
Open the original ledger source, row 301Location recorded in the ledger
These document locations are recorded directly on the ledger row. They are document level navigation, rather than a newly inferred section citation.
- Frontier and open physical interfaces
Sections that explicitly cite this claim
A literal claim identifier is present in these paper sections. The section and its premises determine what the citation supports.
- 2026-06-15 (frontier: two sharper [C] scenario branches — axion angle + leptogenesis)Research changelog; TFPT — Introduction and reading guide
Navigation through a shared verification script
These sections cite a script associated with the claim. This is a source navigation join, rather than an explicit citation of the claim or a theorem equivalence.
- 2026-06-23 (Track 3 — the [formula in source] functor promoted from contracts to TYPED runnable solvers with kill tests: Koide source [formula in source] pole ( v371), [formula in source] Boltzmann ( v372), axion finite- [formula in source] relic ( v373), [formula in source] uncertainty budget ( v374))Research changelog; TFPT — Introduction and reading guide
- 2026-06-15 (the F_transfer functor contract CONTRACT.F.01)Research changelog; TFPT — Introduction and reading guide
- 2026-06-24 (Correction error-bars: v393 the typed budget as actual first-correction magnitudes)Research changelog; TFPT — Introduction and reading guide
- Front matter / supportTFPT — Introduction and reading guide; Verification reference catalog
- 2026-06-24 (A falsifiable clock probe of the frontier: v397 how external is the ``external physics''?)Research changelog; TFPT — Introduction and reading guide
- Route B — leptogenesis interface ( ).Frontier and open physical interfaces
- Front matter / supportFrontier and open physical interfaces
Registered verification modules
- v212_leptogenesis_decuple.pyRegistered verification module · frontier
Read the description recorded in the module registry
leptogenesis, the scalaron-decuple branch: both Boltzmann inputs share the decuple A_Λ=10=|E(K₅)| — M₁=M_scal φ₀²/A_Λ≈8.65×10⁹ GeV and m̃₁=m₃/A_Λ≈5 meV. A cleaner [C] route than v184's M₁=M_R φ₀⁴ (which only relocated the free input to the un-pinned seesaw M_R). [I] shared decuple A_Λ=10; [N] M₁=M_scal φ₀²/A_Λ=8.65×10⁹ GeV (M_scal=c₃^{7/2} M̄≈3.06×10¹³, φ₀≈0.053172) inside the thermal window [3×10⁹,3×10¹⁰] (v169); [N] m̃₁=m₃/A_Λ≈5 meV (m₃≈0.05 eV), K≈4.6 strong washout; [N] Davidson–Ibarra ε₁≈8.5×10⁻⁷, η_B≈0.96×10⁻²·ε₁·κ_f≈1.2×10⁻⁹ brackets observed 6.1×10⁻¹⁰; [C] HONEST: M₁ uses only {M_scal,φ₀,A_Λ} (no hidden seesaw scale), but the coupling mechanism is posited not derived — η_B stays [C]; [X] kill test: a precise Boltzmann/RGE solve outside the band falls the route, not the theory (Route A/Ω_b independent, FR.ETAB.01).
A registered module is a source reference. Its presence does not assert that the module was executed in this snapshot.