Introduction

In the mid-twentieth century, Robert Moses built a network of parkways across Long Island, connecting New York City to its suburbs and beaches. The now-canonical story, drawn from Robert Caro’s biography and made famous by the political scientist Langdon Winner, is that some of Moses’s parkway overpasses were built too low for buses to pass beneath them. Cars could use the parkways. Buses could not. And because the people who depended on public transit were disproportionately poor and Black, the parkways’ design had the effect of restricting access to Jones Beach and Long Island’s suburban communities. Whether or not every overpass reflected deliberate racial intent — the historical record is contested — the analytical point is powerful: a technical artifact can allocate access as effectively as a legal rule.

That is the familiar lesson: infrastructure can govern.

This book begins with the other half of the same thought: law is infrastructure. The parkways were not simply physical objects that happened to produce political effects. They were products of law: public authority law that gave Moses his power, property law that enabled land acquisition, financing structures that funded the construction, administrative discretion that shielded the decisions from oversight, traffic classifications that determined which vehicles could use which roads, and transit governance that shaped the alternatives available to those who couldn’t drive. The overpass was physical. But the system that made the overpass possible — and that determined who would be affected by it — was legal. The built environment did not replace law. It materialized law.

And Moses understood this. That is why he was so effective — and so dangerous. Robert Caro’s biography reveals Moses not primarily as an engineer or even as a planner, but as a master of the legal institutions that enabled and constrained what he wanted to build. He drafted the legislation that created the public authorities he would lead. He designed the bond structures that funded his projects without requiring legislative appropriation. He exploited the administrative discretion those structures gave him to make decisions that elected officials could not easily reverse. Moses built parkways, bridges, and parks — but the tools he used to build them were legal tools: statutes, authorities, bond covenants, administrative powers, and the strategic manipulation of the institutional environment. His real infrastructure was legal. The concrete was just the part you could see.

Look at any city from above. It appears to be made of roads, buildings, pipes, wires, parks, lots, and parcels. But much of what you are seeing is law. The height of the buildings is zoning. The shape of the lots is property law. The distance between structures is a setback requirement. The empty space around stores is often a parking minimum. The width of the streets reflects subdivision rules, fire codes, traffic engineering standards, and public works law. The city is not first built and then regulated. It is built through regulation. Law is not merely a set of commands imposed on the built environment. It is part of the built environment: a human-made infrastructure that shapes what can be built, who can access it, how systems fail, and how society adapts.

That is the thesis of this book: law is, and can be understood as, part of the built environment.

A quarter century ago, Lawrence Lessig famously argued that code is law — that software architecture regulates behavior as effectively as any statute. Perhaps. But is law also code? Sometimes — and where it is, it is far richer, more complex, and often indeterminate. And sometimes it is not code at all. This book is about how engineers engage with law, and a large part of that engagement is understanding how different law is from code.

If this seems obvious, consider how rarely it is taken seriously — and why. Benjamin Franklin. Thomas Hobbes. Aristotle. Thomas Jefferson. Hypatia of Alexandria. All are known for their contributions to political thought. All were also scientific thinkers.

In an earlier era, what we think of today as philosophy, political science, economics, engineering, mathematics, and the natural sciences were all part of a single intellectual enterprise. The people who thought about how to build things and the people who thought about how to govern were often the same people. They understood, intuitively, that the systems of governance and the systems of construction were part of the same project.

In the modern era, this synthesis has given way to specialization. C.P. Snow diagnosed the result in his famous 1959 lecture, “The Two Cultures”: the intellectual life of Western society had split into two camps — the literary-humanistic and the scientific — that could barely communicate with each other. Snow was writing about scientists and literary intellectuals, but the divide he identified has only deepened. Engineers do numbers, math, systems. Lawyers and political scientists do words, theories, policy. The two sides regard each other with mutual incomprehension — and occasionally with contempt. Each side suspects the other of not really thinking. The engineers think the lawyers are imprecise, inefficient, and allergic to quantitative reasoning. The lawyers think the engineers are naive, socially oblivious, and blind to the consequences of their own creations. Both complaints have some truth. And both are consequences of the same underlying problem: the people who build physical and digital infrastructure and the people who build legal and institutional infrastructure have been trained in separate traditions, speak different languages, and see different failure modes — and they have stopped recognizing each other as builders.

