Regulatory Capture: How an Industry Writes the Laws Against Its Rivals

You've been taught to see regulation as a leash on big business. A rule that reins in the giant and protects the little guy. Now watch a giant do something strange: watch it ask for more rules. Watch Facebook's own founder walk into Congress and plead for the government to regulate his industry. Watch the biggest banks quietly support the thousands of pages of compliance that followed 2008. When the largest player in a market begs to be regulated, the leash is not for its neck. It's for yours.

This is regulatory capture, and it is one of the most elegant machines Isfet ever built. It doesn't fight regulation. It authors it.

The moat, and who's allowed to cross it

A castle needs a moat. In medieval terms it was water. In market terms it's a barrier to entry — anything that makes it hard for a new competitor to reach you. And it turns out the most reliable moat in the modern economy isn't a better product or a lower price. It's a law.

Here's the logic, cold and clean. A giant corporation can absorb the cost of a thousand-page compliance regime without blinking. It has armies of lawyers, whole compliance departments, budgets that treat regulatory cost as a rounding error. A startup with six people and a good idea cannot. The rule that the giant "reluctantly" accepts is the same rule that kills the challenger in the crib.

So the giant doesn't fight the regulation. It helps write it — and it makes sure the compliance burden is fixed and heavy rather than proportional and light. Fixed cost is the perfect weapon: trivial for the whale, fatal for the minnow. The moat gets deeper, and only the castle already inside can afford the drawbridge.

The revolving door spins both ways

How does an industry get its hands on the pen? Through a door that never stops turning.

The person regulating the banks last year runs a bank next year. The agency official overseeing an industry came from that industry and will return to it, at triple the salary, the moment their government term ends. This is the revolving door, and it means the regulators and the regulated are frequently the same people wearing different badges. The referee and the striker swap jerseys at halftime, and somehow the score only ever moves one way.

Add lobbying on top. In the United States alone, corporate lobbying runs into the billions of dollars every year — an entire industry whose only product is the shape of the next law. That money is not spent to be ignored. It's spent to hold the pen.

The result: rules that sound like consumer protection and function like competitor elimination. Occupational licensing that turns braiding hair or arranging flowers into a gated profession. Banking rules only a bank the size of a nation can satisfy. AI "safety" frameworks — watch this one closely — increasingly shaped to lock in the handful of labs that already have the compute, and to raise the wall against everyone else.

Our record

Weigh it on the Scales.

Maat is ma'at — the straight rule, the law that holds because it is fair, the order that serves the whole. Isfet doesn't destroy the law. That would be crude, and Isfet is never crude. Isfet captures the law — keeps its shining name and reverses its purpose, so that the instrument built to restrain the strong becomes the instrument that crushes the small.

This is the subtlest theft in the ledger. Not a broken rule — a rule turned inside out while keeping its costume. The word "protection" is spoken with a straight face while the thing being protected is the incumbent's throne. Name it, and the costume falls off.

The IT read: they closed the API and called it security

Every developer has watched this exact move in the software world. A platform opens up. Thousands of small builders flood in on the open API, competing, innovating, keeping the platform honest. Then the platform matures — and one day announces new "security requirements," "trust and safety review," "partner certification." Suddenly you need a compliance team and a six-figure audit just to keep the access you already had.

The giants sail through — they helped draft the requirements. The indie developers get deprecated out of existence. The platform calls it security. It was never security. It was pulling up the ladder after climbing it, and stamping "for your protection" on the spot where the ladder used to be. Same move as a captured regulator. Different stack, identical exploit.

How to spot a captured rule

You can learn to read the tell. A few questions cut through almost every case.

Who lobbied for it? If the biggest incumbents are quietly for a new regulation, ask why the powerful want more rules on themselves. They don't. They want more rules on you.

Is the cost fixed or proportional? A rule that costs the same dollar amount whether you're a giant or a garage is a rule engineered to crush the garage. Fair rules scale with size. Moats don't.

Does it protect the customer or the incumbent? Follow the actual effect, not the title. If the practical result is fewer competitors and higher prices, the "protection" is protecting a market position, not a person.

Where did the rule-writer work before, and where will they work after? Trace the revolving door. The résumé tells you who the pen really belongs to.

The lever

Here's the door, and captured regulators can't lock it — because it isn't built on their turf.

The whole capture machine runs on a single point of failure: a central authority that holds the pen, close enough to be bought. Remove that chokepoint and the moat has no water. This is exactly why open protocols, decentralized networks, and permissionless systems are so threatening to the captured order — there is no single office to lobby, no single regulator to hire away, no single API to close. Rules enforced by open code can't be quietly rewritten by whoever pays the most this quarter.

You can't out-lobby a giant. But you can build and back systems that have no pen to capture. Support the open protocol over the licensed platform. Route around the chokepoint. A machine with no single point of failure is a machine that can't be captured — and that is the one moat they were never able to dig.