P0-locked · machine readable · public sources only

Claim–Evidence
Ledger

Every central statement is connected to assumptions, formulas, source hashes, code, tests, results, limitations and a falsification condition. A software PASS is never promoted into empirical confirmation.

Download ledger JSONJSON Schema
ID
Scope: public static SSZ geometry and its public observable pipelines •Lock: P0-2026.08 •Reviewed: 3 August 2026 •Private mixed material: excluded
Stable Claim-IDs

Search the public scientific record

Deep links use the Claim-ID itself. Hashes identify the reviewed source bytes; commit SHAs identify code state. An empty or open field is evidence of incompleteness, not permission to infer the missing result.

—matching claims

Loading evidence ledger…

Dependency direction

Which statements depend on which locks?

An arrow points from a dependent claim toward a prerequisite. Select a node to open its ledger record. The graph represents declared logical/provenance dependencies, not causal physics.

Select a graph node or use the claim list.
Epistemic vocabulary

Evidence classes are not interchangeable

External review path

Audit a claim without trusting the portal

  1. Resolve the Claim-ID

    Read the precise statement, domain, observer scope and explicitly excluded implications.

  2. Verify source bytes and commit

    Compare the SHA-256 hash, repository path and commit with the cited public source.

  3. Reproduce the code path

    Run the recorded command with the declared inputs and inspect numerical tolerances.

  4. Challenge the evidence class

    Decide whether the result is an identity, numerical check, compatibility result, fit or genuinely discriminating observation.

  5. Apply the falsification condition

    Record negative results and dependencies instead of averaging them into a green aggregate.