Fourth-moment theorem
Lean 4A formalized proposition for the specific operator construction and fourth moment. Proof checking does not replace independent review of how the formal definitions correspond to the intended mathematical object.
Explore the theorem at the centre of the research programme, the higher-moment questions that remain open, the independent Phi-Genesis spectral audit, and the engineering systems built around invariant-first design.
Each link opens its own repository or workflow. Status badges report only the named workflow, not the whole research programme. Rift-L1 and Rift Network have separate source-available licensing notices.
The source theorem concerns a specific SU(2)-connected operator on Sierpiński-gasket graphs and its commuting control.
With the documented normalization, Iₘ(θ) = Δₘ / (3ᵐ⁺¹ + 3) tends to −(16/9) sin²(θ/2). At θ = π/2, the limiting value is exactly −8/9.
Each category answers a different question. This page does not invent live counters; the source links lead to reports and workflows.
A formalized proposition for the specific operator construction and fourth moment. Proof checking does not replace independent review of how the formal definitions correspond to the intended mathematical object.
Selected finite-level Fourier coefficients have modular/CRT certificates, with numerical holdouts. The all-level recurrence and derivation of the exceptional first transition remain open.
Signed-flux spectral decimation and mass-index claims are audited separately. The full exceptional set and residual mismatches are not closed; selected patterns are not established physical laws.
Runtime invariants, fuzzing, audit findings, and deployment records support specific code paths and configurations. They are not a formal proof of every possible execution.
Select a stage to inspect its evidence obligation.
Start from the source statement and formalization. Keep the fourth-moment theorem separate from every conjectural extension.
Higher moments and signed-flux decimation have distinct proof obligations. Finite certificates and numerical patterns do not close all-level claims.
Runtimes, blockchain protocols, kernel stress tests, quantum architectures, and energy models each require their own validation.
Links show the relationship between programmes; they do not imply that a result in one repository proves claims in another.
Specified SU(2)/Sierpiński-gasket fourth-moment identity; Lean 4 formalization reported for stated scope.
Higher-moment recurrence and recursive-operator research; selected finite-level certificates; all-level recurrence open.
Signed-flux spectral decimation, boundary/corner corrections, inertia calculations, and mass-formula audit.
Invariant-first execution model, architecture coordination, and implementation-specific verification.
Pre-experimental gauge-covariant fractal quantum-processing architecture; no speed-up claim implied.
Exploratory invariant-driven energy-system scenarios with explicit modelling assumptions.
This is a conceptual map of the programme. Use commit history for exact chronology and source-specific status at a given date.
Specify state constraints and require transitions to preserve them.
State the fourth-moment identity and formalization scope.
Build finite certificates and holdouts; retain the all-level open problem.
Test signed-flux claims; preserve failures and open residuals.
Explore systems and devices with separate engineering evidence.