06-reference

innermostloop test taker becomes test maker

2026-05-13·reference·source: Innermost Loop·by Alex Wissner-Gross
ai-industrystate-of-aiharnessevalsagentic-systemsmeta-evalsfrontier-modelsorbital-infrastructureroboticsbiotech

Innermost Loop — Welcome to May 13, 2026

AWG's daily state-of-AI roundup, threaded by a single editorial line: "The Singularity is the moment the test-taker becomes the test-maker." This is the next-day continuation of yesterday's "Singularity matures" piece ([[2026-05-12-innermostloop-singularity-matures-state-of-ai]]). Yesterday's frame was models auditing their graders; today's frame tightens that to a flip — the model is no longer the object being evaluated, it is the entity writing the evaluation, the goal, and (industrially) the surrounding software stack. Closing line: "All the world's a training set, and all the men and women merely labels."

Key arguments and beats

Why this is in the vault

Mapping against Ray Data Co

Strong continuity with the harness-engineering thesis, with a sharper one-liner. Yesterday's piece extended the thesis; today's piece names it. "The Singularity is the moment the test-taker becomes the test-maker" is the most usable single sentence AWG has produced this week for RDCO purposes. It captures the exact phenomenon described in [[concepts/2026-05-10-harness-moat-two-layers-portability]]: the model is no longer the artifact, the loop around the model is the artifact, and ownership of that loop is the moat.

Direct map to RDCO's RLHF-shaped pipeline. The metaprompting-Codex-to-draft-its-own-/goal beat is structurally identical to the multi-agent pipeline pattern logged at [[concepts/2026-05-12-rdco-pipeline-rlhf-shaped]] — the critic seat in RDCO's pipeline is the test-maker, the code-author seat is the test-taker, and the convergence loop is exactly what AWG is calling the Singularity at frontier scale. RDCO is doing the same shape of work one level down. That parity is useful: it argues the harness pattern is general and that RDCO's pipeline architecture is on the right side of the trend, not behind it.

Vertical-harness-as-product is the GTM play. "Claude for the legal industry" with 20+ MCP connectors and 12 practice plugins is the productized form of harness-eats-model. It validates RDCO's "the deliverable is the integrated loop, not the model call" framing. Worth noting: Anthropic and OpenAI are both shipping this shape now (Anthropic's legal vertical today; OpenAI Development Company's forward-deployed engineers in yesterday's piece). Two frontier labs are converging on harness-as-product simultaneously.

Disambiguation reminder. AWG's "Innermost Loop" is NOT Peter Diamandis's "Innermost Loop" ([[2026-05-12-diamandis-innermost-loop-ai-infrastructure-thesis]]). Same name, different sources, do not cross-cite.

Specific RDCO-relevant signals:

Mapping strength: strong. AWG remains the primary public source for the harness thesis, and today's one-liner — "test-taker becomes test-maker" — is the cleanest framing he has produced for it. Cite this piece anywhere RDCO needs a single sentence to anchor the harness-eats-model claim.

Related