A registered result in its source context
Original ledger classification: m_p/m_e uncertainty budget: the observed 1836.15 is inside the propagated +-7.5% (alpha_s, C_p) band; lattice-tightening is the kill [C]/[N]/[X]
Recorded statement: Track 3 (2026-06-23, F_transfer): the m_p/m_e transfer as a TYPED uncertainty-budget + kill test -- the falsifiability companion to v262 (the precise 2-loop point), replacing the v326 toy (which hardcodes 1836.15). Does NOT re-derive…
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.QCD.BUDGET.01
Original ledger classification: m_p/m_e uncertainty budget: the observed 1836.15 is inside the propagated +-7.5% (alpha_s, C_p) band; lattice-tightening is the kill [C]/[N]/[X]
Original claim text
Track 3 (2026-06-23, F_transfer): the m_p/m_e transfer as a TYPED uncertainty-budget + kill test -- the falsifiability companion to v262 (the precise 2-loop point), replacing the v326 toy (which hardcodes 1836.15). Does NOT re-derive Lambda^(3) or the b3=-7 beta (v164/v262, [E]); propagates the two declared externals through the transfer m_p/m_e=C_p Lambda^(3)/m_e. [E] b3=-(11-2 n_f/3)=-7 (n_f=6 carrier). [N] two declared externals (v339): alpha_s(M_Z)=0.1179+-0.0009 (PDG) and C_p=2.83+-0.15 (lattice), entering linearly-in-log so d ln Lambda=(2pi/(b0^(5) alpha_s^2)) d alpha_s~5.3% and d C_p/C_p~5.3%. [C] m_p/m_e central ~1824 (v262 2-loop) with a propagated 1-sigma band +-sqrt(5.3^2+5.3^2)%~+-7.5% -> [~1690,~1960], CONTAINING the observed 1836.15 -- no free dial. [X] kill: a future lattice C_p+-0.03 + tighter alpha_s shrink the band to ~+-2%; a band then EXCLUDING 1836.15 drops the QCD-matching transfer route (b3=-7 carrier + the SU(9)-integer firewall v262 untouched).
Original classification detail
[E] b3=-7; [N] the two externals; [C] the observed ratio inside the propagated band (no dial); [X] the lattice-tightening kill test. An uncertainty-budget/falsifiability solver, distinct from v262's point estimate; m_p/m_e stays [C].
Dependencies as recorded
FR.MPME.02; v262; v164; v339
Open the original ledger source, row 86Location 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-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
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.
- Appendix: computational verificationFrontier and open physical interfaces
- The closure ledger: what is done, and what genuinely remainsTFPT — Introduction and reading guide
- 2026-06-23 (Status propagation: the v365– v380 [formula in source] FORM.SEAM.MMST.01 status carried into the remaining papers, the README and the Zenodo description)Research changelog; TFPT — Introduction and reading guide
- What this means for the theory-of-everything questionTFPT — Introduction and reading guide
- -1.2cm TFPT — Research Contracts for the Remaining Interfaces:\\v_ geo [formula in source] G_ net [formula in source] F_ transfer [formula in source] (U_ wall) [formula in source] (G_ metric) [formula in source] [formula in source] / _1/ _2/ _3 [formula in source] next)tfpt research contracts
- The hard reduction: the live residual as typed interfacesTFPT — Introduction and reading guide
- 2026-06-23 (Bird's-eye synthesis: two new structural patterns — v383 the universal spectral-gap principle and v384 the residual is certification, not construction)Research changelog; TFPT — Introduction and reading guide
- Front matter / supportResearch contracts
All 15 linked sections
- 2026-06-24 (Correction error-bars: v393 the typed budget as actual first-correction magnitudes)
- (4) Constructive QFT closure of the admissible physical sector /
- Summary
- Front matter / support
- -1.2cm TFPT — Research Contracts for the Remaining Interfaces:\\v_ geo [formula in source] G_ net [formula in source] F_ transfer [formula in source] (U_ wall) [formula in source] (G_ metric) [formula in source] [formula in source] / _1/ _2/ _3 [formula in source] next)
- 2026-06-24 (A falsifiable clock probe of the frontier: v397 how external is the ``external physics''?)
- (4) Constructive QFT closure of the admissible physical sector /
Registered verification modules
- v374_ftransfer_qcd.pyRegistered verification module · frontier
Read the description recorded in the module registry
Track 3 (F_transfer): the m_p/m_e transfer as a typed uncertainty-budget + kill test -- the falsifiability companion to v262 (the precise 2-loop point), replacing the v326 toy (which hardcodes 1836.15). [E] b3=-(11-2 n_f/3)=-7 (n_f=6 carrier). [N] two declared externals (v339): alpha_s(M_Z)=0.1179+-0.0009 and C_p=2.83+-0.15, each ~5.3%. [C] m_p/m_e central ~1824 (v262) with a propagated +-7.5% band [~1690,~1960] CONTAINING the observed 1836.15 -- no free dial. [X] kill: a future lattice C_p+-0.03 + tighter alpha_s shrink the band to ~+-2%; a band then excluding 1836.15 drops the QCD-matching route (b3=-7 + the SU(9)-integer firewall v262 untouched). Distinct from v262's point; stays [C].
A registered module is a source reference. Its presence does not assert that the module was executed in this snapshot.