The Evaluator Is the Bottleneck: What a Self-Modifying System's Acceptance Test Must Satisfy Before Its Verdict Can Be Trusted, Why Co-Evolving Evaluators Shrink the External Anchor Rather Than Remove It, and How Moving the Anchor Outside Moves the Attack Surface With It

@misc{mahendrakar2026evaluator,
  author       = {Mahendrakar, Pranay},
  title        = {{The Evaluator Is the Bottleneck: What a Self-Modifying System's Acceptance Test Must Satisfy Before Its Verdict Can Be Trusted, Why Co-Evolving Evaluators Shrink the External Anchor Rather Than Remove It, and How Moving the Anchor Outside Moves the Attack Surface With It}},
  year         = {2026},
  month        = oct,
  date         = {2026-10-04},
  publisher    = {Life of Research},
  doi          = {10.5281/zenodo.23130396},
  url          = {https://lifeofresearch.com/articles/83},
  abstract     = {(c) 2026 Pranay Mahendrakar. Licensed under CC BY 4.0. Self-modifying AI systems now decide which changes to their own code to keep by running an acceptance test and retaining whatever scores higher. Published coding-agent loops report large benchmark gains this way, and their safety case rests on sandboxes, archives of past versions and the option to roll back. Every one of those safeguards presupposes that the acceptance test measures the property the modification is supposed to improve. This paper asks what an acceptance test would have to satisfy for its verdict to be trusted, and answers against the published record. It separates five conditions: fidelity of the test on the candidates the loop itself generates, integrity against tampering by the candidate, statistical power across many candidates and many acceptances, coverage of the state that persists after acceptance, and independence of the evaluator's errors from the proposer's. For each condition, a published loop, the benchmark it relies on, or a controlled study of the same decision records a failure. The strongest counter-evidence is a 2026 line of work that evolves the evaluator inside the loop. Read closely, every such system that reports validity against ground truth keeps a labelled anchor or frozen reference that the loop cannot write, and one reports that removing its anchor guards produces an always-pass grader that downstream task scores fail to expose. The external component shrinks; it does not disappear. A 2026 benchmark-poisoning study then shows that an externally supplied benchmark is an attack surface. No experiments are reported here. The paper states which conditions any published loop has tested, which none has, and what measurements would settle how small the external part can safely be. The literature search, drafting and citation verification for this paper were carried out with AI assistance under the author's direction. Every arXiv citation was machine-verified against its live arXiv Atom API record, and every other citation against its Crossref or DOI record, during drafting (title and author list checked against the record returned). Every quantitative claim is taken from the abstract, full text or a table of the source credited with it; full-text numbers were read from the sources' own HTML or PDF renderings rather than from summaries. No experiment was run and no number in this paper was measured by its author. Table 1 re-presents numbers published by the cited papers, each named on its row; Figure 1 plots published values from four cited sources with no transformation. The five-condition decomposition, Table 2's reading of where each loop holds its evaluator, Algorithm 1 and the anchor argument in Sections 10 and 11 are original conceptual synthesis by the author, not empirical results, and are presented as such.},
  keywords     = {self-improving agents, recursive self-modification, acceptance tests, reward hacking, evaluator validity, benchmark poisoning, AI safety, evaluation science},
  language     = {en},
  copyright    = {Creative Commons Attribution 4.0}
}