ImProver 2: Iteratively Self-Improving LMs for Neurosymbolic Proof Optimization
The paper introduces ImProver 2, a neurosymbolic framework that combines data-efficient expert iteration with a structural scaffolding system to enable small language models to effectively optimize complex formal proofs in Lean 4, outperforming significantly larger models while establishing proof optimization as a scalable, learnable task.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you have a massive, growing library of mathematical proofs. These aren't just stories; they are rigid, computer-checked blueprints that prove things are true. Recently, computers (specifically AI) have started helping humans write these proofs, causing the library to explode in size.
But there's a problem: The library is getting messy. Some proofs are correct but written in a confusing style, others are too long, and some rely on a huge list of other rules that make them hard to maintain. It's like having a house where the plumbing works, but the pipes are tangled, the walls are painted in clashing colors, and you need to carry a backpack full of extra tools just to turn on a light.
Enter ImProver 2.
Think of ImProver 2 as a super-organized, self-improving librarian who doesn't just shelve books but rewrites them to be better. Its job is to take a correct proof and rewrite it to be shorter, cleaner, or more modular, without breaking the math.
Here is how it works, using some simple analogies:
1. The "Practice Makes Perfect" Loop (Iterative Self-Improvement)
Usually, to teach a computer to do a task, you show it thousands of examples written by humans. But for proof optimization, good examples are rare.
ImProver 2 solves this by teaching itself.
- The Draft: It takes a proof and tries to rewrite it in many different ways (like a writer brainstorming 10 different endings for a story).
- The Grading: It checks which rewrites are still mathematically correct. Then, it scores them based on what we want: Is it shorter? Does it use fewer external references? Is it broken into clearer steps?
- The Lesson: It compares its "winning" rewrites against its "losing" ones. It learns, "Oh, when I did this, the proof got shorter and stayed correct. When I did that, it broke."
- The Replay Buffer: To prevent the AI from forgetting what it learned or getting stuck in a loop of bad ideas, it keeps a "memory bank" of old good examples mixed with new ones. This ensures it keeps getting better over time, rather than just repeating the same mistakes.
2. The "Neurosymbolic Scaffold" (The Training Wheels)
Imagine trying to fix a complex engine without a manual or a diagram. It's hard. Now imagine having a diagram that highlights exactly which part you are working on, explains what that part does in plain English, and lists the tools you need nearby.
ImProver 2 gives the AI this "diagram" for every proof. This is called Neurosymbolic Augmentation. It provides:
- The Map: It shows the current state of the proof (what is proven so far, what is left to do).
- The Context: It pulls up the specific definitions and rules relevant to that specific proof, so the AI doesn't have to guess.
- The Translation: It gives a "plain English" summary of what the proof is trying to do, helping the AI understand the goal before it starts writing the code.
This "scaffold" helps even small, less powerful computers perform like much larger, smarter ones.
3. The Three Goals (Metrics)
The librarian doesn't just want the proof to be "correct." It wants to optimize for specific qualities, like a chef adjusting a recipe:
- Length (The "Golf" Metric): Just like in golf, the goal is to get the ball in the hole with the fewest swings. ImProver 2 tries to shorten proofs by removing unnecessary steps.
- Dependencies (The "Self-Contained" Metric): Imagine a recipe that says "add the secret sauce from the neighbor's house." That's a dependency. ImProver 2 tries to rewrite proofs so they don't rely on so many external "neighbor's sauces," making them easier to understand and use on their own.
- Modularity (The "Lego" Metric): A messy proof is like a giant block of clay. A modular proof is like a set of Legos—small, distinct, reusable pieces. ImProver 2 tries to break big proofs into smaller, independent sub-proofs (like "have h1," "have h2") so the logic is clearer.
The Results: Small is Mighty
The most surprising finding is that ImProver 2 took a small AI model (7 billion parameters) and trained it to be better at these tasks than massive AI models (some with hundreds of billions of parameters) that were not given this special training.
It's like taking a compact, efficient sports car and tuning its engine so perfectly that it beats a massive, heavy truck in a specific race, even though the truck has a bigger engine. The small model, when given the right "scaffold" and the right "practice loop," learned to restructure complex mathematical arguments better than the giants.
In summary: ImProver 2 is a system that teaches small AI models to be expert proof editors. By giving them a clear map of the problem and letting them learn from their own best attempts, it can clean up messy mathematical libraries, making them shorter, cleaner, and easier to maintain, all without needing the most expensive, massive supercomputers.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.