Foundation Pair Kernel Executable Effect Physical Existence S27 Distinct Product

What the probe theorem shows

In the Recognition Science framework, a ledger is a discrete record of events. The framework's library, a machine-checked collection of formal theorems, proves a fact about the ledger's recognition classes, the categories into which events are sorted by observation. The theorem named distinctProductionEffectClasses_have_distinguishingProbe states: if two effect classes are not equal, then there exists a probe, a single measurement, that gives different readings on the two classes. In plain terms, no two distinct kinds of event are observationally identical; the ledger never hides a difference from every possible test.

This is a separation result. It guarantees that the framework's way of grouping events into classes is faithful to what can be measured. If two classes were different but every probe returned the same value, the classification would be a fiction, a label with no empirical content. The theorem rules that out. It is proved in the machine-checked library with no unproved assumptions, and it is one of the results that lets the framework treat its observable classes as physically meaningful.

The theorem does not claim that any particular probe is known or easy to build. It only asserts that at least one distinguishing measurement exists for any pair of distinct classes. It also does not claim that the framework's classes are the only way to describe physical reality. The library explicitly leaves open the question of whether a separately supplied raw physical ontology, a description of the world given from outside the framework, matches the framework's own classes. That independence is a separate, deliberately unproved point.

What the theorem changes is the epistemic status of the framework's classifications. Before it, one could worry that the classes were merely formal, with no guarantee of observational grip. After it, the worry is closed: distinct classes are always separable by measurement. The result is a foundation for the framework's claim that its recognition classes are not arbitrary bookkeeping but correspond to real, testable distinctions.

/-- Distinct physical effect classes are distinguished by a committed
operational probe. This is the no-ghost converse licensed by the observational
quotient: every distinction in this carrier has an operational witness. -/
theorem distinctProductionEffectClasses_have_distinguishingProbe
    (left right : ProductionOperationEffectClass3)
    (hne : left ≠ right) :
    ∃ probe : ProductionOperationEffectProbe3,
      productionOperationEffectClassObservation3 probe left ≠
        productionOperationEffectClassObservation3 probe right := by
  classical
  by_contra hno
  push_neg at hno
  apply hne
  apply productionOperationEffectCoordinateRepresentation_injective
  funext probe
  exact hno probe

/-- Distinct physical effect classes are distinguished by a committed
operational probe. This is the no-ghost converse licensed by the observational
quotient: every distinction in this carrier has an operational witness. -/
theorem distinctProductionEffectClasses_have_distinguishingProbe
    (left right : ProductionOperationEffectClass3)
    (hne : left ≠ right) :
    ∃ probe : ProductionOperationEffectProbe3,
      productionOperationEffectClassObservation3 probe left ≠
        productionOperationEffectClassObservation3 probe right := by
  classical
  by_contra hno
  push_neg at hno
  apply hne
  apply productionOperationEffectCoordinateRepresentation_injective
  funext probe
  exact hno probe

What this page does not claim

The theorem does not identify any particular probe or show how to construct one. The theorem does not claim that the framework's observable classes are the only valid description of physical reality. The theorem does not establish that a separately supplied raw physical ontology matches the framework's classes.

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