Follow a result back to its evidence.

Choose a result, inspect its assumptions, then run the calculation that supports it. Each check answers a specific question. The original status and the scope of that answer stay attached.

Start with the E₈ construction.

The first module builds the lattice explicitly. It checks the glue, constructs its 240 roots and tests the lattice basis. You can read the source before running it.

Question: Does the explicit construction give the even, unimodular E₈ lattice?
What is tested: Shared ℤ₄ discriminant data; glue norms 5/4 + 3/4 = 2; 240 roots of squared length 2; an integral, even basis with determinant 1.

Read the Python source

Python runs in your browser using Pyodide. The first run downloads the runtime. Its output appears in the existing verification viewer, including any failure and the local reproduction command.

This is a mathematical lattice check. Identifying that lattice with a physical system requires additional arguments and retains its own status.

Find the source behind a check.

Search all 707 registered Python modules by subject, filename, claim or source section. This catalogue records source presence and links. It does not report a new execution or a passing result for every module.

1 matching module · showing 1–1

Clear filters

Continuum realisation sharpened

v351_continuum_realisation_sharpened.py · core

Read the original description and evidence links

The continuum realisation sharpened -- the 'c=8 ambiguity' flagged open in v277/v344 (E8 vs SO(16) both have c=8) is RESOLVED, non-circularly, by the seam's ORDER-4 mu4 clock. [E] E8 (det 1, holomorphic) vs D8=SO(16) (det 4). [E] the order-4 clock (the four Gauss-Bonnet marks, |mu4|=4=h(A3), v216): index-4 extension D5(+)A3 = E8 (v154), index-2 = SO(16); so order-4 selects E8 (16->4->1) not SO(16) (16->4) -- the order (4 not 2) is the discriminator. [E] bootstrap agrees: h(E8)=30 (max prime 5) vs h(D8)=14 (max prime 7). [E] which-net ambiguity RESOLVED (det K=1 is then a consequence). [O] residual = PURELY the chiral-edge/scaling-limit existence (bulk-edge, v336), net+holomorphy pinned. Does NOT close SEAM.EQUIV.01.

Read the original Python source

Linked claims: SEAM.EQUIV.CONTINUUM.02
Paper sections: Source section 1 Source section 2 Source section 3 Source section 4 Source section 5 Source section 6 Source section 7 Source section 8 Source section 9 Source section 10 Source section 11 Source section 12 Source section 13 Source section 14 Source section 15 Source section 16 Source section 17

Different evidence answers different questions.

A numerical calculation, a formal theorem and an experimental comparison carry different kinds of information. Follow the source appropriate to the claim.

Python calculations: Inspect the algorithm, its inputs and its negative controls. Run a browser compatible module here, or use the repository for the complete environment.Browse Python sources
Formal mathematics: Read the actual Lean statement and its assumptions. The carrier formalization has a defined mathematical scope.Inspect the Lean formalization
Independent implementation: The Wolfram implementation checks algebraic results through a separate computational path. The recorded runs report 116/116 base checks and 603/603 extension checks. This is distinct from external experimental replication.Read the Wolfram implementation
Physical comparison: Read each prediction with its freeze, conditions and failure criterion. A passing mathematical check does not decide the experimental comparison.Open the prediction register

Run the same check on your machine.

From a checkout of the repository, install its Python requirements and run the first lattice module. The complete suite is a separate step.

Set up the repository

git clone https://github.com/sthamann/tfpt.git
cd tfpt
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt

Check the E₈ lattice

.venv/bin/python verification/v1_e8_glue.py

Read the individual checks and the final pass or fail result.

Run the registered suite

cd verification
../.venv/bin/python run_all.py

The full suite uses the dependencies and source context documented in the repository.

Repository setup and maintenance instructions

Read the current claim beside its source.

The research snapshot dated 2026-11-02 includes the active ledger, reviewed findings and registered scripts. It records source coverage and stated scope; it is not a new execution of every proof or calculation.

Find a result and its premises Download the ledger Inspect snapshot coverage

Trace the dependencies.

Select a node to inspect its inputs, outputs, scope and verification scripts. Browser compatible checks open the same verification viewer; native certificates provide their local command.

Explore the complete dependency graph

Keep the detailed research in reach.

The script index, figures and detailed research interfaces remain available below. This older technical overview preserves its original statements; use the current result inventory to follow later scope corrections.

Open the script index, figures and research details