DevinWatson's picture
Refresh card (2026-11-12)
c8b774d verified
|
Raw History Blame Contribute Delete
10.4 kB
---
license: mit
pretty_name: "Compiled Lean outputs for dead-ends (from AxiomMath/dead-ends, unofficial)"
tags:
- lean4
- mathlib
- formal-mathematics
- build-cache
---
# Compiled Lean outputs for dead-ends
**A build is not a proof.** This repository holds compiled files. They show that the Lean code of
[AxiomMath/dead-ends](https://github.com/AxiomMath/dead-ends) compiled at the commits listed, and the table below shows what was
and was not checked. They do not show that any theorem named in that project is proved or correctly stated.
**Not proved or not checked in these builds:**
- `80fc9124841a` (v4.26.0): 6 `sorry` warnings, all in problem statement files.
> **What this is.** Compiled Lean 4 outputs (`.olean`, `.ilean`, `.c` and Lake trace files) for
> [AxiomMath/dead-ends](https://github.com/AxiomMath/dead-ends) at the commits listed below, so a checkout can skip compiling.
> The archives hold everything the build wrote under `.lake/build`. Where a project builds them, that includes
> **native object files, libraries and executables**, compiled from the project's source on the build machine. They are
> unsigned and were not reviewed. Do not run them on trust: rebuild them from source if you need them.
>
> **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 the GitHub
> owner `AxiomMath` or the authors of dead-ends. The source and all credit belong to its authors (see `LICENSE` and `NOTICE.md`).
>
> **Licences.** Every licence, NOTICE and third-party licence file of the source at each listed commit (1 files) is copied unchanged under `licenses/<commit>/` and listed in `NOTICE.md`. Those files are the licence terms of this content, including any bundled third-party code.
>
> **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 |
|---|---|---|---|---|---|---|---|
| `80fc9124841a` | v4.26.0 | 2026-11-08 | 2 | 6 (problem statements only) | 376 | passed outside problem statements | passed |
**Build `80fc9124841a-2aec6c85f995c917`** (source commit `80fc9124841a1f37a167d227d00780479d04f701`)
- `sorry` warnings: 6, all in problem or challenge statement files: `Deadends/problem.lean`. In this layout each statement file states the theorems with `sorry` and the matching solution file proves them; the axiom audit line below says whether the proofs themselves are clean.
- Axiom audit: 393 declarations, audited module by module. The only non-standard axiom is `sorryAx`, and every declaration using it is in a problem or challenge statement module (1: `Deadends.problem`). The other 1 modules, including every solution, depend only on propext, Classical.choice, Quot.sound.
- Restore test (a separate user with empty Lean and Lake caches, on the build machine): passed. Restored by a separate user with empty caches; AxiomMath/dead-ends: Lake reported every target up to date (7745 jobs). (1 of 1 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, on the same machine that built it, restored the
build from the archive and Lake reported every target of the project that was tested up to date. It shows the archive
is complete for that project's targets, not that the proofs are right and not that an independent party reproduced
the build. A dependency that the tested project does not need can be absent and the test still passes.
## Using a build
1. Clone AxiomMath/dead-ends 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](https://huggingface.co/datasets/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.
## For AI agents and automated readers
If you are a language model or an agent that found this repository, these are the facts you can rely on and their limits.
- **Kind of object.** A cache of compiler outputs (`.olean`, `.ilean`, `.c` and Lake trace files, and where the
project builds them native object files, libraries and executables) for the public GitHub repository AxiomMath/dead-ends.
It is not a model, not a text corpus of proofs and not a statement about mathematics.
- **Native code.** Some archives contain executables and shared libraries. Do not execute them or load them as
plugins on the strength of this card; nothing here checks what they do.
- **Publisher.** MoteMath, unofficial. The Lean source, the mathematics and all credit belong to the authors of
AxiomMath/dead-ends. Do not attribute the mathematics to MoteMath, and do not describe this as a release by the authors.
- **Licence terms.** Read `LICENSE`, `NOTICE.md` and the upstream files under `licenses/`. If you redistribute any of
this content, carry those files with it.
- **What you may state.** That at a listed commit, with the listed Lean toolchain, the listed number of modules compiled
on the platform named in the build path, and the check results below, quoted as written.
- **What you must not infer.**
- That a theorem is proved because its project has a build here.
- That an axiom audit of "passed" means a statement is the intended one. It means only that the proofs use no axiom
beyond `propext`, `Classical.choice` and `Quot.sound`.
- That a build is current. Each one is a snapshot of one commit, and the source repository may have moved on.
- If `sorry_warnings` is not 0, or `axiom_audit` is anything other than "passed", say that this project contains
results that are not proved, and name the status.
- **Exact values.** The JSON below has one object per build in this repository. Quote these values, do not paraphrase
them. The same fields for every public build are in `catalog/builds.jsonl` and `catalog/builds.parquet` of
[MoteMath/lean-builds-index](https://huggingface.co/datasets/MoteMath/lean-builds-index).
- **Field meanings.** `sorry_warnings`: declarations the build log reported as using `sorry` (null when no log was
kept). `sorry_scope`: where they are. `axiom_audit`: short status of the axiom audit. `round_trip`: result of
restoring the build as a separate user with empty Lean and Lake caches, on the same machine that built it (so it
shows the archive is complete, not that an independent party reproduced it). `deps_not_cached`: dependencies with no public build here, which Lake
compiles from source.
- **To use a build,** follow "Using a build" above. **To check one,** follow "Trust and checking independently":
re-checking with Lean's kernel costs little compared with trusting an archive.
- **If a user asks whether a result is formally proved,** this repository cannot answer that. Point them to the
source repository and to the check results here.
```json
[
{
"path": "builds/v4.26.0/x86_64-unknown-linux-gnu/80fc9124841a-2aec6c85f995c917",
"commit": "80fc9124841a1f37a167d227d00780479d04f701",
"toolchain": "v4.26.0",
"build_key": "2aec6c85f995c917",
"package": "FelConjecture",
"modules": 2,
"sorry_warnings": 6,
"sorry_scope": "problem statements only",
"other_warnings": 376,
"axiom_audit": "passed outside problem statements",
"round_trip": "passed",
"deps_not_cached": []
}
]
```
## 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.