Sovereign 8s.is mirror of standardgalactic/formal-math
  • Lean 99.3%
  • Python 0.5%
  • Ruby 0.1%
  • Shell 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
ecprice-ant e1a4e65081
Some checks failed
Lean projects / detect changed projects (push) Has been cancelled
Add 3sum-apsp: formalization of "Truly Subquadratic 3SUM and Truly Subcubic APSP via Triangles in Sparse Lopsided Graphs" (#28)
* CI: take lean4export's vX.Y.0 tag when a Lean patch release has no tag of its own

For a project on a stable patch release vX.Y.Z (Z > 0), if
leanprover/lean4export has no tag vX.Y.Z, the check takes the tag vX.Y.0 and
builds it with the project's toolchain. Release candidates do not fall back.
A project whose exact tag exists is checked as before. The cache key of the
tools now includes the toolchain.

* Add 3sum-apsp: Lean 4 formalization accompanying "Truly Subquadratic 3SUM and Truly Subcubic APSP via Triangles in Sparse Lopsided Graphs"

A self-contained Lake project (Lean v4.33.1, Mathlib v4.33.1) in 3sum-apsp/.
EndStatement.lean states five headline claims about programs of a word RAM;
PaperStatements.lean states further results of the paper item by item;
ThreeSumApsp/ proves them. Two Comparator configurations list the compared
theorems. 3sum-apsp/README.md says what is proved and what is not.
Adds the project's row to the table of the root README.
2026-10-05 21:00:29 -07:00
.github Add 3sum-apsp: formalization of "Truly Subquadratic 3SUM and Truly Subcubic APSP via Triangles in Sparse Lopsided Graphs" (#28) 2026-10-05 21:00:29 -07:00
3sum-apsp Add 3sum-apsp: formalization of "Truly Subquadratic 3SUM and Truly Subcubic APSP via Triangles in Sparse Lopsided Graphs" (#28) 2026-10-05 21:00:29 -07:00
zeta23 Merge pull request #24 from anthropics/zeta23-authorship 2026-08-28 14:37:34 -07:00
.gitignore Root .gitignore: ignore Lake build artefacts repo-wide 2026-08-27 21:16:09 -05:00
LICENSE Initial release: Lean 4 formalization accompanying "More than two thirds of the zeros of the Riemann zeta function lie on the critical line" 2026-08-07 02:17:33 +00:00
README.md Add 3sum-apsp: formalization of "Truly Subquadratic 3SUM and Truly Subcubic APSP via Triangles in Sparse Lopsided Graphs" (#28) 2026-10-05 21:00:29 -07:00

formal-math

Machine-checked Lean 4 formalizations published by Anthropic. Each subdirectory is a self-contained Lake project with its own toolchain pin, README and build instructions; build from inside the subdirectory. Projects follow the layout of the Palomar submission template (Challenge.lean / Solution.lean / comparator.json / formalization.yaml at the project root) and are submitted to Palomar with the subdirectory as the selected project; the licence file Palomar reads is this repository's root LICENSE.

Project Statement Lean / Mathlib
zeta23/ More than two thirds of the zeros of the Riemann zeta function are simple and on the critical line (Alpöge–Furman, arXiv:2608.13637) leanprover/lean4:v4.33.0-rc2 / Mathlib v4.33.0-rc2
3sum-apsp/ Programs of a word RAM solve 3SUM in O(n^1.9992) steps and the (min,+)-product and APSP in O(n^2.99942) steps, on integers of polynomial size; also bounds for Exact Triangle and Zero-Weight k-Clique, and further results of the paper, item by item (Alman–Vassilevska Williams, arXiv:2610.06783) leanprover/lean4:v4.33.1 / Mathlib v4.33.1

CI

Pull requests and pushes to main run .github/workflows/lean-projects.yml on each project folder whose files changed, and only on those; a change confined to CI configuration or documentation (.github/, this README, ...) verifies nothing, and a full run of every project is started manually from the Actions tab (workflow_dispatch, projects = all). The verify job runs on the runner label in the repository/organization variable LEAN_CI_RUNNER when it is set (e.g. a GitHub larger runner such as ubuntu-latest-16-cores), otherwise on ubuntu-latest. Pull-request runs reuse the project's previous Lake build for the same toolchain and manifest (only changed modules are rebuilt); merges to main and manual runs build from scratch. A project passes when lake build succeeds on its pinned toolchain with no sorry outside the trusted comparator statement files (Challenge.lean, Challenge/<Topic>.lean), and when the Palomar registry's acceptance check — leanprover/comparator with a toolchain-matched lean4export, the independent nanoda kernel and the landrun sandbox, at the registry's tool pins — prints Your solution is okay! for every comparator configuration the project declares (.github/scripts/comparator-check.sh; run it locally with cd <project> && bash ../.github/scripts/comparator-check.sh).

To add a project: create a top-level directory with lakefile.toml (or lakefile.lean), lean-toolchain, lake-manifest.json, a Mathlib-only Challenge module stating the headline theorems, a Solution module proving them from the library, and at least one comparator configuration (comparator.json next to the lakefile, or comparator/config*.json); add a row to the table above.

License

Apache-2.0 — see LICENSE. Individual projects may carry additional NOTICE files.