Sovereignty is not a contract clause. It is a topological property of the system.

For a decade, the European posture on data sovereignty has been fundamentally textual. We wrote it into Data Processing Agreements, into Standard Contractual Clauses, into Schrems II transfer impact assessments. We treated sovereignty as a property that could be guaranteed by language — by careful drafting, by negotiated clauses, by audit attestations.

The March 2026 precedent has made that posture untenable. A clause that can be amended by the counterparty, at the counterparty's convenience, under foreign jurisdiction, is not a guarantee. It is a memorandum of present intent.

A guarantee that can be revised unilaterally is, in operational terms, indistinguishable from no guarantee at all.

Topology is the study of which properties survive deformation — which features of a system remain true regardless of how the surface is stretched, twisted, or relabelled. Applied to cognitive infrastructure, the question becomes: which properties of this system hold even if every contract is rewritten tomorrow?

The answer is short. The properties that survive are the ones encoded in the wiring: where the silicon physically sits, where the inference physically runs, which keys physically exist on which machines, and which audit records physically accumulate under whose custody.

A cognitive system can claim sovereignty only if five invariants hold simultaneously. Each is a physical or cryptographic fact, not a contractual one.

1. Locality of inference. The model weights execute on hardware whose physical location is verifiable by the operator.
2. Locality of state. Vectors, embeddings, and intermediate context never leave the perimeter — not for "telemetry", not for "model improvement", not for "support".
3. Custody of keys. Signing and encryption keys are generated on, and never leave, hardware under the operator's physical control.
4. Custody of audit. The tamper-evident record of every reasoning step is held by the operator and exportable to regulators on demand.
5. Independence of runtime. The system continues to reason if the upstream vendor disappears, is acquired, or is enjoined by a foreign court.

Sovereignty is the conjunction of five physical facts. Strike one and the property collapses.

Contracts are still necessary. They allocate liability, define service levels, and provide a forum for disputes. But they are downstream of architecture, not a substitute for it. A well-drafted DPA over a hyperscaler perimeter is a high-quality promise about a system that, structurally, cannot keep it.

The Cognitive Server inverts the relationship. The system is sovereign by construction; the contract simply documents what the topology already enforces.

When European industrial operators ask "is this AI sovereign?", they are asking a question about the wiring diagram, not the cover page. The answer is found by tracing the path of a single prompt: where it is read, where it is reasoned over, where its evidence is stored, and whose hands can interrupt the chain.

If that path stays inside the operator's perimeter — verifiably, cryptographically, physically — the system is sovereign. If any link leaves, no contractual language can bring it back.