DevinWatson's picture
Add builds (2026-11-10)
0b6faf2 verified
|
Raw History Blame
5.06 kB
metadata
license: apache-2.0
pretty_name: >-
  Compiled Lean outputs for PrimeGapsLib (from AxiomMath/PrimeGapsLib,
  unofficial)
tags:
  - lean4
  - mathlib
  - formal-mathematics
  - build-cache

Compiled Lean outputs for PrimeGapsLib

What this is. Compiled Lean 4 outputs (.olean, .ilean, .c and Lake trace files) for AxiomMath/PrimeGapsLib at the commits listed below, so a checkout can skip compiling.

What this is not.

  • Not a check of the mathematics. These files show that the code compiled. They do not show that the Lean statements faithfully formalize the results they are named after, and nobody here reviewed them as mathematics.
  • Not an official release. Built and published by MoteMath; not affiliated with or endorsed by AxiomMath or the authors of PrimeGapsLib. The source and all credit belong to its authors (see LICENSE and NOTICE.md).

How it was made. By an automated, AI-assisted build pipeline on cloud machines, from the public source at each listed commit. The build log and every report are in each build folder under reports/.

Builds and what was checked

Every value below is read from the build folder's own reports; "not run" and "not recorded" mean exactly that.

commit Lean packed modules sorry warnings other warnings axiom audit round trip
1faa7b14e82d v4.33.0-rc1 2026-11-08 412 0 0 passed passed

Build 1faa7b14e82d-f5c1c2b4f3938cb9 (source commit 1faa7b14e82ddebc2772dfb9153922f01b106477)

  • No sorry warnings in the build log.
  • Axiom audit: 15199 declarations; every one depends only on propext, Classical.choice, Quot.sound.
  • Round trip on a clean machine: passed. Restored on a clean machine; AxiomMath/BGP212: Lake reported every target up to date (4433 jobs). (2 of 2 projects using it passed; checked 2026-11-09)

What the columns mean:

  • sorry warnings: declarations the build reported as using sorry. Anything depending on them is not proved. "problem statements only" means every one is in a problem.lean or challenge file: in that layout the statement file states the theorems with sorry, a matching solution file proves them, and a comparator checks that the two match. The axiom audit then shows whether the solutions are clean.
  • Axiom audit: every declaration in the package's modules traced to the axioms it uses. "passed" means only propext, Classical.choice and Quot.sound. "passed outside problem statements" means a module-by-module audit found sorryAx only in problem or challenge statement modules, and every other module, including every solution, uses only those three. Neither says a statement is the intended one: a theorem that takes a hard fact as a hypothesis passes.
  • Round trip: a separate user with empty Lean and Lake caches restored the build from the archive and Lake reported every target up to date. It shows the archive is complete, not that the proofs are right.

Using a build

  1. Clone AxiomMath/PrimeGapsLib at the build's commit and run lake exe cache get, which fetches Mathlib from Mathlib's own cache and checks out the dependencies.
  2. Get lbc.py from MoteMath/lean-builds-index (tools/lbc.py, about 700 lines of Python; read it before running it). It needs Python 3.10+, zstd and huggingface_hub.
  3. Fetch as little as you need:
    • python3 lbc.py fetch . --module Some.Module downloads only the shards holding that module and its import closure. Repeat --module for several, and add --dry-run to see the size first.
    • python3 lbc.py fetch . downloads every shard of every package with a published build.
  4. Run lake build --no-build +Some.Module (or lake build --no-build after a full fetch). It must report everything up to date; --check on the fetch does this for you.

Each build folder holds manifest.json (commit, toolchain, dependency closure, shard hashes), the exact lake-manifest.json used, deterministic shards/*.tar.zst with a per-file SHA-256 index, and reports/.

Trust and checking independently

  • The SHA-256 hashes show a download is intact and matches what was published here. They come from the same publisher as the files, so they are not evidence that the files are honest.
  • Lean does not re-check .olean files when it loads them. A tampered file could contain a theorem with no valid proof.
  • To check independently, use either route:
    • re-check the compiled environment with the kernel: lake env lean4checker --fresh Some.Module (lean4checker replays every declaration through Lean's kernel);
    • or rebuild from the source commit and compare.
  • For anything you rely on, prefer one of these over trusting the archive.

Questions, corrections and removal

Open a discussion in this repository's Community tab. Authors who want a build corrected or removed can ask there, and it will be done.