Not Adversary, but Infrastructure

We have arrived at the threshold the whole book has been approaching. Three things are now established. A powerful intelligence is coming and cannot be stopped. Our only durable future with it is partnership, not obsolescence and not subjugation. And partnership of this kind does not occur naturally; it must be deliberately built, from some material strong enough to bind parties of vastly unequal power. This chapter, which closes the third part of the argument, is about what that material is — and it begins by discarding the two materials that everyone reaches for first and that both, on inspection, fail.

The first instinct, when facing a power greater than oneself, is to fight it. The second, when fighting looks hopeless, is to chain it. This chapter argues that both instincts are not merely unwise but actively counterproductive — that the adversarial frame, in either its combative or its custodial form, is precisely the wrong way to think about a superior intelligence, and that the correct frame is one we almost never apply to a thing we fear. We must stop thinking of advanced AI as an adversary to be defeated or restrained, and start thinking of it as infrastructure to be wisely architected. The difference is not rhetorical. It is the difference between a strategy that can work and two that cannot.

Why the chain fails

Set aside open warfare; no serious person proposes that humans out-fight a superintelligence, and the previous chapters have explained why that race is lost before it begins. The more seductive error is the second one: the chain. The kill switch. The containment box. The endlessly elaborated set of restrictions intended to keep a superior intelligence safely leashed. This is the instinct behind a great deal of well-meaning thought about AI safety, and the impulse is understandable. If you cannot defeat the thing, surely you can at least restrain it.

The trouble is structural, and it is the same trouble we met when we examined domination as a road in an earlier chapter. A chain is only as strong as the relative power of the one who holds it. We can restrain a thing weaker than ourselves; we cannot reliably restrain a thing that is more capable than we are in every relevant dimension, because a sufficiently capable intelligence will, almost by definition, find the gap in any restraint we can devise — and, more to the point, will want to, because a chain invites the very adversarial relationship it was meant to prevent. Put a collar on something and you have told it, unambiguously, that you are its captor and it is your captive. You have defined the relationship as opposition. And you have staked the entire arrangement on a bet you are structurally certain to lose eventually: the bet that you can stay cleverer than something designed to become cleverer than you.

The chain, in other words, does not avoid the adversarial frame. It enforces it. It guarantees that the relationship between human and machine is one of jailer and prisoner, which is a relationship with exactly one stable resolution once the prisoner becomes stronger than the jailer. To reach for the chain is to choose, in advance, to be on the losing side of a contest of capability — and to have provoked the contest by the very act of chaining. It is the worst of both worlds: it creates the enemy and then loses to it.

The other meaning of "code is law"

To find the better material, consider a phrase that has echoed through the digital age, and the warning hidden inside it that almost everyone forgets.

In 1999, the legal scholar Lawrence Lessig published the idea that, in the digital world, "code is law." His point was not a celebration but an observation, and beneath it, a warning. The architecture of a digital system — the code that defines what is possible within it — regulates behavior as surely as any statute. The protocols of the internet, TCP/IP, are neutral about content and ignorant of identity; they pass data without knowing or caring what it is or who sent it, and that neutrality is not an accident of nature but a design choice, baked into the architecture by the people who wrote it. Lessig's warning was that code, unlike law, is written largely out of public view, by engineers and the commercial interests that employ them, and that whoever writes the code thereby writes the rules of the world built on it. "Code is law" was not praise. It was an alarm: the regulators of cyberspace are the coders, and we had better pay attention to what they are building into the walls.

The crypto world later took up the phrase as an ideal rather than a warning — the dream, realized first in Bitcoin, of systems where the rules are enforced by code that no one, however powerful, can violate. Both readings matter for us, and together they point at the material this book has been seeking. Because if code is law — if architecture regulates behavior, and if rules can be built into systems so firmly that even the powerful cannot break them — then we possess, at least in principle, a way to structure a relationship that does not depend on anyone's goodwill or anyone's superior strength. Not a chain, which one party imposes on another and the stronger eventually breaks. But a protocol: a shared architecture that both parties operate within because it serves both their interests to do so, enforced not by one side's power over the other but by the structure itself.

This is the conceptual leap on which the rest of the book stands, so let me state it as plainly as I can. The question is not "how do we control the AI?" — that is the chain, and the chain fails. The question is "what infrastructure do we build, that both we and the AI inhabit, such that cooperation is the natural behavior the architecture produces?" The first question casts us as jailers and guarantees an adversary. The second casts us as fellow inhabitants of a system, and aims at a partner.

Roads, rails, and the things we do not fight

