Protocol and the Control Hidden Inside Decentralization
Alexander R. Galloway's Protocol is an early and still useful theory of network power. Its central lesson is that decentralization does not remove control. It relocates control into standards, addresses, interfaces, naming systems, defaults, and the technical rules that decide what can connect.
The Book
Protocol: How Control Exists after Decentralization was first published by MIT Press in hardcover in 2004, with paperback and ebook editions following in 2006. MIT Press lists it in the Leonardo series and describes it as a study of whether the internet is best understood as open communication or as a regulated technical bureaucracy.
Galloway's argument is direct: the internet's founding condition is not pure freedom but protocol. The network works because machines agree to rules. Those rules do not merely carry information. They define what counts as a valid address, packet, request, route, domain, format, connection, and failure.
This makes the book unusually valuable for readers who want to understand power after the obvious center disappears. The old question asks who commands the network. Galloway asks how command persists when no single visible commander is necessary.
Protocol Power
Protocol power is quiet because it looks like compatibility. TCP/IP, DNS, HTML, routing tables, file formats, authentication standards, application programming interfaces, platform policies, and model endpoints all promise interoperability. They also impose grammar.
The RFC for Internet Protocol, published in 1981, describes a system for moving datagrams through interconnected networks by common rules for addressing, fragmentation, routing, and gateway behavior. That technical modesty is exactly why Galloway matters. A protocol does not need to sound ideological to organize the possible.
The political point is not that protocol is evil. Without protocol, networks fail. The point is that every shared rule allocates power. It decides who can speak, how identity is represented, where failure is detected, what gets dropped, what remains invisible, and which actors can change the rule later.
Decentralization Is Not Escape
Protocol is most useful when it punctures the romance of decentralization. A distributed network can still be governed. It may be governed less by a throne and more by standards bodies, root zones, browser vendors, cloud providers, identity layers, app stores, moderation APIs, security certificates, model providers, and defaults that ordinary users never inspect.
The 2004 review in Neural read Galloway this way: technical standards enable large-scale infrastructure while also shaping the forms of expression that can appear inside it. That is the right emphasis. A protocol is not only a pipe. It is a social filter that has been made operational.
This is why the book has aged better than many early internet texts. It was written against utopian claims about the liberating network, but its deeper object is not the early web. Its object is any system where governance hides inside the condition of participation.
The AI-Age Reading
AI makes Galloway's argument newly practical. A model ecosystem is full of protocols: prompt formats, API schemas, tool-call conventions, context windows, system messages, safety classifiers, model-card templates, authentication scopes, eval thresholds, content provenance formats, memory export rules, and agent permission layers.
These are not neutral wrappers around intelligence. They shape what the system can remember, which tools it may invoke, how it identifies a user, what counts as an allowed request, when a human must approve an action, and how an institution can audit what happened afterward.
The agentic internet intensifies the issue. When software agents browse, negotiate, purchase, schedule, submit forms, write code, and operate other software, protocols become behavioral law. The important control point may not be the visible chatbot. It may be the permission token, browser automation interface, MCP server, API gateway, payment rail, logging standard, or policy file that decides what counts as a valid action.
Resistance and Its Limits
Galloway does not present protocol as a sealed machine. MIT Press notes that the book turns to hackers, viruses, cyberfeminism, internet art, and tactical media as examples of subversion inside network culture. The point is not escape from rules but pressure on the rule-making layer.
That distinction matters. A hack is not only a breach. It can be a demonstration that the system's categories are contingent: a different route, a malformed request, a fork, a refusal, a parody interface, a new client, a reverse-engineered standard, a protocol extension, or a public exploit that makes hidden assumptions visible.
But resistance can also be absorbed. Once a platform standardizes the workaround, monetizes the deviance, or converts the fork into a feature, the gesture becomes another option in the menu. Protocol power is hard to fight because it can translate opposition into compatibility.
Where the Book Needs Friction
The book's weakness is that its conceptual strength can sometimes outrun institutional specificity. Not all standards operate alike. An open internet standard, a private API, a safety policy, a browser default, a biometric database, and a model vendor's tool schema each distribute authority differently.
That difference matters for governance. Some protocols are publicly documented and can be implemented by many actors. Some are controlled by firms. Some are shaped by states. Some are nominally open but practically dominated by infrastructure incumbents. Some are standards in name and chokepoints in practice.
Academic reception also shows the book as part of a broader debate rather than a final theory. Convergence published Greg Boiarsky's review in 2006, and PhilPapers records James Tobias's 2005 review in Radical Philosophy. The continuing usefulness of the book is not that every sentence settles the politics of networks. It is that it gives readers a durable question: where has control moved when the center is gone?
The Site Reading
For this site, Protocol is a book about the governance layer beneath the interface.
Modern systems often arrive as surfaces: chat windows, feeds, dashboards, companions, identity portals, workplace tools, moderation queues, and agent consoles. The surface invites users to think in terms of content and intention. Galloway pushes attention downward to the rule system that makes the surface possible.
That shift is essential for AI-era literacy. It is not enough to ask whether a model gave a good answer. Ask which protocol carried the request, what memory was attached, what identity was assumed, what tools were available, what safety layer intervened, what logs were retained, what vendor gained dependency, and who can change the rules without the user's consent.
The practical lesson is simple: audit the grammar of participation. Any system that defines the terms of connection also defines a politics. Decentralized language, open rhetoric, and friendly interfaces do not cancel that politics. They often make it harder to see.
Sources
- MIT Press, Protocol: How Control Exists after Decentralization.
- RFC Editor, RFC 791: Internet Protocol, September 1981.
- Neural, "Protocol, how control exists after decentralization", April 21, 2004.
- Greg Boiarsky, Convergence: The International Journal of Research into New Media Technologies, review of Protocol, 2006.
- PhilPapers, James Tobias, review of Protocol in Radical Philosophy, 2005.
Book links are paid affiliate links. As an Amazon Associate I earn from qualifying purchases.
- Amazon, Protocol by Alexander R. Galloway.