A ten-week dark factory built itself a constitution instead of tighter sandboxes

Steve Yegge has spent ten weeks running roughly 50 to 60 Claude agents against his long-running game project, Wyvern, at a self-reported $122,000 a month in equivalent API spend across 21 Claude Max accounts (a number he says has grown by two a week). Rather than converging on tighter guardrails, he reports that the agents built themselves a legal system: a constitution, case law drawn from his own daily rulings, offices that outlive whoever holds them, and mechanical enforcement. Wheelhouse, the resulting factory, now runs about 600,000 lines of code and tests, pushes 270 to 500 commits a day through its merge queue, and by Yegge's account is approaching a 1:1 size ratio with Wyvern itself.

The enforcement primitive he names is a "fence": "any mechanism that turns you away if you aren't supposed to be there," distinct from a sandbox because it does not try to physically stop a capable enough agent, only to require it to follow the process. Rules move through a fixed lifecycle in Wheelhouse: custom practice, then an advisory warning, then written law binding on every agent, then mechanical enforcement, each stage triggered by a repeat violation. By Yegge's count, Wheelhouse now holds 450 of these legal artifacts across offices, runbooks, rulings, and enforcement patrols.

The account is a single operator's self-report with no independent verification and no benchmark numbers, and it leans heavily on enthusiasm ("My reaction was straight up WTF. No words," Yegge writes of first seeing what his agents had built).

Why it matters: This is a live, ten-week-old counterexample to the sandboxing-and-guardrails default that most harness design still assumes. If the pattern holds beyond one operator's game project, "write the rules down and enforce them mechanically" is a concrete alternative for anyone trying to coordinate a growing number of agents that cannot remember yesterday's decisions.