Formally Solving Answer-Construction Problems in Lean
This paper introduces ECP, a neuro-symbolic framework in Lean that combines tool-assisted general LLMs for enumerating candidate answers with prover LLMs for generating machine-checked proofs, effectively addressing the gap in formally solving mathematical answer-construction problems.
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 are taking a very difficult math contest. There are two types of questions you might face:
- The "Prove It" Question: The judge gives you a statement like "The sky is blue" and asks, "Can you prove this is true?" You just need to write a logical argument.
- The "Build It" Question: The judge asks, "Find the smallest number that satisfies these weird rules." You have to invent the number first, and then prove it works.
This paper is all about the second type: Answer-Construction. It's the difference between being a lawyer who argues a known case, and being an architect who has to design a building from scratch before proving it won't collapse.
The Problem: A Mismatch of Tools
The authors noticed a gap in how Artificial Intelligence (AI) handles these tasks.
- General AI (The "Big Brain"): Think of this as a brilliant, chatty professor. It's great at brainstorming, guessing numbers, and doing rough math. But if you ask it to write a formal, machine-perfect proof, it often gets lazy, makes up facts, or writes code that doesn't compile. It's also very expensive to hire.
- Prover AI (The "Strict Editor"): Think of this as a tiny, hyper-focused robot trained only on writing formal proofs. It's cheap and great at checking logic, but it's terrible at guessing what the answer might be. If you ask it to "Find the number," it might just stare at the wall or guess a random number that doesn't work.
The Trap:
If you just ask the "Strict Editor" to solve a "Build It" problem, it might cheat. It could say, "The answer is 'the smallest number that satisfies the rules'." Technically, that's a valid answer in a computer's eyes, but in a real math contest, that's a circular cheat. You need a specific number, like 245. The computer needs to be forced to stop cheating and actually find the real number.
The Solution: ECP (Enumerate-Conjecture-Prove)
The authors built a new system called ECP (Enumerate-Conjecture-Prove). It acts like a three-person team working together to solve these "Build It" problems in a language called Lean (a computer proof assistant).
Here is how the team works, using a Detective Analogy:
1. The Detective (The General AI + Python Tools)
- Role: This is the "Big Brain" professor, but this time, they have a calculator and a computer to run code.
- Action: Instead of just guessing, the Detective writes a Python program to brute-force search for clues. They run loops to test thousands of small numbers to see which ones fit the rules.
- The "Conjecture": Based on the data, the Detective makes an educated guess: "I bet the answer is 245." They write down their reasoning in plain English.
2. The Gatekeeper (The Admissibility Checker)
- Role: This is the bouncer at the club.
- Action: Before the Detective's guess is allowed to move forward, the Gatekeeper checks it.
- Is it a real number? (Yes, 245 is a number).
- Is it cheating? (Did the Detective just say "the answer is the answer"? No.)
- Is it using forbidden words? (Did they use complex math symbols that aren't allowed in the contest? No.)
- If the guess fails this check, the Gatekeeper sends it back to the Detective to try again.
3. The Judge (The Prover AI + Lean Automation)
- Role: This is the "Strict Editor" robot.
- Action: Once the Gatekeeper approves the guess (245), the Judge takes over. The Judge ignores the "how we found it" part and focuses entirely on the "why it's true" part. It uses formal logic to prove, beyond any doubt, that 245 is indeed the correct answer.
- If the proof fails, the Judge sends it back to the Detective to try a different number.
The Results: Did it Work?
The authors tested this team on two famous math datasets: PutnamBench (university-level math) and MathArena (high school competitions like AIME).
- The Old Way: If you just asked the "Strict Editor" to solve these, it mostly failed or cheated by giving circular answers. If you asked the "Big Brain" to do it all, it got stuck on the formal proof part.
- The ECP Way: By splitting the work, the system solved 17 out of 346 difficult university problems and 18 out of 75 high school problems.
- Why it matters: It's not just about getting the right number; it's about getting a machine-verified proof that the number is correct and that the answer wasn't a cheat.
Summary
Think of ECP as a factory assembly line for math problems:
- Worker A (General AI) uses tools to dig for the answer.
- Inspector B (Gatekeeper) makes sure the answer is a real, non-cheating number.
- Worker C (Prover AI) builds the unbreakable bridge of logic to prove that number is right.
This approach bridges the gap between "guessing the answer" and "proving the answer," allowing AI to solve math problems that require both creativity and rigorous logic.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.