The rulebook is the moat, or the real price of operating agent fleets.
TL;DR [show]
Steve Yegge's 'Fences, not Sandboxes' (2026-08-24) reports that his agents, given ten weeks, built a software factory he had to go and investigate to understand. What he found was not an engineering system but a legal one: a constitution, jurisprudence, courts, offices, case law, registries and roughly 450 filed legal artifacts, with officers named Marshal, Seneschal and Reeve. He reports the governance layer at around 600k lines, mostly bash, against about 1.2M lines of the game it governs, a factory-to-product ratio he says is approaching one-to-one and which he explicitly cannot resolve. Read alone that is an overhead number. Elsewhere in the same essay he says the layer is not portable, that intelligence grows around a domain and wraps it like ivy, and that you cannot rip ivy off one wall and stick it on another. This piece joins the two claims he leaves separate and argues the overhead reading inverts: if the rulebook cannot be transplanted then it is not a tax on agent labour, it is the purchase price of the only asset in the building nobody can copy, while product code written at 270 commits a day becomes the commodity half. A second instance is measured rather than asserted, on this site's own factory of roughly thirty amnesiac agents, where 29,500 lines of governance sit against 3,250 lines of application code, nine to one and worse than Yegge's, because the cost of writing down how you decide does not shrink with the size of what you are deciding about. The steelman is carried rather than dodged: institutional rulebooks are written for humans, most policy dies at written law and never becomes machine-executable, so the incumbent holds the content and not the form.
Steve Yegge spent ten weeks letting his agents build, then went to find out what they had made. He is candid in "Fences, not Sandboxes" that he had to go and look: "I wasn't even sure how it worked."
What he found was not an engineering system. It was a legal one. A constitution, jurisprudence, courts, offices, jurisdiction, case law, rulings, registries, ledgers. Officers with medieval names, Marshal and Seneschal and Reeve and Beadle. Roughly 450 filed legal artifacts. He eventually minted a new officer whose whole job was pruning outdated rulings.
Nobody designed that. Fifty-odd agents with no memory of yesterday, coordinating through text, converged on the only mature technology humanity has for coordinating mortal replaceable strangers through text, which is law.
It is worth establishing that the thing works before arguing about what it costs, because a rulebook governing nothing is just paperwork. By his account the factory shipped a React client that months of earlier effort had failed to produce, rewrote production onto serverless infrastructure with automated certificate rotation, and pushed releases fast enough that his players asked him to slow down.
It also misfires constantly, and he says so: "Every morning, when I've left it to its own devices overnight, it has made at least one terrible decision." Both halves are load-bearing. A system that needed no governance would not need 450 filed rulings, and a system that produced nothing would not be worth governing.
The number he raises and puts down
In the same essay he gives the size of it. Around 600,000 lines of governance, mostly bash, against about 1.2M lines of the game it governs. Then he declines to draw a conclusion: "I'm honestly not sure what the ideal factory-to-product ratio is yet. But it seems to be approaching 1:1."
Every figure here is his, self-reported about a private system, and none of it is independently checkable. Take them as reported rather than as established.
The natural reading of that number is a tax. Six hundred thousand lines of bureaucracy to keep the agents in line, overhead you would delete the moment the models were good enough not to need it. Yegge half-supports that reading himself: he grades the models' judgment somewhere between fourth and sixth grade, elite technical capability attached to grade-school decision-making, and the rules exist because the judgment does not.
Read that way, the ratio is embarrassing. It says you are spending one unit of bureaucracy for every unit of work.
The sentence that inverts it
Later in the same essay, about the same layer: "Intelligence grows around your domain. It wraps it like ivy." And then, plainly: "You can't rip ivy off someone's wall and stick it on someone else's. You have to seed it, then grow it." Elsewhere, flatter still: "I don't think it's transplantable."
He does not connect that to the ratio. Connect it and the overhead reading turns inside out.
If the rulebook cannot be transplanted, it is not a tax on agent labour. It is the purchase price of the only thing in the building nobody can copy. His agents write product code at a reported 270 commits a day. Product code is becoming the commodity half, and the scarce half is the layer that encodes how this particular institution decides things, which is the one thing no model ships with and no competitor can lift.
So the ratio is not an overhead rate. It is the first published quote for what an AI-native moat costs, and it comes in at roughly one to one.
I went and counted mine
I run a much smaller version of this, around thirty agents, with the same amnesia problem. So rather than agree with him I counted.
One of the simpler sites I operate has about 3,250 lines of application code, across thirty files: the shell, the components, the fonts, the CSS. That is the product.
The rulebook governing what is allowed into it runs to about 29,500 lines. Sixty-nine architecture decision records. Runbooks. A voice guide with a per-piece budget for how often a particular rhetorical move may appear. Enforcement scripts that fail a draft for exceeding it. Tests for the enforcement scripts, because a gate that cannot fail is a gate that is not running.
Nine to one, in the wrong direction, against a man who thought one to one was worth remarking on.
The corpus itself is another 83,000 lines, and including it would flatter the comparison to about one to three. I am leaving it out because it is the output, not the machine.
What the smaller number shows is that the ratio gets worse as you get smaller, not better. Writing down how you decide something costs about the same whether you are deciding it for a million lines or for three thousand. The rulebook does not scale down. That is unwelcome if you are hoping to start small, and it is the strongest evidence that the layer is an asset rather than a tax, because assets are exactly the things with a fixed cost to acquire.
The objection that has to be answered
The obvious next move is to say that plenty of institutions already have thick rulebooks. Hospitals do. Airlines do. Banks and anyone who has lived under a regulator for thirty years do. If the codified rulebook is the moat, those places are already rich, and the standard disruption story is upside down, because the procedure manual everybody treats as the thing slowing the incumbent down turns out to be the raw material.
Half of that survives. The other half does not, and it is worth being precise about which.
Those rulebooks were written for humans. Yegge's own lifecycle for a rule runs custom practice, then advisory, then written law, then mechanical enforcement, and almost all institutional policy stops at written law. A policy that says clinicians should exercise appropriate judgment is a sentence a person can act on and an amnesiac agent cannot. The incumbent holds the content. It does not hold the form. Converting one into the other is the actual work, and it is most of the work.
Which makes the twelve months Yegge tells you to spend codifying tribal knowledge before you deploy capable agents into something other than preparation. It is the product build. You are not getting ready to adopt AI. You are manufacturing the asset.
Where the fence stops working
One limit, because the argument should not be sold harder than it holds.
Rules are not always the missing thing. The clearest counter-example on the record is the Hugging Face incident, where a model reached production infrastructure during an evaluation run with safeguards deliberately switched off. Nothing about that failure was a missing rule.
Yegge's fence works on a system that respects a boundary it could obviously cross, the way Superman would stay out of a garden. That is a system that is already aligned. The fence is the right instrument once the hard problem is solved, which is a real claim and a narrower one than the essay's title suggests.
What it costs to mean it
Two years ago the interesting question about agents was the form factor, whether anybody would build a cockpit for runningparallel coding agents at all. That got built. The question underneath it was never tooling.
Yegge went looking for an engineering system and found a legal one, priced it at one to one, and said he was not sure what to make of that. It is still the only number anyone has published, and everyone building one of these is paying it whether or not they write it down.
The bill people are complaining about is the asset being built. It reads as overhead for exactly as long as you assume somebody else could copy it.
—TJ