The schism is older than Snow’s two cultures, and deeper. The classical tradition drew a distinction between two kinds of knowledge: technē, the knowledge of how to make something — the craftsman’s skill, oriented toward producing a specified result — and phronēsis, practical wisdom, the capacity to judge and act rightly under uncertainty among competing goods, which Aristotle treated as the characteristic excellence of the statesman (Nicomachean Ethics, Book VI). The tradition was emphatic that the two were different, and that technical skill, however excellent, did not qualify one to govern: ruling required practical wisdom oriented toward the human good, not mastery of a craft oriented toward an end someone else had specified. The shipwright knew how to build the ship; he did not, by virtue of that knowledge, know where it should sail.

This book runs that relationship the other way around. The ancients asked whether the maker’s knowledge qualifies him to rule. The more pressing question now is whether the maker’s knowledge suffices to build — and the answer this book defends is that it does not. If law is part of the built environment, then building for a society, rather than merely building an artifact in isolation, requires practical wisdom and not technical skill alone. The engineer who would build for the polity needs the very faculty the classical tradition reserved for the statesman: the capacity to ask “for what, and for whom?” as part of the work rather than after it. Whether the habits of optimization can become the habits of practical wisdom — whether the two dispositions can inhabit the same mind — is a question this book raises early, demonstrates throughout, and returns to at the end. It does not pretend to settle it.

Moses’s parkways are what happens when this schism operates unchecked: an engineer exercising legal power without legal accountability, in a system where the legal and political institutions couldn’t see what was happening because the decision was embedded in concrete rather than in statute. The modern institutional form of this schism is surprisingly recent. It is artificial. And it is costly.

This book is an attempt to repair part of that schism. Its constructive ideal is a productive tension between builders and regulators: neither engineering unconstrained by governance nor governance uninformed by engineering, but a sustained institutional relationship in which each disciplines and improves the other.

The built-environment thesis has a corollary that engineers will recognize immediately. Infrastructure is not only built. It is maintained, neglected, patched, overburdened, and eventually replaced. The same is true of law. Statutes accumulate like legacy code. Obsolete doctrines persist because the dependencies built on them make replacement effectively impossible. Agencies function as maintenance organizations — and, like all maintenance organizations, they are underfunded, underappreciated, and blamed when things break. The thesis applies not only to law’s design but to its ongoing upkeep.

And the same is true of regulation. Regulation is the state’s ongoing attempt to govern complex, dynamic, technical systems — systems that are themselves designed, built, and maintained by engineers. Regulation is not a natural force. It is a designed intervention in a designed system, made by institutions that are themselves designed.

The animating idea of this book is that taking this observation seriously — not as a metaphor but as an analytical framework — changes how you understand the state, law, and regulation. If law is part of the built environment, then it can be analyzed with the same questions engineers ask of any built system: what problem does it solve? What are its operating parameters? What are its constraints? How does it fail? The great political thinkers — Hobbes, Rousseau, Constant, Weber, Arrow, North, Scott — were not engineers. But they were asking design questions. They analyzed structures, evaluated tradeoffs, proposed mechanisms, and studied failure modes. They didn’t call it engineering. But the analytical moves are ones that any engineer would recognize.

Why This Book Exists

This book is motivated by two observations.

The first is that engineers and technically minded people are often deeply interested in legal and political questions — and often deeply frustrated by them. They see legal rules that seem illogical, regulatory processes that seem irrational, and political institutions that seem to produce outcomes nobody wanted. They suspect that something is wrong with the system, but they don’t have the conceptual tools to diagnose it. When they encounter the law, they expect it to work like a specification: precise, consistent, deterministic. When it doesn’t — when the answer to a legal question is “it depends” or “maybe” — they conclude that the law is broken, or arbitrary, or merely the exercise of power.

This is understandable. But it is wrong. The law’s indeterminacy is not a bug. It is a consequence of using general rules to govern evolving facts in a world of competing values and imperfect information. Understanding why the law works the way it does — not just that it does — requires a different lens than most engineers bring to the problem.

The second observation is that the people who make decisions about how technology is governed and the people who understand the technology often inhabit different professional worlds. Legal institutions are staffed by people trained to see risk, rights, procedure, and accountability. Engineers are trained to see function, feasibility, performance, and iteration. The problem is not that one side is anti-technology and the other is pro-technology. The problem is that each side sees different failure modes — and the institutional structures that govern technology are shaped primarily by people trained in one tradition, with limited input from people trained in the other. Consider the field of “law and technology.” Its practitioners are largely drawn from law students who had an interest in technology — not from engineers who decided to engage with law. This is not a conspiracy. It is a selection effect — and it has consequences for the quality of technological governance.

