Legal Infrastructure must be Sovereign Infrastructure
Every well-functioning legal system is sovereign. The sovereignty of next generation techno-legal infrastructure must be a design choice. Infrastructure hardens quickly once it is in the ground, and once it is hardened the jurisdictions that did not think about sovereignty at the design stage will discover that their legal systems have become, quietly and without anyone having decided this, creatures of whichever technology stack reached market first.
Legal Infrastructure Is Sovereign Infrastructure
Legal infrastructure is sovereign. The courts sit within a constitutional order, the statutes are enacted by a legislature accountable to a population, the lawyers and judges hold their warrants from a state that can revoke them, and the duties owed by directors and fiduciaries run to jurisdictions that can enforce them. None of this is decorative. It is the reason a contract in Sydney is different from a contract in Singapore, and the reason it matters which one you are standing in when something goes wrong.
Analogue legal infrastructure was sovereign by default. It had to be. Courts are physical places in a country, statute books are enacted under a constitution, and the professional classes who operate the system hold practising certificates issued by bodies that answer, eventually, to a parliament. Sovereignty was baked into the physics of how law was produced and enforced, which meant nobody had to design it in. It came for free with the substrate.
That default is now at risk. As law gets rebuilt to operate at machine speed as the sixth layer in the AI Cake, the substrate changes. What replaces the courtroom and the statute book is software, protocols, identity systems, and compute. Any of these can be sovereign. None of them are sovereign by default. The danger is not that someone sets out to strip law of its sovereign character. The danger is that techno-legal infrastructure gets built the way most infrastructure gets built now, by whoever moves first, on whatever stack is cheapest, hosted wherever the latency is lowest, and that the sovereignty question gets asked years later when the answer is already locked in.
Three angles on why this matters
-
Legal infrastructure is a national security asset in the same sense that the payments system and the power grid are national security assets. If an adversary can compromise the registry that records who owns what, or the identity system that establishes whose agent acted on whose behalf, or the attribution layer that determines who is liable when harm occurs, then the adversary has compromised something more fundamental than any individual database. The capacity of the state to adjudicate, to enforce, and to assign responsibility depends on these systems working. A legal infrastructure hosted entirely on foreign-controlled compute, running on foreign-controlled identity standards, settling through foreign-controlled registries, is a strategic vulnerability regardless of how well it is engineered. Engineering quality is not a substitute for jurisdictional control.
-
Privacy law is the place where most jurisdictions have already worked out, painfully and incompletely, that data is not neutral territory. The GDPR settlement, the Schrems decisions, the long-running disputes over data transfers between Europe and the United States, the Australian Privacy Act reforms, all proceed from the same premise: it matters which sovereign can reach the data, because reaching the data means reaching the people the data is about. Techno-legal infrastructure carries the same problem in a sharper form. The data flowing through a legal attribution system is not incidental personal data. It is the record of who did what, under whose authority, to produce what consequence. If that record is controlled from outside the jurisdiction, the jurisdiction has lost something it will find difficult to get back. Constitutional protections that were designed around physical territory and national institutions do not extend automatically to infrastructure that sits in someone else's cloud.
-
The legal system is held together by people who owe duties to jurisdictions. Lawyers owe duties to the courts they are admitted to and the clients they represent under that admission. Directors owe duties under the corporations law of the place where the company is registered. Auditors, trustees, financial advisers, medical practitioners, engineers, each of these roles exists as a bundle of obligations enforceable by a particular state against a particular person. The duties are not portable. A director who discharges obligations competently under Delaware law has not thereby discharged obligations under Australian law, and the director who tries to do both from inside the same AI-mediated decision pipeline is currently doing so without infrastructure that can tell the two apart.
If techno-legal infrastructure is built without regard for jurisdiction, the people holding these duties will find themselves in an impossible position. They will be asked to answer to their home regulator for decisions produced by systems the home regulator cannot inspect, audit, or compel. They will be asked to certify compliance with local law using tools that have no local law hooks in them. The duty does not evaporate because the infrastructure ignores it. It falls on the duty-holder, personally, and the infrastructure shrugs.
What is actually at stake
The sovereignty of analogue legal infrastructure was a product of its physical form. The sovereignty of techno-legal infrastructure will be a design choice, or it will not exist. That is the situation now, and it will not stay open for long. Infrastructure hardens quickly once it is in the ground, and once it is hardened the jurisdictions that did not think about sovereignty at the design stage will discover that their legal systems have become, quietly and without anyone having decided this, creatures of whichever technology stack reached market first.