pith. sign in
module module high

IndisputableMonolith.Foundation.OptionAFalsifierRegistry

show as:
view Lean formalization →

This module registers the implemented Option A combinations C1 through C9 as the core falsifier registry in the Recognition Science foundation. A researcher testing empirical coverage of Option A would cite it to confirm that each combination carries an associated dataset class, predicted observable, and failure mode. The structure leaves C10 as commentary only and supplies the metadata skeleton that downstream protocols consume. It is a pure definition module with no proofs.

claimRegistry of implemented Option A combinations $C_1$ to $C_9$, each equipped with a dataset class, predicted observable, and failure mode; $C_{10}$ retained solely as commentary.

background

Recognition Science derives physics from the forcing chain T0-T8, with Option A combinations arising as concrete instances of the J-cost and phi-ladder constructions. The module introduces the supporting types: CombinationID enumerates the nine implemented cases, TestClass and DatasetClass label the empirical probes, EmpiricalStatus tracks coverage, PredictedObservable names the measurable signature, and FailureMode specifies the falsifying observation. These definitions sit inside the Foundation layer and import only Mathlib, supplying the structural interface that converts theoretical combinations into falsifiable statements.

proof idea

This is a definition module, no proofs.

why it matters in Recognition Science

The module supplies the registry consumed by the Option A Empirical Protocol, which asserts total coverage: every implemented C1-C9 combination possesses a dataset class, predicted observable, and failure mode. It closes the formal loop from the unified forcing chain to empirical falsification, ensuring no implemented Option A result lacks a corresponding test protocol. The construction directly supports the framework's claim that the phi-ladder and mass formulas remain empirically accessible.

scope and limits

used by (1)

From the project-wide theorem graph. These declarations reference this one in their body.

declarations in this module (35)