Independent Convergence

Independent convergence is when unrelated third parties arrive at the conclusion you built on — in their own words, on their own problems, without knowing you exist. It is the only form of external proof we consider defensible: named authors, dated publications, checkable claims. This page is our running record of it. Every entry states who said it, when, and the caveat that rides with it — because a receipt with its caveat stripped is not a receipt.

The record clusters around three conclusions. We wrote about the first in The Model Is the Smallest Part; the sources below extend it.

1. The system, not the model

The strongest entry is the most controlled one. In July 2026, a team at the University of Illinois Urbana-Champaign published SwarmResearch (arXiv:2607.02807) — a study of orchestrated coding agents that held the model constant across every method it compared and attributed the outcome differences entirely to harness design. Their words: they treat it as "a harness-engineering problem." That is the exact experimental shape our thesis predicts: same model, different system, different results.

The practitioners got there first, from unrelated directions. Akimitsu Takeuchi spent eighteen months and roughly 140,000 messages across three model families and titled his conclusion The Model Wasn't the Bottleneck. The Configuration Was (AI Advances, June 2026). Jaroslaw Wasowski, analysing a frontier coding stack (Level Up Coding, June 2026), reported that a harness alone moved an agent from outside the top 30 to the top 5 with the model unchanged — his point being that you should evaluate the whole system, never a single leaderboard number. Kapil Viren Ahuja put it in five words from the methodology side: "the harness is not the method" (Medium, May 2026).

And the market voted. Sakana AI shipped Fugu (June 2026): a planner that writes the full workflow up front and a small router that assigns each step to a worker from a swappable pool of unchanged models — orchestration as the product. In the same window, Anthropic moved dynamic workflows into Claude Code: the agent holds its plan in a script, runs adversarial checkers against its own output, and checkpoints long jobs. The layer everyone treated as glue became the thing both labs decided was worth building. One caveat we carry with the Fugu entry: its performance numbers are vendor-reported, so the receipt is the shipped architecture, not the benchmarks.

One boundary worth stating, because the SwarmResearch team found it and honesty demands it travel with the thesis: the direction of the prescription flips with how open the task is. For contract delivery — build exactly this — instruction specificity helps. For open-ended exploration, the same study found that when the orchestrator prescribes specific ideas, the agents collapse into the orchestrator's own idea basin. The system still explains the variance in both regimes; what the system should do differs.

2. The verifier decides

Fareed Khan's automated security pipeline (AI Advances, June 2026) states the discipline in eight words: "a crash, not the model, decides what counts." His system discards whatever the agent claims it found; a finding exists only when the host reproduces the failure itself. He also publishes his unproven candidates next to the proven ones — the flop beside the win, which is its own kind of receipt.

Lilian Weng's write-up on self-improving harnesses (July 2026) adds the structural version of the same rule: the evaluator and the permission to change things must sit outside the loop that is being improved — otherwise the system grades its own homework and drifts toward reward hacking.

Jesse Vincent (blog.fsck.com, June 2026) supplied the field test. He pre-registered twenty-five experiments on his own agent harness — prediction written down before each run — and, tellingly, found three bugs in his own measurement harness that only manual inspection caught, including one claimed improvement that re-measured to a much smaller honest one. The verifier-decides rule applies to the verifier too.

3. The self-improving harness

Weng's piece also lays out a full reference architecture for improving the harness itself: mine failure patterns from complete execution traces, propose bounded edits only on surfaces explicitly marked editable, and promote a change only when it fixes the weakness it targeted and nothing else regresses on held-out work.

Here the honest framing matters most, so we state it plainly: this is convergence on a design, not a claim that we run the full loop. Parts of it are in production; the proposal and gated-promotion stages are mid-build. What this entry shows is narrower and still worth showing — the reference design we have been building toward is the one an independent researcher published, without knowing we exist.

Convergence, not endorsement

None of the authors on this page validated Bouletteproof. None of them know we exist. They were solving their own problems and publishing what they found — which is precisely why their work is worth citing. This page will never present a worldview essay as a technical receipt, never count vendor guidance as an independent discovery, and never strip a caveat to make a claim stronger. When a new source converges, it gets added with its date and its limits. When one doesn't hold up, it doesn't appear here.