Every border is a protocol — a set of rules governing what crosses and what doesn't. We think of borders as lines on maps, fixed and geographic. But the more useful way to understand them is as interfaces: negotiated boundaries between systems that must interact without fully merging.
This framing changes how you think about almost everything — from national boundaries to API rate limits, from immigration policy to firewall rules. A border isn't just a wall. It's a membrane with selective permeability, and the rules of permeability tell you everything about the systems on either side.
Borders as Interfaces
Consider the internet itself. The network was designed with borders everywhere: between private and public address spaces, between autonomous systems, between application layers. Each border has a protocol. TCP/IP is a border protocol. HTTPS is a border protocol. CORS is a border protocol. They don't prevent crossing — they govern it.
National borders work the same way, just with different protocols. Visa regimes, customs declarations, trade agreements — these are all protocol specifications for how entities cross from one jurisdiction to another. The interesting question is never "should there be a border?" but rather "what protocol does this border implement, and who gets to change it?"
The most consequential borders are the ones you don't notice — not because they're invisible, but because their protocols have become so embedded in your behavior that crossing them feels natural.
The Protocol Stack of Sovereignty
Sovereignty itself can be understood as a protocol stack. At the base layer: territorial control, the ability to enforce rules within a physical boundary. Above that: legal jurisdiction, the framework that determines which rules apply to whom. Above that: economic policy, the rules governing what flows in and out. And at the top: cultural identity, the shared narratives that make the whole stack feel coherent.
When you see geopolitical tension, what you're usually seeing is a disagreement about which layer of the stack takes precedence.