The state has an immune system. When a new technology threatens existing arrangements — existing industries, existing power structures, existing ways of life — the state will respond. Not always wisely. Not always proportionately. But it will respond, because the state’s deepest imperative is to persist, and disruption is a threat to persistence. If the people who understand the technology are not at the table when the state decides how to respond, the decisions will be made by people who don’t understand what they’re governing and who have their own reasons for wanting to constrain it.

This book is preparation for being at that table.

What This Book Is — and What It Isn’t

This is not a “law for engineers” book. Those books exist, and they are useful: they introduce engineers to intellectual property, contracts, product liability, and other areas of law relevant to professional practice. They give engineers a taste of how lawyers think. But they are curated menus — they present the dishes without exploring why they are prepared the way they are.

This is not a conventional engineering-ethics textbook. Those books are useful: they introduce students to case studies, professional codes of conduct, and normative frameworks like consequentialism and deontology. Conventional engineering-ethics instruction often focuses on individual decisions, professional duties, and canonical cases. Those questions matter. They do not exhaust the problem. The social impact of the engineer’s work — and the social acceptance or rejection of what engineers build — also presents questions of political theory, institutional design, and positive political economy. Those questions cannot be answered only by asking what a virtuous individual should do.

This book is something different. It approaches the state, law, and regulation as built systems — designed, maintained, and subject to failure — and asks what an engineering perspective can contribute to understanding them. It introduces foundational ideas from political theory, jurisprudence, and institutional economics, not as abstract philosophy but as the intellectual infrastructure you need to understand the systems you live inside.

The thesis is not that law is literally engineering, or that the state is literally a machine. It is not. The state is a human institution, embedded in history, politics, culture, and power. Legal reasoning is not algorithmic. Regulation is not optimization. The book insists on these distinctions even as it argues that engineering-minded analysis has genuine value for understanding these systems.

The deeper argument is that the analytical tools of institutional analysis — breaking complex systems into components, studying interactions, identifying failure modes, designing for resilience — are shared by engineering and political thought, even though the two traditions have developed them independently and use different vocabularies. The schism between engineering and political thought is recent, artificial, and costly. This book is an attempt to stitch it back together.

Who This Book Is For

This book is written for several audiences.

First, for engineers and engineering students — the primary audience. The book aims to equip technically minded readers to understand the state, law, and regulation well enough to participate effectively in legal, regulatory, and policy debates. Not as lawyers. Not as lobbyists. As engineers who understand the design logic of the systems that govern the things they build.

Second, for anyone interested in a “how the world works” perspective on law and government. The engineering lens is not exclusive to engineers. Anyone who responds to analytical frameworks, structural analysis, and systems thinking will find something useful here.

Third, for people who already think about law and politics — law students, policy students, legal scholars — and are interested in seeing these familiar topics from an unfamiliar angle. The engineering perspective doesn’t replace legal analysis. It complements it, sometimes in surprising ways.

How to Use This Book

For general readers: Read straight through. The annotated Additional Readings at the end of each chapter are optional — they point toward fuller treatments of the topics the chapter covers, but the main text is self-contained. The separate companion teaching materials carry the classroom apparatus so that this book can remain a continuous work of argument. The companion is designed not only to reinforce the book but to test it: it supplies rival frameworks, disciplinary cautions, counterexamples, and structured ways to teach against the book’s claims.

For undergraduate instructors: Assign one chapter per week over fifteen weeks, or use one of the complete course pathways in the companion. The annotated Additional Readings in each chapter support classroom use. The companion supplies learning objectives, chapter-at-a-glance notes, discussion questions, classroom exercises, assessment prompts, rubrics, engineering-ethics and PPE/PPEL pathways, and a recurring “teach with / teach against” apparatus.

For graduate, law-school, or advanced PPE/PPEL seminars: Assign selected chapters as framing essays alongside primary texts, cases, articles, or current controversies. The companion identifies readings that deepen the chapter’s argument and readings that resist it, and it provides comparative and disciplinary pathways for seminars in law and technology, regulation, political theory, engineering ethics, and PPE/PPEL.

The Structure of the Book

The book is organized in three parts, followed by a short coda.

Part I — The State (Chapters 1–5) asks why we build states, how the state both enables and confines individual liberty, why collective decisions are irreducibly contested, why institutions determine prosperity, and how state systems see, simplify, and fail.

Part II — Law (Chapters 6–9) asks what law is, why it isn’t code, how private law structures markets, how public law structures state power, and how product liability evaluates design after harm.

