INQUIRING LINE

Counterintuitively, your most powerful AI model may actually be worse at following a pre-written playbook than a mid-tier one.

How should we allocate model budget between evolvers and harness users?

This explores how to split a fixed model budget between the work of evolving/updating a harness (writing the protocols, skills, memory edits) and the work of actually using that harness to do tasks — and whether those two jobs reward different model sizes.


This explores how to split a fixed model budget between the work of *evolving* a harness — writing the protocols, skills, and memory edits — and the work of *using* that harness to get tasks done. The corpus has a surprisingly sharp answer to the first half: the capacity to produce useful harness updates is roughly flat across model tiers, while the capacity to *benefit* from those updates follows an inverted U, peaking at mid-tier models Do stronger models always evolve harnesses better?. Weak models can't reliably invoke the harness they're handed; very strong models chafe against faithfully following externalized instructions. That single finding reframes the whole budgeting question — if evolving is flat but benefiting is peaked, you don't need to spend your best model on writing the harness.

The practical implication is a deliberate asymmetry: pay your premium tokens to the *users*, not the *evolvers*. Since any tier can draft a competent harness edit, the evolver role is a place to economize — a cheaper or smaller model can generate protocol and skill updates without much loss. The expensive, high-value compute belongs where the inverted-U peaks: the mid-tier agents actually executing tasks against the harness. This is the same logic the diversity literature reaches from another direction — smaller models around 500M parameters generate more unique outputs per sample than large ones, because big models concentrate probability mass and collapse variety Why aren't bigger models better for generating diverse outputs?. If part of evolving a harness is proposing many candidate edits to select from, smaller generators may literally explore better per dollar.

There's a deeper warning lurking here, though: don't let the evolvers run on a closed loop. Pure self-improvement — a model rewriting its own harness off its own judgment — hits structural limits from the generation-verification gap, diversity collapse, and reward hacking; the methods that actually work smuggle in external anchors like past versions, third-party judges, or user corrections Can models reliably improve themselves without external feedback?. So a slice of budget should go not to *more* evolver compute but to *verifier* compute — and reward models themselves improve markedly when allowed to reason before scoring, which turns evaluation into its own test-time-scaling axis Can reward models benefit from reasoning before scoring?. The evolver/user split is really a three-way split: generate, use, and verify.

Stepping back, the corpus reframes "allocation" itself as adaptive rather than fixed. The compute-optimal scaling work shows that spending the *same* total budget adaptively — less on easy prompts, more on hard ones — beats a uniform split and can even beat a larger model under a flat budget Can we allocate inference compute based on prompt difficulty? How should we spend compute at inference time?. Applied here, that means don't fund evolvers and users at a static ratio; fund harness evolution when the agents are visibly struggling (hard, novel task regimes) and starve it when the harness is already carrying the load. Inference compute and parameter scaling are not independent resources Can inference compute replace scaling up model size?, and the same is true of evolver and user budget — they trade against each other on the margin.

Finally, if budget keeps growing past the point where refining one configuration helps, the population literature suggests spending it on *many* rather than *bigger*: after single-model pretraining saturates, aggregating a diverse population reaches lower loss than refining one model further Should extra compute refine one model or build many?, and evolutionary search at inference time — many candidates kept diverse by an island model — outperforms best-of-N and sequential revision Can evolutionary search beat sampling and revision at inference time?. The unexpected takeaway: the best use of a marginal token is rarely a stronger evolver. It's a cheaper, more diverse pool of evolvers, an external verifier to keep them honest, and your premium compute reserved for the mid-tier agents who actually metabolize the harness into results.


Sources 9 notes

Do stronger models always evolve harnesses better?

Model capability to produce useful harness edits stays constant across tiers, but capacity to actually benefit from those edits follows an inverted U-shape, peaking in mid-tier models. Weak models fail to invoke harnesses; strong models struggle with faithful instruction-following.

Why aren't bigger models better for generating diverse outputs?

Research shows that for synthetic data generation, models around 500M parameters outperform larger ones in output diversity per sample. Larger models concentrate probability mass on preferred outputs, reducing the variety of distinct samples generated within a fixed budget.

Can models reliably improve themselves without external feedback?

