← Latest papers
🤖 machine learning

Ideas in Inference-time Scaling can Benefit Generative Pre-training Algorithms

This paper argues that the traditional dichotomy between autoregressive and diffusion models is misleading, proposing instead that generative pre-training should prioritize designing efficient inference procedures for sequence expansion and state refinement before selecting training objectives to overcome fundamental algorithmic limitations.

Original authors: Jiaming Song, Linqi Zhou

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

Original authors: Jiaming Song, Linqi Zhou

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 the world of AI image and text generation as a massive construction site. For years, the industry has been stuck arguing over two specific types of construction crews, thinking they are completely different species:

  1. The "One-Brick-at-a-Time" Crew (Autoregressive Models): These workers lay down one brick, then another, then another, building a wall from left to right. They are great at building long walls (like writing long stories), but they can't fix a mistake in the middle without tearing down the whole wall.
  2. The "Sculptor" Crew (Diffusion Models): These workers start with a giant block of noisy marble and chip away at it, refining the shape over and over until a statue emerges. They are great at making high-quality shapes, but they usually work on the whole statue at once rather than adding new parts.

The Paper's Big Idea:
The authors of this paper say, "Stop fighting over which crew is better. That's a fake argument."

They argue that the real difference isn't about who is building (the model type), but how they are building (the inference procedure). They propose we should look at two different ways to scale up AI efficiency:

  • Axis 1: Sequence Expansion (Adding more stuff): Making the wall longer or the story bigger.
  • Axis 2: State Refinement (Making existing stuff better): Polishing the statue or fixing a mistake in the middle of the wall.

The paper claims that the best future AI shouldn't just pick one crew; it should design the construction plan (inference) before hiring the workers (training). If your plan is flawed, no amount of training will fix it.

Here are the three main lessons from the paper, explained with everyday analogies:

1. The "Missing Instruction" Problem (The DDIM Fix)

The Scenario: Imagine you are a GPS app. You tell the GPS, "Take me from Point A to Point B." But the GPS only knows where you are now (Point A) and the current time. It doesn't know where you want to end up (Point B) or when you want to get there. It just guesses a direction based on where you are right now.

The Paper's Claim:
Current AI models (specifically "DDIM" samplers) often try to jump from a noisy image to a clear image in one big step. But the math they use is like that GPS: it doesn't know the "target time" (the destination). It tries to guess the jump without knowing where it's supposed to land.
The Fix: The paper says, "Just tell the GPS the destination!" By simply adding the "target time" as an input to the AI's brain, the model suddenly has the capacity to make a perfect, one-step jump to the final image. It's a tiny change in the instructions that makes the whole process work.

2. The "Poker Hand" Problem (Multi-Token Prediction)

The Scenario: Imagine you are trying to guess the next two words in a sentence: "The poker hand is a..."
If you guess the first word and the second word completely independently, you might guess "High" and "House." Individually, those words make sense. But together, "High House" isn't a real poker hand. You need to understand that "High" and "House" are linked.

The Paper's Claim:
Many modern AI models try to speed things up by guessing multiple words at once. But they often guess them independently, like rolling two dice separately. This breaks the connection between the words.
The Fix: The paper argues that if you want to guess multiple words at once, your AI needs to be trained to understand the relationship between them (the joint distribution). If you don't build that relationship into the guessing process, the AI will keep making weird combinations, and no amount of training data will fix the fundamental flaw in how it guesses.

3. The "Long Jump" vs. "Baby Steps" (Flow Maps)

The Scenario: Imagine you need to get from the bottom of a hill to the top.

  • Old Way: You take tiny, baby steps, checking your balance after every single step. This is slow and requires many steps.
  • New Way: You learn to take a giant, confident leap directly to the top.

The Paper's Claim:
Most current AI models are trained to take tiny, baby steps (local updates). They learn how to move a little bit, then a little bit more. The paper argues that for AI to be fast, it needs to learn Flow Maps.
Think of a Flow Map as a "teleportation guide." Instead of learning how to take one small step, the AI learns the direct path (the map) to jump from a messy state to a clean state in one or two giant leaps. Recent methods are starting to do this, and they are much faster because they stop taking baby steps and start taking long-range jumps.

The Bottom Line

The paper concludes that we need to stop obsessing over whether a model is "Autoregressive" or "Diffusion." Instead, we should ask:

  1. Does the plan allow the AI to add more content efficiently? (Sequence Expansion)
  2. Does the plan allow the AI to refine its work efficiently? (State Refinement)

If the AI's "construction plan" (inference) is missing key variables (like the destination time) or assumes things that aren't true (like words being independent), then the training will never work perfectly. Design the move first, then train the player.

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 →