Part III — Engineering, Law, and the State (Chapters 10–15) asks what happens when the legal operating structure of Parts I and II tries to govern complex technical systems. Chapter 10 establishes why regulation is necessary and difficult. Chapter 11 explains the administrative state as an institutional design. Chapter 12 shows why simple rules produce unintended consequences in complex adaptive systems. Chapter 13 shows why sophisticated regulated actors game rules. Chapter 14 explains why regulatory design is always second-best. Chapter 15 develops adaptive regulation as the constructive response.

The Coda returns to the book’s opening themes. Engineers already participate in governance whenever they build systems that allocate access, risk, power, or knowledge. The only question is whether they will do so invisibly and naively, or visibly and responsibly.

A Note on Method

A book that tries to build an analytical framework from Hobbes, Rousseau, Constant, Weber, Arrow, Rawls, Nozick, North, Acemoglu and Robinson, Mokyr, Marx, Popper, Scott, Holmes, Coase, and Ostrom — to name only the most prominent thinkers — owes the reader a candid statement about what it is doing.

It is not doing intellectual history. It is not providing a comprehensive account of any thinker’s ideas. Each of these figures has generated a vast scholarly literature, and specialists will find the treatments here selective, sometimes contestably so. The book reads Hobbes through game theory, Arrow through institutional design, Marx through failure-mode analysis, and Mokyr through regulatory dialectics. These are productive readings, but they are not the only readings, and the book does not claim otherwise.

What the book is doing is building a vocabulary — a set of analytical tools for understanding the relationship between the state, law, regulation, and the things engineers build. The thinkers are recruited to that project. Where the recruitment involves simplification — and it always does — the Additional Readings sections at the end of each chapter point the reader toward fuller accounts. “What Hobbes meant” and “how Hobbes’s ideas function as analytical tools” are different projects. This book is doing the second.

The engineering translations in this book are analytical reconstructions. They are not claims that Hobbes secretly practiced game theory, that Scott was doing control engineering, or that legal and technical systems are interchangeable. The translations isolate a structure that engineers can recognize and then ask what the comparison reveals — and where it breaks.

The core text advances a position. It does not attempt to stage every objection inside every chapter. The companion teaching materials do that work. They place the book’s arguments in conversation with competing normative, historical, legal, economic, and institutional perspectives so that instructors can teach with the book, around it, and against it without turning the core manuscript into an ecumenical survey.

Parts II and III draw principally on United States law and institutions. The analytical framework is intended to travel, but particular doctrines and institutional arrangements do not. The companion identifies comparative materials and asks students to test which claims survive when the legal architecture changes.

A Note on Tone

This book is institutionally realist. It is not anti-regulatory. Regulation is necessary in modern interconnected systems — the book argues this explicitly. But regulation is hard, and poorly designed regulation has predictable failure modes. The book takes those failure modes seriously without concluding that the answer is less regulation.

The method throughout is comparative institutional analysis: evaluating institutions not against an imaginary ideal but against the actually available alternatives, each with its own costs and failure modes. The question is never “is this institution perfect?” — no institution is. The question is “does this institution perform better than the realistic alternatives, given the costs of transition?” Harold Demsetz called the failure to ask this question the nirvana fallacy: comparing a flawed real institution to a flawless imaginary one. This book tries to avoid that fallacy consistently, which means acknowledging the costs of regulation without pretending that unregulated markets are costless, and acknowledging the costs of markets without pretending that regulation is free.

Equally, the book is not technocratic. It does not argue that experts should “just optimize everything.” Regulation is a design problem, but it is a design problem embedded in politics, legitimacy, law, institutional incentives, and dynamic technical systems. The engineer who thinks that political problems can be solved by better algorithms has not yet understood what a political problem is. This book aims to provide that understanding.

The style throughout is clear, conceptually ambitious, and accessible. It uses concrete examples and engineering analogies, but it does not overclaim that law is literally engineering or that the state is literally a machine. These are human institutions. The engineering lens illuminates them. It does not replace the need to understand them on their own terms.

An Invitation

I don’t mean to romanticize the past. Benjamin Franklin was unique among his peers; philosopher-kings are always few. And specialization is both a necessity and a benefit in the modern world. We should, however, consider what of importance has been lost and think about how we might recover it.

This book’s thesis is built on a belief that a little interdisciplinary knowledge can go a long way. Understanding what the state is, how law operates, and why regulation fails the way it does will not make you a lawyer or a political scientist. It will make you a more effective engineer, a more informed citizen, and a more capable participant in the decisions that will shape the systems we all live inside.

The state and the law are built systems that govern other built systems. If you build things for a living, you should understand the systems that govern what you build. This book is the place to start.