Sovereignty — Harobanda

You do not truly own a system you cannot rebuild, whose updates you cannot decline, and whose support ends on a date someone else chose. These are not hypotheticals. A major phone maker once removed the ability to unlock the bootloader on every device it had sold, worldwide, in a single update, with no warning. When the vendor lives inside the system, the vendor decides — and can decide against you.

The phone is the extreme, and worth naming plainly: the vendor fuses the hardware and the software so that neither can leave the other. Sovereignty is the opposite. You choose ordinary, replaceable hardware, and you own the system that runs on it; the two are joined by your declaration, not by a vendor's weld. Sovereignty here has exactly one meaning — nothing anyone else can withdraw — and it has never meant “every line is ours.” The kernel underneath is kept as source fixed by its fingerprint, and built by your own compiler: borrowed, but impossible to take back. And the whole machine is one text file plus a short list of exact fingerprints, which you can hand to any provider you choose. Reversibility stops being a clause in a contract and becomes the thing itself.

An example

An organisation whose most sensitive records must never leave its walls cannot prove that on a system it does not control. A declared machine can: one line says the box knows no route to the outside world, and the court refuses to build the machine if anything on it contradicts that line. “The data stays here” stops being a promise on paper and becomes a fact the machine itself enforces. Compare the usual offer — a management console the vendor lets you build, while the agent, the service and the ownership stay theirs: you own the screen, not the power.

Sovereignty is what no one else can withdraw.