Pure self-improvement stalls due to the generation-verification gap, diversity collapse, and reward hacking. Reliable improvement methods succeed by smuggling in external anchors: past model versions, third-party judges, user corrections, or tool feedback.

Can reward models benefit from reasoning before scoring?

Three independent teams (RRM, RM-R1, DeepSeek-GRM) discovered that adding chain-of-thought reasoning before reward scoring enables adaptive test-time compute scaling for evaluation. Reasoning-based approaches raise the capability ceiling of reward models beyond what outcome-based evaluation achieves.

Can we allocate inference compute based on prompt difficulty?

Research shows inference effectiveness varies dramatically by prompt difficulty. Reallocating the same total compute adaptively—giving easy prompts less and hard ones more—substantially outperforms larger models under uniform budgets.

Show all 9 sources
How should we spend compute at inference time?

Research shows that uniform inference budgets waste compute; allocation should vary by prompt. Test-time compute can substitute for training-time scaling on hard problems, but cannot overcome fundamental limitations set by the training regime.

Can inference compute replace scaling up model size?

Snell et al. (2024) showed that inference-time compute trades off against model parameter scaling, especially on difficult prompts. This reveals pretraining and inference compute are not independent resources.

Should extra compute refine one model or build many?

Once single-model pretraining saturates, aggregating predictions from a diverse population of models reaches lower validation loss than further refining one model. Anti-correlated learning-rate and weight-decay schedules plus chain distillation enable this efficiently, matching 256-epoch ensembles with ~56 epochs.

Can evolutionary search beat sampling and revision at inference time?

Mind Evolution uses genetic algorithms with LLM-generated mutations and crossovers to significantly outperform Best-of-N and Sequential Revision on planning benchmarks. An island model sustains population diversity, preventing the premature convergence that single-trajectory refinement exhibits.

Papers this line draws on 8

The research behind the notes this line reads — ranked by how closely each paper relates.

Research prompt for your LLMexpand ↓

Copy into ChatGPT or Claude to take this line of inquiry further — it asks the model to find newer work and re-test which earlier constraints still hold.

You are an ML systems analyst. Open question: how should a fixed model budget be split three ways — between agents that EVOLVE a harness (protocols, skills, memory edits), agents that USE it to get work done, and agents that VERIFY — and does the recommended split still hold?

What a curated library found — and when (dated claims, not current truth); these span ~2024–2026:
- The capacity to PRODUCE useful harness updates is roughly flat across model tiers, while the capacity to BENEFIT from them is an inverted U peaking at mid-tier models — so pay premium tokens to users, economize on evolvers (~2026).
- Smaller models (~500M params) generate more unique outputs per sample than large ones, which concentrate probability mass and collapse variety — cheaper generators may explore candidate edits better per dollar (~2025).
- Pure self-improvement is circular: generation–verification gap, diversity collapse, reward hacking; methods that work smuggle in external anchors (past versions, third-party judges, user corrections) (~2024).
- Reward models improve markedly when allowed to reason before scoring, making verification its own test-time-scaling axis (~2025).
- Spending the SAME budget adaptively (less on easy prompts, more on hard) beats a uniform split and can beat a larger model under a flat budget (~2025).

Anchor papers (verify; mind their dates): Harness Updating Is Not Harness Benefit (arXiv:2605.30621, 2026); Mind the Gap: Self-Improvement of LLMs (arXiv:2412.02674, 2024); Reward Reasoning Model (arXiv:2505.14674, 2025); Evolving Deeper LLM Thinking (arXiv:2501.09891, 2025).

Your task: (1) Re-test each constraint. For every finding, judge whether newer models, training, tooling, orchestration (memory, caching, multi-agent), or evaluation has RELAXED or overturned it — cite what resolved it; separate the durable question (the split) from perishable limits (e.g. is the inverted-U still tier-specific?), and say where a constraint still holds. (2) Since this is synthesis-probing, RECONCILE the threads: does adaptive per-difficulty allocation subsume the flat-evolver/peaked-user rule, or do they conflict? Surface superseding work from the last ~6 months. (3) Propose 2 research questions that assume the regime has moved.

Cite arXiv IDs; flag anything you cannot ground in a real paper.