Masses Mass Genesis Rest Mass Equals Mass Law Same Topology Realized Patterns Ha

Same topology, same mass

In the Recognition Science account, a light pattern is a discrete record of recognition events, and its topology is the shape of that record: which events connect to which. The framework's library of machine-checked theorems contains a result about what the topology alone can determine. It says that if two stable light patterns have the same topology, and if each pattern's measured rest mass equals the mass that its topology predicts, then the two rest masses are equal. The theorem is a conditional bridge: it does not claim that every pattern realizes the mass law, only that among those that do, topology fixes the mass.

The proof is short and direct. Rest mass for a stable pattern is defined as its integrated neutral light load. The mass-law prediction is a function of three topology-derived labels: sector, rung, and a charge label Z. The theorem first shows that same-topology patterns share all three labels, hence share the same predicted mass. Then, if each pattern's rest mass equals that common prediction, the two rest masses must equal each other. The library also proves the contrapositive: two same-topology patterns with different rest masses cannot both satisfy the mass-law equality.

This result matters because it marks the boundary of what topology can force. The framework models particle masses as lying on a phi-power ladder, with the scaling law proved. But the equality between rest mass and the topology-derived prediction requires an additional condition, named MassLawLoadRealized, which states that the integrated load actually realizes the predicted value. That condition is not proved from topology alone; it is a predicate that names the remaining normalization theorem. The library is explicit about this gap, calling it the missing realization predicate.

In Recognition Science, then, the declaration establishes a precise conditional statement: same topology plus realized mass law implies same rest mass. It does not establish that all stable patterns realize the mass law, nor that topology alone determines rest mass. The framework's own documentation flags this as the honest M7 boundary, the point where the bottom-up realization theorem still needs to be supplied.

theorem sameTopology_realized_patterns_have_same_restMass
    {ψ χ : LightPattern Λ}
    (htop : SameTopology ψ χ)
    (hψ : restMass ψ = predictedMass ψ)
    (hχ : restMass χ = predictedMass χ) :
    restMass ψ = restMass χ := by
  rw [hψ, hχ]
  exact predictedMass_eq_of_sameTopology htop

theorem predictedMass_eq_of_sameTopology
    {ψ χ : LightPattern Λ} (h : SameTopology ψ χ) :
    predictedMass ψ = predictedMass χ := by
  unfold predictedMass
  rw [sectorOf_eq_of_sameTopology h,
      rungOf_eq_of_sameTopology h,
      ZOf_eq_of_sameTopology h]

theorem sameTopology_different_restMass_obstructs_both_realized
    {ψ χ : LightPattern Λ}
    (htop : SameTopology ψ χ)
    (hdiff : restMass ψ ≠ restMass χ) :
    ¬ (restMass ψ = predictedMass ψ ∧ restMass χ = predictedMass χ) := by
  intro hboth
  exact hdiff
    (sameTopology_realized_patterns_have_same_restMass htop hboth.1 hboth.2)

What this page does not claim

The declaration does not prove that every stable pattern realizes the mass law. The declaration does not prove that topology alone determines rest mass. The declaration does not establish the missing realization predicate MassLawLoadRealized.

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/Masses/MassGenesis/RestMassEqualsMassLaw.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: