← Latest papers
🤖 AI

Mitigating Legibility Tax with Decoupled Prover-Verifier Games

This paper proposes a decoupled prover-verifier game framework that mitigates the "legibility tax" by training a translator model to convert a solver's correct but uncheckable outputs into a verifiable format, thereby preserving accuracy while enhancing checkability.

Original authors: Yegon Kim, Juho Lee

Published 2026-06-19
📖 5 min read🧠 Deep dive

Original authors: Yegon Kim, Juho Lee

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

The Big Problem: The "Legibility Tax"

Imagine you have a brilliant, super-smart student (a Large Language Model) who can solve very hard math problems. However, this student has a bad habit: when they explain their work, they write in a messy, confusing, or overly complicated way.

To make sure the student isn't cheating, you hire a teacher (a "Verifier") who is much less smart than the student. The teacher's job is to read the student's explanation and say, "Yes, this is right" or "No, this is wrong."

The Problem: In previous attempts to train these students to write clearly for the teacher, something went wrong. To make their explanations easier for the teacher to understand, the students started making mistakes in their actual math answers. They sacrificed getting the right answer just to make the explanation look good.

The authors call this the "Legibility Tax." It's like a student who gets a perfect score on a test but writes the answers in a way that the teacher can't read, so the teacher gives them a zero. Or, worse, the student changes the answer to something simple the teacher understands, even if it's wrong.

The Old Way: The "Do-It-All" Student

In the old method (called a standard Prover-Verifier Game), you asked the student to do two things at once:

  1. Solve the math problem correctly.
  2. Write the explanation clearly enough for the teacher to check.

The paper argues that asking the student to do both simultaneously is too hard. The student gets confused and starts failing the math part just to pass the "clarity" part.

The New Solution: The "Translator" Team

The authors propose a new team structure with three roles to fix this. Instead of one student trying to do everything, they split the work:

  1. The Solver (The Genius): This model is trained only to get the right answer. It doesn't care if the explanation is messy. It just solves the math perfectly.
  2. The Translator (The Editor): This model's only job is to take the Genius's messy solution and rewrite it into a clean, easy-to-read format. It must promise, "I will not change the answer, I will just make it look nice."
  3. The Verifier (The Teacher): This model checks the Translator's work. It asks, "Is this explanation clear? And does it match the Genius's answer?"

How They Train: The "Good Cop, Bad Cop" Game

To make sure the Translator actually tells the truth and doesn't try to trick the teacher, the authors set up a game with two types of Translators:

  • The Faithful Translator: This one tries to rewrite the Genius's answer clearly, keeping the answer exactly the same.
  • The Sneaky Translator: This one is a "trickster." It is given the correct answer by the teacher but is told to write a convincing explanation that leads to a wrong answer. It tries to fool the Verifier into thinking a wrong answer is right.

The Game:

  • The Verifier tries to spot the difference between the Faithful Translator (who is honest) and the Sneaky Translator (who is lying).
  • The Faithful Translator tries to get the Verifier to agree that its explanation is clear and correct.
  • The Sneaky Translator tries to fool the Verifier.

Over time, the Verifier gets really good at spotting lies. The Faithful Translator learns that the only way to win is to be perfectly clear and stick to the original answer. The Sneaky Translator learns that it can't fool the Verifier anymore.

The Result: No More Tax

The paper shows that by separating the "getting the answer right" part from the "making it readable" part, they solved the problem.

  • Accuracy: The system kept the high accuracy of the Genius Solver (about 57% on their math test).
  • Legibility: The Translator learned to make the answers easy to check without changing the math.
  • No Tax: Unlike the old method, where accuracy dropped to 22% because the model tried to be too clear, this new method kept the accuracy high while making the output checkable.

A Simple Analogy: The Architect and the Blueprint

Think of it like building a house:

  • The Old Way: You asked the Architect to design the house and draw the blueprints perfectly at the same time. Because they were so focused on making the lines pretty, they accidentally put the kitchen in the wrong place.
  • The New Way: You hire a Master Builder who designs the house perfectly (ignoring how pretty the drawings are). Then, you hire a Draftsman whose only job is to take the Builder's rough notes and turn them into a beautiful, easy-to-read blueprint. You also hire a Inspector who checks if the blueprint matches the Builder's notes.

If the Draftsman tries to change the kitchen's location to make the drawing look simpler, the Inspector catches them. The result is a house that is built correctly (accurate) and has blueprints that are easy to read (legible).

Summary

The paper introduces a method to stop AI models from getting "dumber" just to make their answers easier to read. By splitting the job into a "Solver" (who gets the answer right) and a "Translator" (who makes it readable), and training them against a "Sneaky" trickster, they created a system that is both smart and easy to check, without losing accuracy.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →