The Mathlib port is already underway: for programmers

See actual imported mathematical proofs being checked by Osprey, with each theorem's assumptions made visible.

For programmers. Choose the other audience version or browse the complete series.

The Mathlib port is already underway: for programmers (2:46). Captions are on; choose a chapter to jump to it.

Lean is the development oracle for compatible proofs; Osprey checks them independently. Known unsound reference behaviour must be refused, and changing a discipline requires fresh proof validation.

What this demonstrates

The films record an earlier selection of supporting lemmas; the dated progress guide records the current public corpus separately. These are checked exports from Lean developments, not a completed port of Mathlib or the headline research theorems.

Read the guide and try it yourself. Osprey is actively evolving; the guide distinguishes the recorded demonstration from current corpus progress.

Actual source

Continue learning

Use the Workbench · Current Mathlib port evidence · All twelve films

Transcript

  1. Mathlib is a library of mathematical definitions and proofs built for Lean, a proof assistant. Think of it as reusable mathematics with evidence attached. Osprey's port is underway: an actual Mathlib module is now going through the importer.
  2. Mathlib saves you from rebuilding mathematics before proving something useful. Lean provides a reference for comparison; Osprey checks the imported evidence itself. Known soundness bugs must not become rules. Osprey's pluggable checker protocol keeps theories separate. Safe theory forks, with fresh checks of affected proofs, are part of the completion milestones.
  3. Here is one of the recorded Lean export files. It contains declarations, names, and proof terms, plus the information needed to interpret them. The repository preserves the file and its origin. We can replay the data through Osprey instead of asking you to trust a screenshot.
  4. Now run the actual Osprey-built checker. It accepts three recorded Lean proofs: swapping the order of two facts, reversing an equality, and showing that a statement is equivalent to itself. Those lines come from execution; the public corpus covers 194 statements.
  5. Here is a real arithmetic result. For every pair of natural numbers, adding them in either order gives the same answer. Osprey checks Lean's proof of that rule, including the definitions it uses. This checks evidence for every natural number, rather than testing a few chosen inputs.
  6. This imported lemma checks a loop's work counter. For any input width, the counter is exactly three times that width, plus one. The Workbench shows the actual statement and its checked result. It also names the proof's assumption: propositional extensionality. These are supporting lemmas; the headline research results remain separate work.
  7. The second result deliberately corrupts the arithmetic proof. Osprey rejects it with a type mismatch. Keeping that failure beside the accepted proof checks a useful boundary: changing the proof cannot simply leave a success badge behind. It does not prove the checker has no bugs.
  8. These selected proofs run under garbage collection, reference counting and WebAssembly. We are now bringing in Euclid's theorem: there are infinitely many primes. Osprey reads its exported proof, but the last full check did not finish. We have isolated a smaller part that checks. The guide tracks the next steps.