Masses Mass Genesis Load Normalization Support Averaged Mass Law Load Realizes

The averaging condition

In the Recognition Science framework, a light pattern (a discrete configuration of recognized events) carries a numerical load at each occupied site. The framework's mass law assigns each stable pattern a predicted mass, a number derived from the pattern's topology alone. The question this page addresses is how the loads at individual sites must be arranged so that their total equals that predicted mass.

The declaration supportAveragedMassLawLoad_realizes establishes a sufficient condition. If every occupied site carries the same load, and that common load equals the predicted mass divided by the number of occupied sites, then the total load equals the predicted mass. In plainer terms: if the mass is spread evenly across all occupied sites, the sum works out. The theorem also requires that the pattern has at least one occupied site, a nonempty support.

This is a formal statement in the framework's machine-checked library of formal theorems. It does not assert that real patterns actually distribute their loads this way. The docstring is explicit: this is a sufficient target, not the final physics of every pattern. It identifies one way the mass law could be realized, not the way it must be.

The theorem's role is to pin down what amplitude information is missing from a simpler normalization. A prior result showed that if every occupied site carries unit load, the total load equals the number of sites. The averaging condition goes further: it states the exact per-site load needed to hit the topology-selected mass, rather than just the site count.

What the declaration does not claim is equally important. It does not prove that any actual pattern satisfies the averaging condition. It does not derive the condition from deeper principles; the framework's docstring lists that derivation as a future target. And it does not say that the predicted mass itself is correct, only that this load distribution would realize it.

For a reader, the practical upshot is a precise statement of a possible mechanism. The framework has not yet shown that mass is actually spread evenly across occupied sites. It has shown that if it were, the mass law would be satisfied. The gap between the sufficient condition and the actual physics remains open.

theorem supportAveragedMassLawLoad_realizes
    (ψ : LightPattern Λ)
    (hsupp : ψ.support.Nonempty)
    (havg : SupportAveragedMassLawLoad ψ) :
    MassLawLoadRealized ψ := by
  unfold MassLawLoadRealized
  rw [integratedMeaningLoad_eq_support_sum ψ]
  have hcard_ne : (ψ.support.card : ℝ) ≠ 0 := by
    exact_mod_cast Finset.card_ne_zero.mpr hsupp
  calc
    ψ.support.sum (fun x => siteMeaningLoad ψ x)
        = ψ.support.sum
            (fun _x => predictedMass ψ / (ψ.support.card : ℝ)) := by
          apply Finset.sum_congr rfl
          intro x hx
          exact havg x hx
    _ = (ψ.support.card : ℝ) *
          (predictedMass ψ / (ψ.support.card : ℝ)) := by
          simp
    _ = predictedMass ψ := by
          field_simp [hcard_ne]

theorem integratedMeaningLoad_eq_supportCard_of_neutralUnitLoad
    (ψ : LightPattern Λ) (hunit : NeutralUnitLoadOnSupport ψ) :
    integratedMeaningLoad ψ = (ψ.support.card : ℝ) := by
  rw [integratedMeaningLoad_eq_support_sum ψ]
  calc
    ψ.support.sum (fun x => siteMeaningLoad ψ x)
        = ψ.support.sum (fun _x => (1 : ℝ)) := by
          apply Finset.sum_congr rfl
          intro x hx
          exact hunit x hx
    _ = (ψ.support.card : ℝ) := by
          simp

What this page does not claim

The theorem does not assert that any real pattern actually distributes its load evenly. The theorem does not derive the averaging condition from deeper principles. The theorem does not establish that the predicted mass itself is correct.

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/LoadNormalization.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: