Encyclopedia Foundation Foundation Pair Kernel Weyl Event Length Non Identifiability Scale Realized Post

ARTICLE 3 claims 2 theorems 1 model

Foundation Pair Kernel Weyl Event Length Non Identifiability Scale Realized Post

A machine-checked result shows that the framework's present data about an event cannot fix its physical size; any positive length unit works.

The scale wall

A physical radius needs two ingredients: a number and a unit. The Recognition Science framework models an event's size with a length carrier, a small record that pairs a dimensionless radius with one positive physical length unit, such as a meter. The declaration scaleRealizedPostingWeylLengthCarrier27 defines an operation on this carrier: multiply the unit by any positive scale factor, say 2 or 1/1000, and leave the dimensionless radius untouched. This operation always produces another valid carrier, and the physical radius it reports changes by exactly that factor. The definition is a modeling choice, not a theorem.

The theorem that follows from this definition is the sharp one. It states that two carriers holding the same dimensionless radius and the same attached center, but different positive length units, yield different physical radii. In other words, the present recognition data, the center and the dimensionless radius, cannot select a physical length. The framework's library proves this as a formal no-go result: presentWeylRecognitionData_does_not_select_dimensionedRadius27 and its constructive companion presentWeylLengthScale_countermodel27 exhibit an explicit pair of carriers with identical recognition data but unequal radii.

The scope of this result is precise. It is a theorem no-go for the stated present-data interface, not a proof that no future Recognition construction can derive length. The framework's own docstring says the surviving theory must add a scale-bearing physical carrier whose length response is part of the object from birth. The result carries no sorry, no new axiom, and no empirical constant; it is a statement about the current data structure, not about the world.

What changes because of this theorem? It tells a reader exactly where the framework cannot yet reach: physical size is not determined by the recognition data available so far. Any claim that the framework has derived a specific length for an event from its center and dimensionless radius would overstate this result. The theorem closes one door and names the next one: a carrier that carries its length response from the start.

MODEL scaleRealizedPostingWeylLengthCarrier27 · IndisputableMonolith/Foundation/PairKernelWeylEventLengthNonIdentifiability.lean
/-- Positive rescaling of only the physical event-length unit. -/
def scaleRealizedPostingWeylLengthCarrier27
    {event : RealizedPostingEvent3 3}
    (scale : ℝ)
    (hscale : 0 < scale)
    (carrier : RealizedPostingWeylLengthCarrier27 event) :
    RealizedPostingWeylLengthCarrier27 event where
  dimensionlessRadius := carrier.dimensionlessRadius
  eventLengthUnit := scale * carrier.eventLengthUnit
  dimensionlessRadius_pos := carrier.dimensionlessRadius_pos
  eventLengthUnit_pos :=
    mul_pos hscale carrier.eventLengthUnit_pos
THEOREM presentWeylRecognitionData_does_not_select_dimensionedRadius27 · IndisputableMonolith/Foundation/PairKernelWeylEventLengthNonIdentifiability.lean
presentWeylRecognitionData_does_not_select_dimensionedRadius27 · IndisputableMonolith/Foundation/PairKernelWeylEventLengthNonIdentifiability.lean:102
/-- Two positive length units remain compatible with exactly the same present
Weyl Recognition data and yield different physical radii. -/
theorem presentWeylRecognitionData_does_not_select_dimensionedRadius27
    {event : RealizedPostingEvent3 3}
    (carrier : RealizedPostingWeylLengthCarrier27 event) :
    ¬ PresentWeylRecognitionDataSelectsDimensionedRadius27
      carrier := by
  intro hselect
  have hsame :=
    scale_preserves_presentWeylRecognitionData27
      2 (by norm_num) carrier
  have heq := hselect
    (scaleRealizedPostingWeylLengthCarrier27
      2 (by norm_num) carrier) hsame
  rw [dimensionedWeylEventRadius_scale27] at heq
  have hradius_pos :
      0 < dimensionedWeylEventRadius27 carrier :=
    mul_pos carrier.eventLengthUnit_pos
      carrier.dimensionlessRadius_pos
  linarith
THEOREM presentWeylLengthScale_countermodel27 · IndisputableMonolith/Foundation/PairKernelWeylEventLengthNonIdentifiability.lean
/-- Constructive countermodel pair for external consumers. -/
theorem presentWeylLengthScale_countermodel27
    {event : RealizedPostingEvent3 3}
    (carrier : RealizedPostingWeylLengthCarrier27 event) :
    ∃ other : RealizedPostingWeylLengthCarrier27 event,
      SamePresentWeylRecognitionData27 carrier other ∧
        dimensionedWeylEventRadius27 carrier ≠
          dimensionedWeylEventRadius27 other := by
  refine
    ⟨scaleRealizedPostingWeylLengthCarrier27
        2 (by norm_num) carrier,
      scale_preserves_presentWeylRecognitionData27
        2 (by norm_num) carrier, ?_⟩
  intro heq
  rw [dimensionedWeylEventRadius_scale27] at heq
  have hradius_pos :
      0 < dimensionedWeylEventRadius27 carrier :=
    mul_pos carrier.eventLengthUnit_pos
      carrier.dimensionlessRadius_pos
  linarith

What this page does not claim

The result does not prove that no future Recognition construction can derive length. The result does not claim that the framework has derived any specific physical length for an event. The declaration does not assert that the scaling operation is physically meaningful; it only defines it.

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/Foundation/PairKernelWeylEventLengthNonIdentifiability.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