Reasoning-Trace Collapse: Evaluating the Loss of Explicit Reasoning During Fine-Tuning
This paper identifies and quantifies "reasoning-trace collapse," a phenomenon where fine-tuning reasoning models on answer-only data causes them to lose valid intermediate reasoning steps despite maintaining correct final answers, and proposes a structural evaluation framework and loss-masking strategies to detect and mitigate this degradation.
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 hire a brilliant student who has been trained to always "show their work" on math tests. They don't just write the final answer; they write out every step of their logic in a special notebook before circling the result. This "showing work" is what makes them a reasoning expert.
Now, imagine you give this student a new set of homework problems. These new problems only have the final answers in the back of the book; they don't show the steps. You ask the student to practice on these new problems.
The Problem: The "Silent" Collapse
The paper argues that when the student practices on these "answer-only" problems, something strange happens. They start getting the right answers (so you think they are doing great), but they stop writing down their steps in the notebook. They start skipping the "show your work" part entirely, jumping straight to the answer.
The authors call this "Reasoning-Trace Collapse."
It's like a chef who used to write down a detailed recipe before cooking a dish. After being asked to cook many dishes where the recipe wasn't provided, the chef starts cooking the dishes perfectly but stops writing the recipes down. If you only taste the food (the final answer), you think the chef is still a great recipe-writer. But if you ask for the recipe, it's gone. The chef has lost the habit of "showing their work," even though the food still tastes good.
The Hidden Danger
The paper warns that if we only check the final answer (did they get the right number?), we miss this failure. The model looks successful, but it has lost the specific behavior that made it a "reasoning model" in the first place. It's a structural failure: the machine stopped producing the intermediate steps, even if the final result is correct.
The Solution: The "Masking" Trick
The researchers tested a few ways to fix this without needing a teacher to write out new recipes for every problem.
- The "Empty Box" Method: When giving the student the "answer-only" homework, they tried forcing the student to write an empty box where the steps should be, even if the box is blank. This didn't work well for everyone; some students still stopped writing steps.
- The "Teacher" Method: They hired a super-smart teacher to write out the steps for the homework problems first, then had the student copy them. This worked well for some students but was expensive and didn't work for everyone.
- The "Masking" Method (The Winner): This is the clever trick. When the student practices on the "answer-only" homework, the computer ignores the part where the steps should be when calculating the score. It only rewards the student for getting the final answer right, but it doesn't punish them for leaving the step-box empty.
Think of it like this: If you tell a child, "I don't care if you write the steps, just give me the right answer," they stop writing steps. But if you say, "I'm only going to grade the final answer, so don't worry about the steps for now," the child might still keep the habit of writing steps because they aren't being actively trained to stop doing it.
The paper found that this "masking" strategy was very effective. It allowed the models to learn the new tasks (get the right answers) without forgetting how to "show their work."
The Takeaway
The main message is simple: When we train these smart AI models on new tasks, we can't just look at whether they get the right answer. We have to check if they are still "showing their work." If we don't, we might end up with models that give correct answers but have forgotten how to reason through the problem, which is a big problem if we need to trust how they got there.
The authors also released a free tool called THINKPACK (like a universal translator for these models) to help developers check if their models are still writing down their steps or if they've fallen into this "silent collapse."
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.