Does scaling toward AGI depend on what System-1 lets System-2 execute?
AI has grown by paying for more: more parameters, more data, longer reasoning, more agents. We argue the next gains may come from deciding, cheaply and before paying, which of those interactions are worth it.
1Department of Automation and 2Department of Computer Science, Tsinghua University, Beijing
Every step costs. Most teach very little.
We call any exchange between an AI system and its data, its computation or the world an interaction. Interactions take different forms, but they share one awkward property: you pay before you see what you got.
A language model thinks
A prompt turns into a chain of reasoning tokens.
A robot or RL agent tries
A trajectory of states, actions and rewards.
An agent calls a tool
A search, a code run or an API call, and its result.
More interactions help, but each one helps less than the last. Reasoning tokens that don't change the answer, training runs that produce no learning signal, and robot steps that repeat what is already known all burn real resources. So the bottleneck is shifting. It is no longer only how many interactions a system can handle, but which ones are worth their cost.
The easy supply is running out
For a decade, the answer to "how do we get better?" was "collect more". That frontier is closing.
- Human data is finite. Pretraining already folds most recorded text into one model, and public text may be exhausted within this decade.
- Good data is scarcer still. The examples that teach the most are a small slice of that stock.
- Synthetic data trades quantity for coverage. It can refill the pool, but the space of things to synthesize is enormous. A robot alone would need scenes, objects, dynamics, lighting and sensors covered. The real question becomes which synthetic examples are worth making.
- Some interactions are slow by nature. In science, robotics and clinical work, data arrives one experiment or one measurement at a time. No amount of compute speeds up a chemical reaction.
- Self-improvement makes it sharper. An agent that learns after deployment and interacts indiscriminately spends its budget on experiences that teach it nothing.
Wasted effort, in one picture
Reasoning models are often trained with verifiable rewards: give the model a problem, let it try several times, and score each attempt automatically. Popular methods like GRPO learn by comparing attempts at the same problem against each other. If every attempt gets the same score, there is nothing to compare, and the model learns nothing from that problem.
Too easy
8 attempts paid for. Zero learning signal.
Too hard
8 attempts paid for. Zero learning signal.
Just right
Mixed results. This is the only one that teaches.
A large share of a typical training pool falls into the first two rows. If you could tell in advance which problems will be "just right", you could spend the generation budget only on those. The chance that a problem teaches anything follows from its pass rate and the number of attempts :
As the model improves, more problems drift toward a 100% pass rate and stop teaching. Predicting before generating is exactly System-1's job in this setting.
Physical systems face the same issue with higher stakes. Real-world trials can't be run in parallel for free, and they take real time. When a robot must generalize across many conditions, which conditions it practises matters as much as how many.
When AI starts teaching AI
We sketch a trend we call the super parrot hypothesis. It is an illustration of a direction, not an established history.
This trend makes the efficiency problem harder, not easier. Every self-generated example is paid for with the system's own compute, and many teach little: problems it already solves, reasoning tokens that don't change the answer, tasks it has already mastered. A system that teaches itself needs an internal sense of what is worth doing before it does it.
How can an AI know what an interaction is worth before it pays for it?
The research question behind this Perspective.
Our position: predict before you pay
A costly System-2 can't screen its own work: if judging an interaction cost as much as doing it, there would be nothing to save. So we give it a partner. A lightweight System-1 estimates each candidate's value, and the heavyweight System-2 runs only what passes. We call this conditional interaction, and it runs as a loop.
System-1
Predict
Score each candidate interaction by its expected usefulness. This is cheap.
System-1
Gate
Admit only candidates above a threshold that adapts to the budget.
System-2
Execute
Do the expensive work: reasoning, training rollouts, tool calls, real actions.
Both
Update
Real outcomes become System-1's training signal, so its judgment improves.
Then back to step 1, with a sharper System-1.
Because each system shapes the other, they have to be designed together. That is the core claim: a large part of the next advance may come from co-designing System-1 and System-2, rather than from scaling System-2 alone. System-1 decides what System-2 runs, which model runs it, how much it may spend, and what is kept in memory. System-2's results are how System-1 learns. Pairing them raises three decisions at scale:
Compute
Which prompts, tasks or requests deserve rollouts, trials or long chains of thought.
Storage
Which samples, buffers, caches and context entries are worth keeping.
Feedback
How expensive outcomes should correct the cheap judgment that chose them.
Co-design, not a cascade
Pairing a small model with a big one is not new. A static cascade trains a fast router once and sends the hard requests to a large model. That works when difficulty never changes. Here it does: what is useful for System-2 shifts with every update, so System-1 has to keep learning from System-2's results. The difference is feedback and joint optimization, not the number of models.
| Static cascade | Co-design | |
|---|---|---|
| System-1 is trained | Once, then frozen | Continuously, on System-2's outcomes |
| It predicts | Fixed difficulty of a request | Value relative to the current System-2 |
| It acts | At inference only, on one call path | In training and at inference, over compute and storage |
| Outcomes flow back | Never | Every round |
AlphaZero is the familiar precedent: its strength came from a policy-value network and a tree search that trained each other, not from deeper search alone. A stronger System-2 raises what can be achieved. A well-calibrated System-1 decides how much of it you get per unit of cost and latency.
The framework, piece by piece
Both systems are defined by their role, not their model family. System-1 takes a candidate (a prompt, a task, a query, a tool call) and returns a score, not a solution, at a cost . System-2 performs the interaction, and only on candidates System-1 admits.
- Represent. Each candidate becomes a compact embedding: a frozen language-model encoder for prompts, or a graph or transformer encoder over a task's structure for robots.
- Predict. A small model outputs a predicted value and its uncertainty. When costs are equal, the best way to use those outputs is to rank by the calibrated mean: executing the top by maximizes expected utility among all rules that see only the predictions.
- Gate. Admit candidates whose score clears a threshold . A controller nudges it to hold a target admission rate : .
- Execute. System-2 does the costly work on what was admitted. A small audit sample of rejected candidates is executed too, so System-1's misses can be detected.
- Learn. Outcomes are logged and used to refit System-1, while System-2 learns from the same outcomes.
The two systems learn on different clocks. Writing for System-2 and for System-1, one round of co-design is a refit of System-1 followed by a gated step of System-2:
Neither update is defined without the other. System-1 adapts quickly to realized outcomes, and System-2 improves slowly along gradients sampled through the gate. That separation of timescales is what keeps the loop stable.
Beyond the gate, co-design fixes three interfaces:
Knowledge
What is distilled from System-2 into System-1. For routine cases, the solution itself can move into System-1, which then answers directly and escalates the rest.
Representation
What System-1 sees. Sharing System-2's features buys accuracy but shares its blind spots. Independent encoding keeps their errors uncorrelated.
Feedback
Which outcomes supervise System-1: rewards, gradients, verifier verdicts, or audits. This decides which of its own mistakes it can ever see.
Because System-1 sees every candidate before System-2 acts, it is also a natural place to enforce cost, irreversibility and safety limits. The same gate can be stacked across levels, such as motor, skill and plan, with each level gating the one below.
Examples: one loop, four settings
The same predict, gate, execute, learn pattern runs in training and deployment, in software and in the physical world. What changes is what counts as useful and what counts as cost.
| Training reasoning models | Training robots | Test-time reasoning | Agents using tools | |
|---|---|---|---|---|
| A candidate is | a prompt | a task or environment setting | one more reasoning step or sample | a think, search, tool or ask action |
| System-1 predicts | the chance of a mixed group of attempts | the risk the robot fails after adapting | the value of continuing | the value of the information, net of cost |
| System-2 executes | a group of reasoning rollouts | an episode in a simulator or on hardware | the extra inference | the call or action |
| Feedback | verifier rewards | adaptation loss | consistency or halting signal | tool result, task outcome |
| Cost saved | training compute | actuation and simulation time | inference compute and latency | latency, money, tokens and risk |
| Gate | informative-sample rate | risk threshold | halting threshold | call or commit threshold |
Try it: how much does predicting first save?
Below are 120 things an AI could do next. Only some of them would teach it anything, and it can't tell which until it has paid. Choose how to spend the budget.
How much of the candidate pool would actually be useful.
How often its prediction is wrong, in either direction.
- Paid for, useful
- Paid for, taught nothing
- Useful, but skipped
- Skipped, correctly
Pick a strategy to see what it costs.
In this toy model, each System-1 check costs 2% of one execution, and every execution costs the same. With a perfect predictor the saving approaches 1/ρu. Prediction errors, exploration and shifting data shrink it, as the paper's bounds make precise.
ρu: how much of the effort is worth it
Classic scaling laws describe performance in terms of parameters N, data D and compute C. We add a coordinate that describes how well those three turn into capability: ρu, the share of candidate interactions whose usefulness clears a stated bar.
Performance = f( N, D, C ; ρu )
ρu is not a new resource you can buy. It comes out of the learning process itself, and it always depends on how "useful" is defined. Useful prompts for training, risky tasks for a robot and hard questions for test-time reasoning give different values. Two readings of it matter:
The pool fraction
How much of what's on offer is worth doing right now. A gate can't change this.
The executed fraction
How much of what you actually paid for was worth doing. Doing everything leaves it equal to the pool fraction. A perfect gate pushes it to one.
Our prediction is that ρu falls as a system improves, because mastered tasks stop teaching anything. If so, that decay may explain part of why returns diminish, and scaling would be better measured in informative compute than in total compute.
Skipping the useless share, 1 − ρu, helps on every axis at once. Fewer rollouts and updates save compute and data. Sending each task only to the model it needs reduces how much capacity is switched on. Gating during training lowers cost, gating at test time cuts latency, and focusing both on informative interactions raises success per unit of either.
The math in brief
The paper states these results for any declared utility , with the share of candidates whose true utility clears a floor fixed in advance. Each holds under the assumptions noted, and each comes with its own proof in the paper.
-
The gate
The threshold decides which candidates are allowed, and decides how sharply the best ones are preferred. As it becomes "pick the top candidate". As it becomes a plain filter. If nothing clears the bar, the system abstains.
-
Budgets turn the gate into a price
Spending a budget well is a knapsack problem. The answer is to admit candidates in order of value per unit cost, with the budget setting the price . Prompt selection, task sampling, adaptive halting, tool gating and model routing are all this rule with a different menu, utility and cost.
-
Predicting first beats running everything and filtering
To find the useful candidates, predicting first costs a fraction of executing them all, so the speedup approaches as screening gets cheap.
Assumes a perfect screen. Audit samples and refitting System-1 add to the cost.
-
With an imperfect System-1
Interaction information efficiency (IIE) is useful work per unit of total cost. False positives (), misses () and prediction cost () each shrink the gain below . The demo above computes exactly this ratio. Misses also reduce the yield, so efficiency and yield are reported together: an aggressive gate can look efficient while starving the learner.
Shown for equal execution costs and dead candidates carrying no utility. The paper gives the general form.
-
Bigger pools without more rollout memory
A candidate that is scored rather than executed needs only an embedding, so peak memory does not grow with the pool size . Larger pools contain better candidates, and System-1 can search them at no extra rollout memory.
Compared with synchronous execute-then-filter evaluation.
-
When a cheap predictor picks exactly right
If System-1's error is under half the gap between the worst candidate worth keeping and the best one worth dropping, it selects exactly what an oracle would, with zero regret. Beyond that, regret grows only linearly. A high-probability version adds a term for blind spots, which dominate once average error is small.
-
System-1 should grow with System-2
As System-2 becomes more expensive by a factor , the best System-1 size never shrinks. Scaling System-2 dilutes System-1's own cost but not the cost of its mistakes, so accuracy becomes cheaper to buy. This fixes the direction of co-scaling, not its rate.
Assumes System-1's error curves don't change as System-2 scales.
-
Test-time reasoning
Take one probing step, predict whether the full budget would change the answer, then stop or continue. The saving approaches , and accuracy drops at most by the share of queries wrongly halted.
The paper flags that neither premise has been measured at test time yet.
-
Agents using tools
Calling only the actions predicted to matter costs about the useful share of a call-everything agent, plus prediction and error terms, with accuracy within of it.
Holds for separable actions. Long click sequences need whole sub-trajectories scored instead.
-
A testable scaling hypothesis
With a constant and a perfect gate, the loss curve simply shifts left by on a log-compute axis. If decays as the model improves, curves should line up better against informative compute than against total compute. The stronger hypothesis is that gating also changes the scaling exponent. Both can be tested.
Our line of work on co-design
The position grows out of System-1 and System-2 pairs our group has built and tested across settings. In each, a small predictor learns from the shared optimization history and decides where a much larger system spends its effort.
Training reasoning models: which prompts to roll out
Moving from filtering after generation to predicting before it.
- MoPPS KDD 2026 arXiv 2507.04632
- Tracks each prompt's success rate with an online Bayesian posterior and approaches an evaluation-heavy dynamic-sampling baseline with far fewer rollouts, with several-fold rollout savings reported. System-1 Bayesian prompt-difficulty posterior. System-2 the reasoning model being fine-tuned.
- DPS ICLR 2026 arXiv 2603.10887
- Dynamics-predictive sampling models how each prompt's difficulty evolves as a hidden-Markov process, so selection tracks a moving learner. System-1 difficulty-dynamics model. System-2 the reasoning model.
- GPS ICML 2026 arXiv 2602.01970
- Trains one small, generalizable prompt-predictive model on the shared optimization history to steer RL post-training of a much larger reasoning model, improving training efficiency and test-time compute allocation. System-1 small generative predictor. System-2 a large reasoning model.
Agentic reinforcement learning: where rollouts and credit go
Running the loop inside long-horizon trajectories.
- TRACE EMNLP 2026 arXiv 2606.11119
- A unified rollout-budget allocation framework for agentic RL. It allocates rollouts across tasks and shared trajectory prefixes, and propagates terminal rewards back through the resulting trees. System-1 rollout budget allocator. System-2 the agent's multi-step rollouts.
- Tree-aware Posterior Distillation arXiv 2610.23181
- Critic-free, tree-aware credit assignment for long-horizon agents, deciding which steps of a long trajectory deserve the learning signal. System-1 tree-aware credit model. System-2 the long-horizon agent.
Context: what to keep
System-1 allocates storage, such as a context window, as well as compute.
- You Only Edit Once arXiv 2609.33609
- For in-context learning, a small trained model makes a single edit to the retrieved demonstrations, instead of repeatedly scoring or searching over demonstration subsets. System-1 small demonstration editor. System-2 the LLM using the context.
Test-time reasoning: how much to plan
Gating inference compute, where more thinking can hurt.
- Halo in Limited Reasoning Space arXiv 2602.19281
- The paper finds that larger test-time budgets can make long-horizon reasoning collapse, because over-planning adds redundant feedback. It argues there is an optimal range of compute. Halo is a model predictive control framework for LLM planning: an entropy-driven dual controller follows a measure-then-plan strategy to regulate planning at the edge of the model's reasoning ability. This keeps the benefits of extra compute while suppressing over-planning, and it outperforms static planning baselines on complex long-horizon tasks. System-1 entropy-driven controller. System-2 the LLM doing the long-horizon reasoning.
Robots and adaptive decision-makers: which tasks to train on
Predicting adaptation risk instead of executing tasks to find it.
- MPTS Nature Communications 2026 Read the article
- Model predictive task sampling learns a risk-predictive model from the optimization history, removing the need to evaluate tasks to locate the hard tail. It trains the two systems jointly on two timescales, as in the framework above. System-1 task-risk predictor. System-2 the adaptive policy.
- PDTS ICML 2026 arXiv 2504.19139
- Adds posterior sampling and diversity to task selection, choosing a whole batch at once, for fast and robust adaptation in randomized environments. System-1 posterior risk model with diversity. System-2 the decision-maker.
- In-context MPTS NeurIPS 2026 arXiv 2610.14913
- Closes risk-approximation gaps in model predictive task sampling with in-context risk prediction. System-1 in-context risk model. System-2 the adaptive policy.
Related work from the group studies why the useful band of prompts drifts during RL (Listwise Policy Optimization). As the paper notes, these results illustrate the framework rather than validate it. The decisive test is measuring directly.
What we claim, and how sure we are
This is a Perspective, so we separate what we assume, argue, hypothesize and predict.
Premise assumed
Future digital and robotic systems may be limited more by interaction efficiency than by parameters or data.
Position argued
Progress toward general intelligence should co-design a cheap System-1 with a costly System-2, judging interactions before they run and skipping those predicted to teach nothing.
Hypothesis proposed and testable
The density of useful interactions, ρu, is an important factor in how efficiently resources become capability.
Prediction not yet measured
ρu decays as the system improves. This may account for part of the diminishing returns, so scaling laws are better written in informative compute.
Under stated assumptions, the paper proves screening savings, a regret bound tied to predictor error and the utility margin, and test-time, agentic and co-scaling cost bounds.
Where it helps
- Interactions are costly
- Their value is uneven
- Their value can be predicted in advance
Where it isn't enough
- The predictor is unreliable
- Exploration is still needed, since a gate only learns from what it lets through
Our answer: a qualified yes
Co-design is promising wherever interactions are costly, unequal in value and predictable in advance. The decisive next step is measurement: track ρu as systems learn, compare scaling curves at matched informative compute, and test whether co-design changes more than a constant factor.
Cite this work
@misc{wang2026scaling,
title = {Does Scaling Toward AGI Depend on What System-1
Lets System-2 Execute?},
author = {Wang, Qi and Qu, Yun and Cai, Lizhou and Zou, Heming and
Chi, Haoang and Lv, Yiqin and Li, Xiang and Feng, Haiyan and
Ge, Mengyu and Geng, Yize and Jiang, Yuhang and Mao, Yixiu and
Ji, Xiangyang},
year = {2026},
note = {Tsinghua University}
}