pith. machine review for the scientific record.
sign in
theorem

codata_in_band

proved
show as:
module
IndisputableMonolith.Foundation.AlphaDerivationExplicit
domain
Foundation
line
36 · github
papers citing
1 paper (below)

plain-language theorem explainer

The theorem establishes that the CODATA 2022 inverse fine-structure constant lies strictly inside the Recognition Science interval from 137.030 to 137.039. A physicist verifying consistency between the derived alpha and experimental data would cite this result. The proof is a term-mode application of constructor to split the conjunction followed by norm_num on the three numeric definitions.

Claim. $137.030 < 137.035999084 < 137.039$

background

The Explicit Alpha Derivation module traces the provenance chain from the J-uniqueness theorem through the forced phi fixed point and D=3 (from the eight-tick period) to the 44-slot frequency structure that yields the RS alpha formula. The lower bound is defined as 137.030 and the upper bound as 137.039, while the CODATA value is fixed at 137.035999084. Upstream, the alpha definition supplies the fine-structure constant as the reciprocal of its inverse, and the from theorem reduces seven axioms to four structural conditions plus three definitional facts.

proof idea

The term proof applies constructor to split the conjunction into two goals. It then passes the definitions of alphaInverseLower, alphaInverseUpper, and codataAlphaInverse to norm_num, which reduces both inequalities to decidable numeric comparisons that evaluate directly.

why it matters

This result supplies the codata_in_band field of the AlphaProvenanceCert structure, which certifies the full chain from uniqueness to the alpha match. The module documentation presents it as part of the structural theorem confirming that the experimental value lies inside the RS band. In the framework it closes the verification step for the fine-structure constant after the T5 J-uniqueness, T6 phi fixed point, T7 eight-tick octave, and T8 D=3 steps.

Switch to Lean above to see the machine-checked source, dependencies, and usage graph.