Encyclopedia Masses Masses Mass Genesis T10 Run Cascade Quadratic Scale Boundary Canonical Exact Oct

ARTICLE 3 claims 3 theorems

Masses Mass Genesis T10 Run Cascade Quadratic Scale Boundary Canonical Exact Oct

A filter that accepts only one exact ledger record shows why mass generation cannot depend on the full order of past events.

The exact-octave filter

In the Recognition Science account of mass generation, a ledger is a discrete record of recognition events, and a filter is a rule that accepts or rejects a proposed carrier, a package of pattern and amplitude that would carry a mass. The declaration canonicalExactOctaveFilter_violates_r4 proves that one particular filter, which accepts a carrier only if its settled octave record equals a fixed canonical record, cannot satisfy the four-witness interface RunPatternScaleCouplingInterface. The proof shows this filter is run-only: it depends only on the settled octave, not on any other feature of the carrier.

Why does that matter? The four-witness interface is a set of conditions that any viable scale-coupling must meet, and a run-only filter fails them all. The theorem states that no filter in this class can meet the interface, and the exact-octave filter is a concrete, non-vacuous instance: it accepts the intended carrier, so the failure is real, not an artifact of an empty class. The proof is a membership theorem, not a second wall: every predicate excluded here was already excluded by the earlier run-only obstruction T10RunHistoryScaleCouplingBoundary.

The theorem does not claim that no filter can ever satisfy the interface. It does not classify the complement: filters keyed to pattern.support or pattern.topology lie outside both the run-only class and the quadratic family, and amplitude-pinning filters with an octave-varying level already meet all four witnesses. The theorem only establishes that this natural, maximally free candidate family sits inside the run-only class, and therefore cannot serve as a scale coupling.

THEOREM canonicalExactOctaveFilter_violates_r4 · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Fully concrete specialization to the constructed Gray-settled octave. -/
theorem canonicalExactOctaveFilter_violates_r4 :
    ¬ RecognitionGroundStateSelection
      (CarrierRealized
        (ExactOctaveFilter canonicalQ3SettledLedgerOctave)) :=
  exactOctaveFilter_violates_r4
    canonicalQ3SettledLedgerOctave
THEOREM exactOctaveFilter_isRunOnly · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- Exact-octave equality is run-only. -/
theorem exactOctaveFilter_isRunOnly
    (octave : Q3SettledLedgerOctave) :
    IsRunOnly (ExactOctaveFilter octave) := by
  intro c d hcd
  unfold ExactOctaveFilter
  rw [hcd]
THEOREM exactOctaveFilter_accepts_intended · IndisputableMonolith/Masses/MassGenesis/T10RunCascadeQuadraticScaleBoundary.lean
/-- The filter accepts the actual intended carrier over that octave. -/
theorem exactOctaveFilter_accepts_intended
    (octave : Q3SettledLedgerOctave) :
    ExactOctaveFilter octave
      (intendedGapOneFactorCarrier octave) :=
  rfl

What this page does not claim

The theorem does not classify all filters that fail the interface; it only covers the run-only and quadratic families. The theorem does not construct or assume any surviving coupling with an independently derived nonzero reference level. The theorem does not claim that no filter can ever satisfy the interface.

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