pith. sign in
theorem

neutron_lifetime_discrepancy_structure

proved
show as:
module
IndisputableMonolith.Experimental.NeutronLifetimeDiscrepancyStructure
domain
Experimental
line
15 · github
papers citing
none yet

plain-language theorem explainer

The neutron lifetime discrepancy structure holds because the lifetime matches the ledger prediction supplied by the phi-ladder model. Experimental physicists examining the neutron lifetime anomaly would cite this result to connect Recognition Science predictions with measured decay rates. The proof is a one-line term application of the upstream input theorem that reduces the ledger property to the neutron lifetime structure.

Claim. The neutron-lifetime discrepancy structure holds, since the neutron lifetime equals the value given by the ledger structure on the phi-ladder.

background

In Recognition Science the neutron lifetime is placed on the phi-ladder, with the general lifetime for rung k defined as phi^k. The module Experimental.NeutronLifetimeDiscrepancyStructure supplies an experimental interface that identifies the observed discrepancy with the ledger property. The upstream theorem has_neutron_lifetime_input states that the neutron lifetime from the ledger follows from the neutron lifetime structure. The definition neutron_lifetime_discrepancy_from_ledger simply equates the discrepancy proposition to that ledger property.

proof idea

This is a one-line wrapper that applies the theorem has_neutron_lifetime_input, which itself reduces the ledger property directly to the neutron lifetime structure.

why it matters

The declaration supplies the experimental link that lets the phi-ladder lifetime prediction confront the neutron lifetime anomaly. It sits inside the broader chain that derives particle masses and lifetimes from the self-similar fixed point phi and the eight-tick octave. No downstream theorems are recorded, so the result functions as a terminal experimental interface rather than an intermediate lemma.

Switch to Lean above to see the machine-checked source, dependencies, and usage graph.