How it works.

Sovereignty is usually sold as a policy: a promise about where data will be held and who will be permitted to look at it. Policies can be audited, but they cannot be enforced by the machine itself. We treat sovereignty as an architectural property instead.

The appliance holds its own data, its own models, and its own records. Nothing in normal operation requires a route to the outside, so the default posture at the network boundary is deny. Connections are not blocked after the fact — they are absent until someone declares them, and every declared route is logged and reviewable.

The practical consequence is narrow and useful: there is no misconfiguration that quietly sends your documents somewhere else, because there is no destination to send them to.

Air-gapped systems still need maintenance, and the usual answer — open a connection briefly — defeats the reason the gap exists. Element 31 delivers updates as signed release bundles: a complete, versioned set of software and model artifacts, built and signed before it leaves our hands.

The bundle crosses on physical media. The appliance verifies the signature and the contents before applying anything, refuses what it cannot verify, and records what was installed and when. The gap is never bridged. Something is carried across it.

A buyer who cannot say where a machine came from cannot say very much about it at all. Integration, sealing, software load, and final assembly are performed in the United States, and that sequence is treated as part of the product rather than a logistics detail.

Treating provenance as a requirement constrains earlier decisions: what the enclosure is made of, how it closes, where the software image is produced, and what evidence exists that the unit in front of you is the unit that left the line. We would rather answer that question with a record than with a reassurance.