Mathematical-Reasoning

TL;DR for operators When a compact model fails on a difficult multi-step problem, the default remedies are expensive: use a larger model, generate many independent attempts, or accept lower accuracy. This paper tests a different allocation of compute—keep the solver small, but give it localized guidance at difficult intermediate steps. HintMR1 separates those jobs. A hinter tells the solver what to consider next without supplying the full solution; the solver then advances its reasoning one step at a time. On AIME-2024, DeepSeek-R1-Distill-Qwen-7B rises from 20.69% accuracy without hints to 68.97% with GPT-5.2-generated hints. The result is not evidence that any second model helps: non-fine-tuned small-model hints are inconsistent and sometimes reduce accuracy below the no-hint baseline. ...

TL;DR for operators Zhijie Wang’s GRPO and Reflection Reward for Mathematical Reasoning in Large Language Models1 offers two practical signals for teams tuning reasoning models. First, additional post-training stages do not compose automatically. On Qwen2.5-Math-7B, the base model scores 58.6% on MATH-500, supervised fine-tuning reaches 66.2%, and reinforcement learning applied directly to the base model reaches 73.8%. Yet the model that receives supervised fine-tuning before reinforcement learning falls to 57.6%. The authors attribute this weakness mainly to differences in the size and distribution of the datasets used at the two stages. ...

TL;DR for operators A post-training team with a fixed budget can spend it on long worked solutions or on shorter labels aimed at the decision that determines the rest of the reasoning path. Wang and Zhang’s study1 provides evidence that, for mathematical word problems, the second option deserves serious consideration. The authors classify more than 90% of analyzed model failures as mistakes in selecting the relevant quantities, dependencies, or operation. Those errors remain dominant after conventional chain-of-thought supervised fine-tuning. Their alternative, First-Step Logical Reasoning (FSLR), trains the model only on that initial planning decision. Across the reported experiments, it generally beats matched full-trajectory fine-tuning, including under distribution shift, while using roughly 81-87% fewer supervised training tokens and approximately four- to sixfold less training time. ...

TL;DR for operators A model reads a chart, diagram, or photographed math problem and produces the wrong answer. Treating that event as a generic “reasoning failure” can send engineering effort to the wrong component. The model may have misread a number, attached a label to the wrong object, confused a scale or unit, or reasoned incorrectly after extracting the right facts. ...

TL;DR for operators Two new papers point to the same operational lesson from different sides: long reasoning becomes useful only when its intermediate steps are made explicit, scoped, and checkable. HIPIF tackles the training side of long-horizon agents: it teaches an LLM agent to break tasks into subgoals, fold completed progress into compact memory, reflect on whether a subgoal is done, and use local process rewards to reduce repeated or ungrounded behavior.1 Mask-Proof tackles the evaluation side: it turns research-level mathematical proofs into masked-step tasks where a model must reconstruct a critical formula from self-contained context, then uses a semantic-equivalence judge with repeated voting to grade the result.2 ...

A spreadsheet error rarely announces itself with dramatic music. It usually arrives politely. A pricing model gives a clean answer. A compliance calculator writes a confident explanation. A financial assistant produces a neat derivation with enough intermediate steps to look reassuring. The result is formatted, fluent, and possibly wrong. That is the uncomfortable business lesson behind Mathematical Reasoning in Large Language Models: Benchmarks, Architectures, Evaluation, and Open Challenges, a 2026 survey of roughly 120 studies on LLM mathematical reasoning.1 The paper is not introducing one new benchmark, one heroic model, or one more leaderboard trophy to place on the already overcrowded mantelpiece. Its useful contribution is more structural: it connects datasets, representations, training methods, tool use, verifiers, and evaluation metrics into one reasoning pipeline. ...

A coding agent can fail in two very different ways. One failure is obvious: it does not think enough. It sees an error report, guesses the wrong file, edits too early, and then spends the rest of the trajectory debugging its own mistake. Anyone who has watched an autonomous coding agent wander through a repository has seen this little tragedy. The machine is busy, but not necessarily useful. ...

Spreadsheet errors have a special talent: they look boring until they become expensive. That is the business version of the LLM math problem. A model can produce a calm, step-by-step explanation, put a confident number at the bottom, and still be wrong in the only place that matters. Worse, the reasoning may look plausible enough that a manager, analyst, tutor, or compliance reviewer nods and moves on. The answer has the rhythm of thinking. It has the costume of calculation. It may even have a chain-of-thought trace. Very civilized. Still not proof. ...

Think Longer, Act Worse? What M2A Teaches About Reasoning Agents A coding agent does not fail only because it cannot think. Sometimes it fails because it keeps thinking after it should inspect the repository. Sometimes it writes a plausible explanation before checking the relevant file. Sometimes it burns the context window by wandering through hypotheses, each one almost reasonable, none of them decisive. The result is not stupidity in the familiar sense. It is a coordination failure: the model does not know when to reason, when to call a tool, when to absorb feedback, and when to edit. ...

Opening — Why this matters now The AI industry has discovered a wonderfully pedestrian way to misread progress: build models that can solve harder math problems, then grade them with evaluators that panic when 2040 minutes is not written as 34 hours. That is not a joke. It is the central irritation behind “Rethinking Math Reasoning Evaluation: A Robust LLM-as-a-Judge Framework Beyond Symbolic Rigidity”, an arXiv paper that examines how mathematical reasoning benchmarks can be distorted by rigid symbolic verification.1 ...