Act 3 · Frontier & Caveats
16. Wrap-Up: What You Now Know
The past fifteen pages are a small but mighty snapshot of what inference-time scaling is under the hood. Reasoning turned out to be one knob that can be turned many different ways, and that can even be moved from one axis to another. Here is every lever on the first axis, measured on the same problems the pages showed you. Then ten questions, to see whether the mechanisms landed rather than whether the numbers stuck.
1. The whole toolbox, on one axisour runs · 100 problems · pages 5 to 11
Each page measured its own lever against its own baseline, so none of them could draw this. Now that all of them are behind you, they go on one axis, priced in the compute they actually spent.
Read it top to bottom as steps that keep getting smaller. Writing the reasoning at all is the largest single move on the chart, and being made to write more of it is the only step that goes backwards.
Every chain above was written by Qwen2.5-3B. One model wrote all of it. What changes down the chart is how many chains it was allowed to write and what got to pick between them, never who was writing; where a judge appears it scores chains, it does not write them. The run behind each rung is linked at the top of this page, traces included, so any of them can be re-derived without a GPU.
1b. Conclusionssix things the chart is evidence for
1.Letting the model reason wins, every time
Ask for the answer on its own and it mostly gets it wrong. Let it write its working first, on the same problems, and it gets far more of them right. But making it write more working, when it has nothing new to go on, is a different thing: it costs a great deal more and turns about as many answers wrong as it turns right. Reasoning is worth having. It is not worth forcing.
2.The answer is usually already in the pile
Ask the same question many times and a right answer turns up far more often than any rule we tried managed to pick out. The gap between what was found and what was chosen is not a thinking problem, and sampling harder does not close it.
3.So the judge is the bottleneck, and judges can barely read
Something has to choose. An arithmetic checker can only mark the small part of a chain that is arithmetic, and the rest is prose it cannot read at all. Meanwhile the more variety you buy by sampling, the worse every model asked to judge gets, while a model trained to score holds steady. So you want a trained judge. But sampling and judging your way to what a bigger model reaches on its own costs many times more compute than simply using the bigger model.
4.Adaptive compute is where that points, not where it lands
Spend more on the hard questions and less on the easy ones, rather than the same on all of them. That is the obvious next move, and this deck could not make it pay: even picking the best stopping point for each question with hindsight bought no more per unit of compute than plain resampling. Knowing where to spend only helps if you can know it in advance.
5.And you pay for every node you look at
Branching through partial chains and cutting the bad ones sounds cheaper than it is. You pay for a branch before you can judge it, so pruning never refunds what looking cost. It has no bar here because this deck never ran it, and running it would mean holding a second, larger model in memory beside the one doing the writing.
6.And the biggest move in this story is not on this axis
The largest jump in the whole deck came from none of the levers on this chart. It came from taking a small model and training it on the reasoning of a much stronger one. It is not a bar here because it was not the same test: the published result covers every difficulty level and this chart is only the hardest ones, and our own models score noticeably higher on the easier mix. So part of that gap is the easier test and part is the training, and this deck cannot tell you how it splits.
2. Ten questionsconcepts, not numbers
In the deck's order. Each answers itself as soon as you pick, and says which page it came from. The options are shuffled on every visit, so where an answer sat last time tells you nothing. Nothing here needs a number memorised: where a figure appears it is the setting the question is asked in, not the thing being asked.
0 right of 0 answered, 10 in all