Encyclopedia Physics Physics Pion Mass Rs
ARTICLE 2 claims 2 theorems
Physics Pion Mass Rs
A machine-checked file about the pion mass turns out to prove only general facts about a cost function, not the mass itself.
The pion mass note
The neutral pion is the lightest of the mesons, particles made of a quark and an antiquark bound by the strong force. Its measured mass is about 135 MeV, where one MeV is the energy gained by an electron crossing one million volts. In the Recognition Science framework, a research note records an intended match: the golden ratio phi, about 1.618, raised to the tenth power gives 123 MeV, and multiplying by 1.10 brings that to 135 MeV, the pion mass. The note presents this as a numerical coincidence to explore, not as a derived result.
The framework's machine-checked library of formal theorems contains a file named for this idea, but the file proves something narrower. Its central definition, called domainCost, takes two real numbers m and e and returns the framework's recognition cost, a measure of how far a ratio sits from unity, applied to their quotient m divided by e. The library proves three general facts about this cost: it equals zero when m equals e, it never goes negative for positive inputs, and a certain threshold involving phi is positive. These are properties of the cost function itself, true for any positive numbers, not statements about pions.
The file's own documentation says this plainly: the paragraph about 135 MeV is a research note recording where the idea was meant to go, not a result. What would turn the file into a theorem about the pion is a definition of m and e in terms of the pion's own physics, such as its energy and some reference scale. No such definition appears. The file establishes that the cost function behaves sensibly at equality and stays nonnegative, and it packages those facts into a certificate structure, but it does not connect the numbers 135, 123, or 1.10 to any physical quantity.
For a reader, the useful lesson is about how to read the framework's output. A file named for a particle can contain only generic lemmas, and the name alone does not make the physics true. The numerical match in the note remains an unverified observation, a target for future work rather than a claim the library endorses.
THEOREM domainCost_at_eq · domainCost_nonneg · canonicalThreshold_pos · IndisputableMonolith/Physics/Pion_Mass_RS.lean
theorem domainCost_at_eq (r : ℝ) (h : r ≠ 0) : domainCost r r = 0 := by
unfold domainCost; rw [div_self h]; exact Jcost_unit0
theorem domainCost_nonneg (m e : ℝ) (hm : 0 < m) (he : 0 < e) : 0 ≤ domainCost m e := by
unfold domainCost; exact Jcost_nonneg (div_pos hm he)
theorem canonicalThreshold_pos : 0 < canonicalThreshold := by
unfold canonicalThreshold; linarith [phi_gt_onePointFive]
THEOREM cert_inhabited · IndisputableMonolith/Physics/Pion_Mass_RS.lean
theorem cert_inhabited : Nonempty PionMassCert := ⟨cert⟩
What this page does not claim
The pion mass is not derived from the framework's axioms in this file. The numerical match 135 MeV is not a theorem; it is an unverified research note. The file does not define m or e in physical terms.
Verify this page
Every tagged claim above names its theorem. To check one yourself rather than trust this page, elaborate the source module with Lean 4 and audit its axiom basis:
$ lake env lean IndisputableMonolith/Physics/Pion_Mass_RS.lean
expected axiom basis: [propext, Classical.choice, Quot.sound] (the Lean kernel's standard three; no RS-specific axioms)
A page whose claims cannot be reproduced this way does not ship. In production, every anchor links to the exact declaration in the public source release, and this block carries the build receipt for the page itself.
Derived articles
This page is generated by a question-recursion engine: the questions its answers raise become the next pages. The current agenda, with open targets marked red:
- What physical definition of m and e would make the pion mass a derived theorem rather than a research note?
- Does the 1.10 factor in the note have any structural meaning within the framework, or is it a free fit?
- Which other particle-mass files in the library share this same generic template?
MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND
THEOREM domainCost_at_eq · domainCost_nonneg · canonicalThreshold_pos · IndisputableMonolith/Physics/Pion_Mass_RS.lean
theorem domainCost_at_eq (r : ℝ) (h : r ≠ 0) : domainCost r r = 0 := by unfold domainCost; rw [div_self h]; exact Jcost_unit0theorem domainCost_nonneg (m e : ℝ) (hm : 0 < m) (he : 0 < e) : 0 ≤ domainCost m e := by unfold domainCost; exact Jcost_nonneg (div_pos hm he)theorem canonicalThreshold_pos : 0 < canonicalThreshold := by unfold canonicalThreshold; linarith [phi_gt_onePointFive]The library proves three general facts about this cost: it equals zero when m equals e, it never goes negative for positive inputs, and a certain threshold involving phi is positive. domainCost_at_eq · domainCost_nonneg · canonicalThreshold_pos · IndisputableMonolith/Physics/Pion_Mass_RS.leanTHEOREM cert_inhabited · IndisputableMonolith/Physics/Pion_Mass_RS.lean
theorem cert_inhabited : Nonempty PionMassCert := ⟨cert⟩The file establishes that the cost function behaves sensibly at equality and stays nonnegative, and it packages those facts into a certificate structure, but it does not connect the numbers 135, 123, or 1.10 to any physical quantity. cert_inhabited · IndisputableMonolith/Physics/Pion_Mass_RS.lean