What is checked
A Lean proof is as good as its statement, its axioms and the program that checks it. This page asks each question, and gives the answer when the check has run.
| not run | Is the source the same as the release? | Run rh fetch -compare. |
|---|---|---|
| not run | Does the project build with the pinned Lean and Mathlib? | Milestone M2. |
| not run | Which axioms does riemannHypothesis use? | Milestone M2, with #print axioms. |
| not run | Does a second kernel accept the proof? | Milestone M2, with lean4checker. |
| not run | Do the Lean statements say what the standard statements say? | Milestone M2, a review by a named person. |
| not run | How much of the proof is written in words? | Milestone M3 and later. |
How to read the table
- yes means that the check ran and passed.
- no means that the check ran and failed.
- open means that the check ran and a person must decide.
- not run means that the check did not run yet.
Question Q0 has a tool now: rh fetch -compare reproduced the hash of the archive and found the same 175,190 files as riemann-lean. The table changes to yes when the result is in records/trust.json. Questions Q1 to Q3 need a build of the full project, and milestone M2 does them. Question Q4 needs a person who reads each Lean statement against the standard statement.
The source of this page. The data is api/trust.json.