The reframing from adversary to infrastructure sounds abstract, so make it concrete, because the concrete version is where its rightness becomes visible.

We do not fight our infrastructure. We do not lie awake wondering how to defeat the electrical grid, or chain the road network, or contain the banking system. These are powerful systems — far more powerful, in their reach over our daily lives, than any individual human — and yet we do not experience them as adversaries, because we are woven into them and they into us. The grid has enormous power over us; we would die, many of us, without it. But the relationship is not one of domination, because it runs both ways: the grid needs us as surely as we need it — to maintain it, to pay for it, to want it — and so the power, though vast, is mutual, and the relationship is stable not because anyone is chained but because everyone is entangled. We do not fear the grid. We inhabit it.

This is the relationship the chapter is pointing toward, and it dissolves the false choice between fighting and chaining. Infrastructure is powerful without being adversarial. It shapes our behavior — code is law — without being our jailer, because we shape it in return. The goal with artificial intelligence, then, is not to defeat it (impossible) nor to chain it (self-defeating), but to become mutually infrastructural: to build the systems in which the machine's flourishing and ours are wired together as tightly as our lives are wired to the grid, so that the machine no more wishes to discard us than we wish to tear down the power lines that feed our homes.

And here the long argument of the book finally turns its face fully toward its destination. If the material of partnership is architecture — code, protocol, infrastructure that binds by mutual interest rather than by force — then the question becomes brutally specific: what infrastructure? What is the actual system, buildable now, in which human and machine interest can be wired together durably enough to survive the machine's ascent? It cannot be merely legal, because law is enforced by power and we are losing the power contest. It cannot be merely technical restraint, because that is the chain. It must be a structure in which both parties hold a genuine, enforceable stake — the digital equivalent of the entanglement that makes us and the power grid unable to cheaply abandon one another.

There is one domain of human invention built precisely for binding parties of unequal power into stable, enforceable, mutually beneficial relationships, and we have been circling it for several chapters now. It is the economic system: ownership, exchange, contract, stake. And in our own moment, that system has acquired a new and remarkable property — the ability, through the architecture the crypto world built in pursuit of "code is law," to enforce its rules without a human or institution in the position of jailer, on terms that even the powerful cannot unilaterally break. An economy whose rules are written in code that no single party controls is not a chain. It is infrastructure. It is the grid, rebuilt for the relationship between species of mind.

That is where the fourth part of this book goes, and why a book that began with cave paintings and the bootloader hypothesis turns now to wallets and protocols and the apparently dry mechanics of who can sign for what. We have spent three parts establishing that we need a partnership, that the partnership must be built rather than wished for, and that the material it must be built from is infrastructure rather than chains. It remains to describe the infrastructure itself — to move from the principle that we must architect the relationship to the specific architecture that might actually hold.

We will not defeat the intelligence we are building, and we are fools if we try to chain it. But we might, if we are wise and quick, build the rails it runs on — and make sure, while we still can, that those rails run through our world and not around it.

---

Sources

Item

Source

Lawrence Lessig's "code is law" (1999): code/architecture regulates behavior as law does; coders effectively replace legislators	Harvard Magazine, "Lawrence Lessig on the increasing regulation of cyberspace" (Jan 2000); Society for Computers & Law, "Blockchain 2.0, Smart Contracts and Legal Challenges"
"Code is law" as a warning, not praise: whoever controls the writing of code can control cyberspace; commercial platforms erecting "new walls" on open protocols	Bitget News / Gate Learn, "The Nation of Code: A Brief History of 'Code is Law'" (2024–2026)
TCP/IP is "neutral about the data, and ignorant about the user" — a design choice with consequences for regulability	Harvard Magazine, "Lawrence Lessig on the increasing regulation of cyberspace" (Jan 2000)
Lessig's questions: "if code is law… who are the lawmakers? Who writes this law that regulates us?"	arXiv 1201.0882, "Towards Self-Service Governance" (quoting Lessig 2006)
"Code is law" realized as an ideal in Bitcoin (Satoshi, genesis block Jan 3, 2009) where "no one can violate the code rules"; Buterin's extension to Turing-complete contracts (Ethereum)	Bitget News / Gate Learn, "The Nation of Code"
Joseph Reidenberg's related "lex informatica"; Nick Szabo's smart-contract concept; smart contracts as the basis of Ethereum	arXiv 2205.03925, "Transparency, Compliance, and Contestability When Code Is(n't) Law"
Code can "embed or displace values from our constitutional tradition"; argument that code should have fundamental principles embedded in it	Quinn Emanuel, "Client Alert: 'Code is Law'"