Add builds (2026-11-09)
Browse files
README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
| 1 |
---
|
| 2 |
license: mit
|
| 3 |
-
pretty_name: "Lean
|
| 4 |
tags:
|
| 5 |
- lean4
|
| 6 |
- mathlib
|
|
@@ -8,47 +8,72 @@ tags:
|
|
| 8 |
- build-cache
|
| 9 |
---
|
| 10 |
|
| 11 |
-
# Lean
|
| 12 |
|
| 13 |
-
Compiled Lean 4
|
| 14 |
-
[AxiomMath/partial-regularity](https://github.com/AxiomMath/partial-regularity), so a checkout can skip compiling.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 15 |
|
| 16 |
-
|
| 17 |
-
or by Axiom. The source code and all credit belong to its authors; see `LICENSE` and `NOTICE.md`.
|
| 18 |
|
| 19 |
-
|
| 20 |
|
| 21 |
-
| commit |
|
| 22 |
-
|---|---|---|---|---|
|
| 23 |
-
| `90e9fef30ec4` | v4.34.0-rc2 |
|
| 24 |
|
| 25 |
-
|
| 26 |
-
`lake-manifest.json` used, deterministic `shards/*.tar.zst` with a per-file SHA-256 index, and `reports/`.
|
| 27 |
|
| 28 |
-
|
|
|
|
|
|
|
|
|
|
| 29 |
|
| 30 |
-
|
| 31 |
-
|
| 32 |
-
|
| 33 |
-
|
| 34 |
-
|
|
|
|
|
|
|
| 35 |
|
| 36 |
-
##
|
| 37 |
|
| 38 |
-
-
|
| 39 |
-
|
| 40 |
-
|
| 41 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 42 |
|
| 43 |
-
|
| 44 |
|
| 45 |
-
-
|
| 46 |
-
|
| 47 |
-
- `
|
| 48 |
-
-
|
|
|
|
|
|
|
|
|
|
|
|
|
| 49 |
|
| 50 |
-
##
|
| 51 |
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
over the environment.
|
|
|
|
| 1 |
---
|
| 2 |
license: mit
|
| 3 |
+
pretty_name: "Compiled Lean outputs for partial-regularity (from AxiomMath/partial-regularity, unofficial)"
|
| 4 |
tags:
|
| 5 |
- lean4
|
| 6 |
- mathlib
|
|
|
|
| 8 |
- build-cache
|
| 9 |
---
|
| 10 |
|
| 11 |
+
# Compiled Lean outputs for partial-regularity
|
| 12 |
|
| 13 |
+
> **What this is.** Compiled Lean 4 outputs (`.olean`, `.ilean`, `.c` and Lake trace files) for
|
| 14 |
+
> [AxiomMath/partial-regularity](https://github.com/AxiomMath/partial-regularity) at the commits listed below, so a checkout can skip compiling.
|
| 15 |
+
>
|
| 16 |
+
> **What this is not.**
|
| 17 |
+
> - Not a check of the mathematics. These files show that the code compiled. They do not show that the Lean
|
| 18 |
+
> statements faithfully formalize the results they are named after, and nobody here reviewed them as mathematics.
|
| 19 |
+
> - Not an official release. Built and published by MoteMath; not affiliated with or endorsed by AxiomMath or the
|
| 20 |
+
> authors of partial-regularity. The source and all credit belong to its authors (see `LICENSE` and `NOTICE.md`).
|
| 21 |
+
>
|
| 22 |
+
> **How it was made.** By an automated, AI-assisted build pipeline on cloud machines, from the public source at each
|
| 23 |
+
> listed commit. The build log and every report are in each build folder under `reports/`.
|
| 24 |
|
| 25 |
+
## Builds and what was checked
|
|
|
|
| 26 |
|
| 27 |
+
Every value below is read from the build folder's own reports; "not run" and "not recorded" mean exactly that.
|
| 28 |
|
| 29 |
+
| commit | Lean | packed | modules | `sorry` warnings | other warnings | axiom audit | round trip |
|
| 30 |
+
|---|---|---|---|---|---|---|---|
|
| 31 |
+
| `90e9fef30ec4` | v4.34.0-rc2 | 2026-11-08 | 4 | 2 | 421 | flags sorry | passed |
|
| 32 |
|
| 33 |
+
**Build `90e9fef30ec4-3ebee2901176c032`** (source commit `90e9fef30ec4deaab84034917424b011f4341ec7`)
|
|
|
|
| 34 |
|
| 35 |
+
- `sorry` warnings: 2, in `PartialRegularity/problem.lean`, `extension/ext_problem.lean`. Results in these files are not proved.
|
| 36 |
+
- Axiom audit: 535 declarations; axioms beyond the standard three: sorryAx.
|
| 37 |
+
- Declarations that depend on them (first ones listed by the audit): `irregular_primes_asymptotic` (sorryAx), `irregularPrimes_isBigO` (sorryAx).
|
| 38 |
+
- Round trip on a clean machine: passed. Restored on a clean machine; AxiomMath/partial-regularity: Lake reported every target up to date (8767 jobs). (1 of 1 projects using it passed; checked 2026-11-09)
|
| 39 |
|
| 40 |
+
What the columns mean:
|
| 41 |
+
- **`sorry` warnings:** declarations the build reported as using `sorry`. Anything depending on them is not proved.
|
| 42 |
+
- **Axiom audit:** every declaration in the package's modules traced to the axioms it uses. "passed" means only
|
| 43 |
+
`propext`, `Classical.choice` and `Quot.sound`. It does not say a statement is the intended one: a theorem that
|
| 44 |
+
takes a hard fact as a hypothesis passes.
|
| 45 |
+
- **Round trip:** a separate user with empty Lean and Lake caches restored the build from the archive and Lake reported
|
| 46 |
+
every target up to date. It shows the archive is complete, not that the proofs are right.
|
| 47 |
|
| 48 |
+
## Using a build
|
| 49 |
|
| 50 |
+
1. Clone AxiomMath/partial-regularity at the build's commit and run `lake exe cache get`, which fetches Mathlib from Mathlib's own
|
| 51 |
+
cache and checks out the dependencies.
|
| 52 |
+
2. Get `lbc.py` from [MoteMath/lean-builds-index](https://huggingface.co/datasets/MoteMath/lean-builds-index)
|
| 53 |
+
(`tools/lbc.py`, about 700 lines of Python; read it before running it). It needs Python 3.10+, `zstd` and
|
| 54 |
+
`huggingface_hub`.
|
| 55 |
+
3. Fetch as little as you need:
|
| 56 |
+
- `python3 lbc.py fetch . --module Some.Module` downloads only the shards holding that module and its import closure.
|
| 57 |
+
Repeat `--module` for several, and add `--dry-run` to see the size first.
|
| 58 |
+
- `python3 lbc.py fetch .` downloads every shard of every package with a published build.
|
| 59 |
+
4. Run `lake build --no-build +Some.Module` (or `lake build --no-build` after a full fetch). It must report everything up
|
| 60 |
+
to date; `--check` on the fetch does this for you.
|
| 61 |
+
|
| 62 |
+
Each build folder holds `manifest.json` (commit, toolchain, dependency closure, shard hashes), the exact
|
| 63 |
+
`lake-manifest.json` used, deterministic `shards/*.tar.zst` with a per-file SHA-256 index, and `reports/`.
|
| 64 |
|
| 65 |
+
## Trust and checking independently
|
| 66 |
|
| 67 |
+
- The SHA-256 hashes show a download is intact and matches what was published here. They come from the same publisher
|
| 68 |
+
as the files, so they are not evidence that the files are honest.
|
| 69 |
+
- Lean does not re-check `.olean` files when it loads them. A tampered file could contain a theorem with no valid proof.
|
| 70 |
+
- To check independently, use either route:
|
| 71 |
+
- re-check the compiled environment with the kernel: `lake env lean4checker --fresh Some.Module` (lean4checker
|
| 72 |
+
replays every declaration through Lean's kernel);
|
| 73 |
+
- or rebuild from the source commit and compare.
|
| 74 |
+
- For anything you rely on, prefer one of these over trusting the archive.
|
| 75 |
|
| 76 |
+
## Questions, corrections and removal
|
| 77 |
|
| 78 |
+
Open a discussion in this repository's Community tab. Authors who want a build corrected or removed can ask there,
|
| 79 |
+
and it will be done.
|
|
|