Encyclopedia Masses Masses Mass Genesis T10 Run Cascade Quadratic Scale Boundary

ARTICLE 5 claims 5 theorems

Masses Mass Genesis T10 Run Cascade Quadratic Scale Boundary

A machine-checked proof shows that a broad family of cascade models in Recognition Science cannot produce the scale coupling the framework requires, narrowing the search for mass generation.

The quadratic scale boundary

The T10 run-cascade quadratic scale boundary is a result in the Recognition Science framework's study of mass generation. It concerns a specific family of candidate models that attempt to connect two levels of description: the discrete record of recognition events, called the ledger, and a continuous amplitude scale. The central finding is that this entire family, despite being given maximal freedom in its internal details, cannot satisfy the four-witness interface that the framework requires for a viable scale coupling. This is a membership theorem: it shows the family belongs to a class already known to be excluded, not a new wall in itself.

To understand the result, consider what the candidate models are allowed to do. The framework defines a ledger, a discrete record of events, and a cascade, a structured sequence of transformations. The models in question can inspect the complete settled octave, the full record of eight recognition ticks, and use any deposit sequence, any coefficients for cascade sectors, and any real-valued target functional. They may depend on initial balances, debit and credit sides, schedule order, and every reconstructed run state. These functions are granted maximal freedom: no factorization through parity, topology, deposit counts, or total length is assumed. The only constraint is that the deposit map is a single sequence shared across all sectors, not a sector-indexed family.

Despite this freedom, the mathematics forces a collapse. The unnormalized cascade pairing, the sum over sectors of coefficients times a load term, factors by the posting event load, which equals the amplitude squared. The settled continuum anchor load, the absolute neutralized load of the carrier's settled anchor window, is exactly twice the amplitude squared. When the model balances the cascade pairing against a multiple of the anchor load, the amplitude cancels, leaving an equation on the octave alone. The theorem quadraticRunPatternBalance_iff_reduced states this equivalence exactly: the balance holds if and only if the reduced pairing equals twice the target. Consequently, every such balance is run-only, meaning it depends only on the run, not on the amplitude or pattern shape.

Being run-only is fatal. The framework's RunPatternScaleCouplingInterface requires a coupling to respond to scale in a specific way, and a run-only filter cannot meet its four witnesses. The theorem quadraticRunPatternBalance_fails_interface proves this for the entire quadratic family. A concrete non-vacuity check is then provided: the exact-octave filter, which accepts carriers with a specified settled-octave record, is run-only, accepts the intended carrier, realizes the intended pattern, and violates the recognition ground state selection R4. This demonstrates the obstruction is real, not an artifact of an empty class.

The practical consequence is a narrowing of the search space. The most natural amplitude-bearing candidate family, with deposits, coefficients, and target maximally free on the octave, is now known to sit inside the run-only class and is therefore excluded. The proved complement of the two killed classes (run-only filters and this quadratic family) is larger than any named list of surviving shapes. Filters keyed to pattern support or topology lie outside both classes, and amplitude-pinning filters with an octave-varying level already meet all four interface witnesses. The framework has not constructed a surviving coupling with an independently derived nonzero reference level; that remains open. The result tells researchers where not to look, and where the remaining candidates must be found.

THEOREM orderedCascadePairing_factor · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Every such unnormalized pairing factors by the event load supplied at the
free continuum amplitude. -/
theorem orderedCascadePairing_factor {N : ℕ}
    (deposits : Q3SettledLedgerOctave → List (Fin N))
    (coeff : Q3SettledLedgerOctave → SectorN N → ℝ)
    (c : EmittedScaledSettledReadoutCarrier) :
    orderedCascadePairing deposits coeff c =
      postingEventLoad c.amplitude *
        reducedOrderedCascadePairing deposits coeff c.octave := by
  classical
  unfold orderedCascadePairing reducedOrderedCascadePairing
  rw [Finset.mul_sum]
  apply Finset.sum_congr rfl
  intro i _
  obtain ⟨n, p⟩ := i
  rw [omegaCascade_factor_amplitude]
  ring
THEOREM carrierAnchorLoad_eq · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Settlement makes the continuum anchor load exactly two amplitude
quanta. -/
theorem carrierAnchorLoad_eq
    (c : EmittedScaledSettledReadoutCarrier) :
    carrierAnchorLoad c = 2 * c.amplitude ^ 2 :=
  settledAnchor_neutralizedNormSq c.settled_anchor
THEOREM quadraticRunPatternBalance_isRunOnly · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Despite arbitrary order-sensitive run dependence, every balance in this
class is run-only. -/
theorem quadraticRunPatternBalance_isRunOnly {N : ℕ}
    (deposits : Q3SettledLedgerOctave → List (Fin N))
    (coeff : Q3SettledLedgerOctave → SectorN N → ℝ)
    (target : Q3SettledLedgerOctave → ℝ) :
    IsRunOnly
      (QuadraticRunPatternBalance deposits coeff target) := by
  intro c d hcd
  constructor
  · intro hc
    apply
      (quadraticRunPatternBalance_iff_reduced
        deposits coeff target d).2
    have hred :=
      (quadraticRunPatternBalance_iff_reduced
        deposits coeff target c).1 hc
    rw [hcd] at hred
    exact hred
  · intro hd
    apply
      (quadraticRunPatternBalance_iff_reduced
        deposits coeff target c).2
    have hred :=
      (quadraticRunPatternBalance_iff_reduced
        deposits coeff target d).1 hd
    rw [hcd]
    exact hred
THEOREM quadraticRunPatternBalance_fails_interface · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Main boundary: no unnormalized same-degree cascade/anchor balance in this
maximally order-sensitive class can meet the four-witness interface. -/
theorem quadraticRunPatternBalance_fails_interface {N : ℕ}
    (deposits : Q3SettledLedgerOctave → List (Fin N))
    (coeff : Q3SettledLedgerOctave → SectorN N → ℝ)
    (target : Q3SettledLedgerOctave → ℝ)
    (octave : Q3SettledLedgerOctave) :
    ¬ RunPatternScaleCouplingInterface
        (QuadraticRunPatternBalance deposits coeff target)
        octave := by
  intro hgate
  exact
    (runPatternScaleCouplingInterface_not_runOnly
      (QuadraticRunPatternBalance deposits coeff target)
      octave
      hgate)
      (quadraticRunPatternBalance_isRunOnly
        deposits coeff target)
THEOREM exactOctaveFilter_violates_r4 · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Non-vacuous instantiation of the banked run-only obstruction. -/
theorem exactOctaveFilter_violates_r4
    (octave : Q3SettledLedgerOctave) :
    ¬ RecognitionGroundStateSelection
      (CarrierRealized (ExactOctaveFilter octave)) :=
  runOnly_carrierRealized_violates_r4
    (ExactOctaveFilter octave)
    (exactOctaveFilter_isRunOnly octave)
    octave
    (exactOctaveFilter_accepts_intended octave)

What this page does not claim

This module does not construct or assume any surviving coupling with an independently derived nonzero reference level. This module does not classify the complement of the two killed classes; it only proves the complement is larger than any named list of surviving shapes. This module does not claim that the quadratic family is the only excluded class, nor that it is a new wall beyond the existing run-only obstruction.

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

MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND