Encyclopedia Masses Masses Mass Genesis T10 Orbit Section No Go Ledger Topology Only Parent Not Reco
ARTICLE 3 claims 3 theorems
Masses Mass Genesis T10 Orbit Section No Go Ledger Topology Only Parent Not Reco
A machine-checked theorem shows that a certain class of rules for choosing a pattern's amplitude cannot work, and it carefully names the limits of that result.
A limit on scale-blind selection
A ledger, a discrete record of events, can be rescaled: you can multiply all its numerical entries by the same positive number and still have a record of the same shape. The theorem ledgerTopologyOnlyParent_not_recognitionGroundStateSelection concerns rules for selecting a pattern's amplitude that depend only on this shape, not on the scale. It proves that no such rule, if it accepts even one valid pattern, can also select the pattern's ground state, the state of lowest cost. The proof works by taking the accepted pattern, rescaling it to its zero-cost point, and then doubling it; the result is still accepted, but it sits at a ratio of four, where the cost is not zero.
The theorem is a statement about a fragment of the framework, not about the whole foundation. The framework is not scale-blind: it derives a load-side predicate, ledger occupancy, which is two-valued and therefore not scale-invariant, and this predicate forces the settled amplitude to exactly one. That derived predicate lies outside the fragment the theorem concerns. An independence claim quantified over the whole foundation would be false, and was refuted on 2026-07-27. Both no-go results carry receipts showing their hypotheses are load-bearing: dropping the same-zero-set hypothesis or the accepted-carrier hypothesis changes the outcome.
In plain terms, the theorem says that a rule which only sees the shape of a pattern, and ignores its size, cannot also pick out the pattern's ground state. It does not say that no rule in the framework can do this, only that no rule of that particular shape-blind kind can. The framework's own derived predicate, which is not scale-blind, does the job. The result is a boundary on a class of rules, not a verdict on the framework as a whole.
THEOREM ledgerTopologyOnlyParent_not_recognitionGroundStateSelection · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean
/-- Consequently no ledger/topology-only parent that accepts a Q3 carrier can
be a realization predicate satisfying R4. This is the load-side counterpart of
the banked amplitude wall. -/
theorem ledgerTopologyOnlyParent_not_recognitionGroundStateSelection
(P : Q3SettledLedgerOctave → LightPattern (Fin 8) → Prop)
(hP : IsLedgerTopologyOnlyParent P)
(octave : Q3SettledLedgerOctave)
{ψ : LightPattern (Fin 8)}
(E : Q3ClosedPatternEvidence ψ)
(hacc : P octave ψ) :
¬ RecognitionGroundStateSelection (fun χ => P octave χ) :=
scaleBlindFragment_not_recognitionGroundStateSelection _
(ledgerTopologyOnlyParent_rescalingClosed P hP octave) E hacc
THEOREM booleanOccupancy_is_derived_and_not_scaleBlind · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean
/-- **The scope statement for no-go 2.** There is a derived, load-side predicate
of the present foundation which is outside the rescaling-closed fragment *and*
which fixes an absolute amplitude: a settled anchor whose window is Boolean has
posting amplitude exactly one.
So the foundation is not silent about the normalization and no-go 2 must never
be reported as independence from it. The honest reading is narrower and still
useful: nothing inside the scale-blind fragment can supply the missing sentence,
so a derivation has to come from the part of the foundation this predicate
inhabits. -/
theorem booleanOccupancy_is_derived_and_not_scaleBlind :
¬ IsRescalingClosedPatternPredicate BooleanSettledAnchorWindow ∧
∀ (a : ℝ) (χ : LightPattern (Fin 8)),
SettledAnchorWindow a χ → BooleanSettledAnchorWindow χ → 0 < a →
a = 1 :=
⟨booleanSettledAnchorWindow_not_rescalingClosed,
fun _a _χ hwin hbool ha =>
settledAnchor_boolean_forces_unitAmplitude hwin hbool ha⟩
THEOREM sameZeroSet_hypothesis_is_load_bearing · acceptedCarrier_hypothesis_is_load_bearing · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean
/-- Deleting the same-zero-set hypothesis from no-go 1 makes it false. The
universally true constraint is imposed by every realization predicate, while R4
fails for the matter carrier, so the two sides come apart. -/
theorem sameZeroSet_hypothesis_is_load_bearing :
(∀ ψ : LightPattern (Fin 8), Q3MatterCarrier ψ → True) ∧
¬ RecognitionGroundStateSelection Q3MatterCarrier :=
⟨fun _ _ => trivial, q3MatterCarrier_not_recognitionGroundStateSelection⟩
/-- Deleting the accepted-carrier hypothesis from no-go 2 makes it false. The
empty realization predicate is rescaling-closed and satisfies R4 vacuously, so
the no-go bites exactly on predicates that accept some matter. -/
theorem acceptedCarrier_hypothesis_is_load_bearing :
IsRescalingClosedPatternPredicate (fun _ => False) ∧
RecognitionGroundStateSelection (fun _ => False) :=
⟨fun _ _ _ h => h.elim, fun _ h => h.elim⟩
What this page does not claim
The theorem does not claim that no rule in the framework can select a ground state. It does not claim that the framework itself is scale-blind or incomplete. It does not claim that the specific derived predicate of ledger occupancy is the only way to break scale blindness.
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/T10OrbitSectionNoGo.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 is the full definition of the ledger topology that the theorem's scale-blind fragment uses?
- How does the derived, non-scale-blind predicate of ledger occupancy fit into the broader mass genesis derivation?
- What other fragments of the framework might be subject to similar no-go results?
MACHINE LAYER · GROUNDED CLAIM TABLE · CLICK TO EXPAND
THEOREM ledgerTopologyOnlyParent_not_recognitionGroundStateSelection · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean
/-- Consequently no ledger/topology-only parent that accepts a Q3 carrier can be a realization predicate satisfying R4. This is the load-side counterpart of the banked amplitude wall. -/ theorem ledgerTopologyOnlyParent_not_recognitionGroundStateSelection (P : Q3SettledLedgerOctave → LightPattern (Fin 8) → Prop) (hP : IsLedgerTopologyOnlyParent P) (octave : Q3SettledLedgerOctave) {ψ : LightPattern (Fin 8)} (E : Q3ClosedPatternEvidence ψ) (hacc : P octave ψ) : ¬ RecognitionGroundStateSelection (fun χ => P octave χ) := scaleBlindFragment_not_recognitionGroundStateSelection _ (ledgerTopologyOnlyParent_rescalingClosed P hP octave) E haccIt proves that no such rule, if it accepts even one valid pattern, can also select the pattern's ground state, the state of lowest cost. ledgerTopologyOnlyParent_not_recognitionGroundStateSelection · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.leanTHEOREM booleanOccupancy_is_derived_and_not_scaleBlind · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean
/-- **The scope statement for no-go 2.** There is a derived, load-side predicate of the present foundation which is outside the rescaling-closed fragment *and* which fixes an absolute amplitude: a settled anchor whose window is Boolean has posting amplitude exactly one. So the foundation is not silent about the normalization and no-go 2 must never be reported as independence from it. The honest reading is narrower and still useful: nothing inside the scale-blind fragment can supply the missing sentence, so a derivation has to come from the part of the foundation this predicate inhabits. -/ theorem booleanOccupancy_is_derived_and_not_scaleBlind : ¬ IsRescalingClosedPatternPredicate BooleanSettledAnchorWindow ∧ ∀ (a : ℝ) (χ : LightPattern (Fin 8)), SettledAnchorWindow a χ → BooleanSettledAnchorWindow χ → 0 < a → a = 1 := ⟨booleanSettledAnchorWindow_not_rescalingClosed, fun _a _χ hwin hbool ha => settledAnchor_boolean_forces_unitAmplitude hwin hbool ha⟩The framework is not scale-blind: it derives a load-side predicate, ledger occupancy, which is two-valued and therefore not scale-invariant, and this predicate forces the settled amplitude to exactly one. booleanOccupancy_is_derived_and_not_scaleBlind · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.leanTHEOREM sameZeroSet_hypothesis_is_load_bearing · acceptedCarrier_hypothesis_is_load_bearing · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean
/-- Deleting the same-zero-set hypothesis from no-go 1 makes it false. The universally true constraint is imposed by every realization predicate, while R4 fails for the matter carrier, so the two sides come apart. -/ theorem sameZeroSet_hypothesis_is_load_bearing : (∀ ψ : LightPattern (Fin 8), Q3MatterCarrier ψ → True) ∧ ¬ RecognitionGroundStateSelection Q3MatterCarrier := ⟨fun _ _ => trivial, q3MatterCarrier_not_recognitionGroundStateSelection⟩/-- Deleting the accepted-carrier hypothesis from no-go 2 makes it false. The empty realization predicate is rescaling-closed and satisfies R4 vacuously, so the no-go bites exactly on predicates that accept some matter. -/ theorem acceptedCarrier_hypothesis_is_load_bearing : IsRescalingClosedPatternPredicate (fun _ => False) ∧ RecognitionGroundStateSelection (fun _ => False) := ⟨fun _ _ _ h => h.elim, fun _ h => h.elim⟩Both no-go results carry receipts showing their hypotheses are load-bearing: dropping the same-zero-set hypothesis or the accepted-carrier hypothesis changes the outcome. sameZeroSet_hypothesis_is_load_bearing · acceptedCarrier_hypothesis_is_load_bearing · IndisputableMonolith/Masses/MassGenesis/T10OrbitSectionNoGo.lean