The Gauntlet Loop: never let the builder grade itself

Matt Shumer's Gauntlet Loop went viral after a single-prompt Claude-built FPS pulled 3.8M views, and the pattern underneath is more useful than the demo.

Three rules. First, the lead agent decomposes the goal into independently judgeable pieces, not the human. Second, each piece gets a specialist builder subagent plus a blind critic subagent with fresh context. Third, and this is the load-bearing rule, the critic only passes work that beats a concrete real-world reference it can actually inspect. For the FPS, that was actual Call of Duty screenshots. For your domain, it's a reference site, a writing sample, a competitor's output, a test suite. No fixed round count. The loop runs until output beats the bar or gains go negligible.

The artifact is inspectable, which is what separates this from the usual viral thread. Claude-of-Duty is on GitHub at 2,129 stars and 300 forks: roughly 55,000 lines across 11 subsystems on Three.js r180 and WebGL2. The constraint that makes it a real datapoint is that there are zero art assets. No models, no HDRIs, no image files, no audio files. 19 procedural surfaces generated on the GPU at load time, with three as the only runtime dependency. The render subsystem has cascaded shadow maps with PCSS contact hardening, a depth/normal/velocity MRT prepass, GTAO, and TAA with YCoCg variance clipping. That is not a toy.

Reported settings are Opus 5 with /effort ultracode and the /loop skill. Now the cost signal, because everyone skips this part: an r/ClaudeAI replication on a 3D platformer burned three consecutive 5-hour Opus windows. Budget accordingly. If you're on a subscription, that's most of a day.

What I like about this is that it names the actual failure mode in agentic building, which is that the model grades its own homework and gives itself an A. Fresh-context criticism is the fix, and it's showing up independently everywhere today. old-coder encodes Uncle Bob's advice as a skill: don't read the agent's code, make it produce a test plan before and an evidence report after, and review those two documents instead of the diff. OCBC's Helios puts a fourth independent agent in production whose only job is checking the other agents for accuracy, with humans reviewing only what it can't verify. Prefactor took #1 on Product Hunt with 591 points for wiring eval scores into runtime enforcement so a risky run pauses for human approval instead of just showing up red on a dashboard.

Builder, critic, reference artifact. The critic needs fresh eyes and something real to compare against. Everything else is implementation detail.