The Harness Edit That Wins Your Eval Set Is Not the One That Generalizes Best

Meta-Harness raised its score on the evolve set from 89.4 to 93.0. On held-out benchmarks it moved from 39.7 to 40.6. RRSI, a method described in a recent preprint (arXiv 2609.24972), barely moved on the evolve set, to 90.5. On held-out work it reached 43.6, the highest of the six rows in its comparison table.

That table is the most useful thing I have read this month about teams that let an agent rewrite its own harness. In the setups this preprint studies, the harness around a model is something a loop can edit, score and keep. The table shows what happens when the loop scores against the same set it learns from.

The six rows

The preprint compares a starting harness (H0) against five evolution methods. Each row reports two numbers: the average on the Harvey LAB evolve set, then the average on out-of-distribution sets.

Method	Evolve set	Held-out
H0 (starting harness)	89.4	39.7
Meta-Harness	93.0	40.6
AHE	90.7	39.2
TTHE	91.1	38.0
HarnessX	91.8	39.7
RRSI	90.5	43.6

Read the held-out column first. AHE and TTHE finish below the harness they started from. HarnessX ties it. Meta-Harness, the strongest in-set performer, gains under one point. Three of the four other methods improved what they were scored on and did not improve, or made worse, what they were not scored on.

RRSI inverts the ranking. Its evolve-set score of 90.5 represents the smallest gain over H0’s 89.4 among the five methods. Its held-out score of 43.6 against H0’s 39.7 represents the largest gain.

Two qualifiers belong in the same breath as that result. The out-of-distribution sets are different benchmarks in the same domain, so “held-out” here means nearby work, not unrelated work. And the method’s hyperparameters were tuned on the evolve set, which means some of the evolve set’s information reached RRSI through a side door. The preprint is not peer reviewed. The primary page lists 14 authors with no affiliation, so I attribute the work to its authors and nothing more.

A secondary write-up on StackSweep puts the size in proportion: “The absolute out-of-distribution gains are modest: 1.8 to 4.7 points.” That range is StackSweep’s summary and I cannot map it to specific rows of the table above. Modest is the right word. The direction is what matters for anyone running a self-improvement loop in production.

Why the loop overfits

The mechanism needs no exotic explanation. StackSweep states it in one line: “if you score candidates against the same finite set every round, you are training on your test set.”

A harness edit gets kept because it raised the score. After enough rounds, the surviving edits are the ones that fit the quirks of that particular set: its phrasing, its edge cases, its noise. Each individual edit looks like progress. The accumulated harness is a key filed to one lock.

The RRSI page frames its response as “Regularize the search, not the harness.” The constraint goes on the loop that proposes and accepts edits. For a team, that framing matters because the loop is where your change control lives. In a loop that runs unattended, you do not review every accepted edit by hand. You review the rule that let it in.

Four rules for the loop

StackSweep condenses the approach into three instructions: “Measure your eval noise before you start, make every edit pay for its cost, and delete what stops earning its place.” I add a fourth of my own: keep leaky edits from being scored. I am treating the four as change-control rules for any self-improving harness. The implementation details belong to the preprint. What follows is how I read each rule as policy.

1. Measure noise before the first edit. If the same harness scores differently across repeated runs, an edit that lands inside that spread has not been shown to do anything. Without a noise measurement, the loop will keep lucky edits and reject unlucky ones, and both decisions will be recorded as evidence.

2. Keep leaky edits out of scoring. An edit that carries information about the evaluation set into the harness will score well for the wrong reason. The rule is to stop such an edit from earning credit at all, not to discount it afterwards.

3. Make every edit pay for its cost. Harness growth is not free. StackSweep reports that RRSI used “2.42M policy tokens per trial vs. 3.80M for unregularized evolution (36% fewer).” That figure comes from the secondary, not the primary page, so treat it as reported rather than confirmed. The policy point stands on its own: an edit that adds cost must clear a higher bar than one that does not.

4. Delete what stops earning its place. Self-improving loops accumulate. A rule that helped early may be dead weight many rounds later. Pruning has to be a scheduled operation of the loop, with the same scoring discipline as additions.

We covered the mechanics of building self-improving agents and the oversight questions around recursive self-improvement at lab scale. Neither measured overfitting to the evolve set. These four rules are the piece that sits between them: the discipline that decides whether an edit enters the harness.

The same exposure, one layer down

Datadog published a distillation that sits next to this problem. Scott Kramer and Junaid Ahmed describe teaching a 9B model to investigate production alerts, trained on 186 examples. “The resulting model achieved 87% of GLM-5.3’s recall. Its self-hosted LLM serving cost was $0.003 per investigation, compared with $0.06,” which is roughly 20 times cheaper, a comparison Datadog scopes to “our evaluated deployment conditions.”

They also say “Prompt engineering alone wasn’t enough to make the smaller model reliable.”

The detail that connects to RRSI is the label source. Datadog writes: “We treat each referenced change as a proxy label: the change Bits associated with the incident, rather than independently verified causality.” The training targets are the conclusions of Datadog’s own agent, Bits.

I am not claiming this caused a failure. My reading is that the exposure is structural. When your labels are your agent’s past outputs, the student learns to agree with the teacher, and agreement with the teacher is also what your evaluation can most easily measure. That is the same closed circle the harness loop runs in: the system is scored against material it helped produce. Datadog names the limit openly, which is the part worth copying.

What the table does not tell you

Six numbers per column, one domain, one preprint. The held-out gains are small in absolute terms, and the tuning of RRSI’s hyperparameters on the evolve set weakens the cleanest reading of its held-out lead. I would not pick a harness evolution method from this table.

I would change how I govern one. The pattern in the held-out column does not depend on RRSI being the best method. It depends on the observation that most in-set gains in that table did not transfer. If your team runs any loop that keeps harness edits because a score went up, you are exposed to the same pattern, whether or not you ever read the preprint.

Our earlier piece on self-improving agent governance is the wider frame. In this case the practical conclusion is narrow: the evaluation set is part of the control surface, and it needs the same rotation and protection as any other.

Do this now

Pick one self-improving loop you run, whether it tunes prompts, skills, memory rules or tool configuration.

Run the current harness several times on your evaluation set without changes. Record the spread. Any accepted edit whose gain sits inside that spread gets re-tested.
Split off a held-out set the loop never sees, from adjacent but different work. Report both numbers on every accepted edit, side by side, the way the RRSI table does.
Attach a cost figure to every edit: tokens, latency or context size. Reject edits that raise cost without a held-out gain.
Schedule a pruning pass. Remove each rule in turn and re-score. Rules that no longer move the held-out number go.
Audit your labels. If your eval or training targets come from your own agent’s outputs, write that down next to the metric, as Datadog did.

If your in-set score climbs while your held-out score stays flat, the loop is learning your test.

This analysis synthesizes RRSI: Regularized Recursive Self-Improvement of Agent Harnesses (RRSI authors, arXiv 2609.24972, September 2026), Self-improving agent harnesses overfit. How Google fixes it (StackSweep, Engineer’s Codex, undated), and Teaching a 9B model to investigate production alerts (Datadog, September 2026).

Victorino Group helps engineering teams put change control around self-improving agent loops, from eval noise to held-out gates. Let’s talk.