Archive and hash route
The source page identifies the archive, exports, manifests, logs, toolchain versions, and SHA-256 values needed to identify the reported run.
External formalization reader / public source record
A public Lean claim becomes readable through five linked records: its theorem statement, source artifact, reported machine checks, stated caveats, and an independent replay route.
The reader preserves the source record in its native form and makes its evidence status, conditions, and inspection path explicit.
Source identity / current status
riemannHypothesis : RiemannHypothesisSOURCE_REPORTEDPENDING_REPLAYLOCAL_REPLAYED · self-attestedThe MIT-hosted checker page reports a public Lean formalization of the Riemann Hypothesis and related Dirichlet L-function statements. Coppalini Architecture supplies a source-indexed reader: artifact identity, evidence status, conditions, caveats, and an independent inspection route.
Native theorem carrier
The source displays Mathlib’s own definition of RiemannHypothesis. This reader retains that declaration as the theorem carrier rather than translating it into an Architecture theorem.
def RiemannHypothesis : Prop :=
∀ (s : ℂ) (_ : riemannZeta s = 0)
(_ : ¬∃ n : ℕ, s = -2 * (n + 1))
(_ : s ≠ 1), s.re = 1 / 2
Reported verification record
The source page identifies the archive, exports, manifests, logs, toolchain versions, and SHA-256 values needed to identify the reported run.
The page reports 175,187 compiled modules, an axiom audit, Lean-kernel replay, nanoda, con-leche, lean4lean, and comparator rows. Each is retained as a source-reported status, not collapsed into one badge.
At the source update, the default and paranoid Lean-kernel export replays and the end-to-end lake comparator run remained active. The direct-build, export-provenance, and comparison caveats remain adjacent to reported passes.
External checker page → source archive and hashes → selected independent checker → output comparison → source-indexed reader receipt.
Reporting context / secondary records
The reporting record preserves the public event around the release: its announcement, reception, and active review. It remains distinct from the theorem carrier, source artifact, checker table, caveats, and replay receipt.
Joseph Howlett’s initial report records the public claim and Lean release. A later report by Clara Moskowitz and Lee Billings records independent recompilation while retaining comparator, redefinition, and kernel-path checks as outstanding.
Nature reports the claimed result as an announcement requiring rigorous checking, with the mathematical response and interpretation still in progress.
The AP report records the announcement, the Lean artifact, and the institutional fact that assessment of a claimed solution takes time.
Quanta documents the release and the contemporaneous effort to inspect its formal record, keeping the public mathematical question separate from the announcement itself.
Office. These are selected contemporaneous secondary reports retrieved 2026-11-21. They do not supply the Lean theorem carrier, source artifact identity, machine-check outcome, caveat disposition, or independent replay receipt. The statuses SOURCE_REPORTED and PENDING_REPLAY remain unchanged.
Coppalini Architecture / reader office
Each statement retains its source, condition, status, and check route. The external source carries its theorem statement, artifacts, and reported checker results. This reader carries their public address, stated conditions, and a clean route for independent inspection.
Local reader boundary. EARR-001 is a finite external-anchor receipt. Its small local Lean module is LOCAL_REPLAYED · self-attested; R3’s retention repair remains pending because the workflow hash and raw command output are not retained. That local replay does not replay, validate, or prove the external Riemann-Hypothesis formalization.
External-artifact boundary. The external formalization remains SOURCE_REPORTED / PENDING_REPLAY until a separately retained artifact replay supplies its own transcript. R14’s semantic-schema repair remains required before adapter names can carry a semantic adapter claim.
Packet boundary. This page does not publish, link, or distribute the EARR-001 packet. Packet release remains gated on Section 8 of the reader brief.
Adapter boundary. Adapter names are retained; semantic adapter schema is not declared.