Sovereignty
What it means to be sovereign on the substrate
Sovereignty on the substrate is not a tier or an add-on. It is a set of structural guarantees, about who controls the keys, who can inspect the data, and what rights participants hold, that apply across every deployment mode.
Structural, not contractual
The substrate's sovereignty guarantees are built into the architecture, not promised in a contract. Outbound connections from sovereign deployments are structurally disabled, not just configurable. Key management stays with the operator, not with Sovern Digital.
Right to fork, guaranteed
Every deployment, regardless of mode, carries the constitutional right to fork. If an operator ceases operations or an expression is discontinued, participants can export their full coordination record and continue on a compatible substrate without permission.
Participant sovereignty
Individual participants hold sovereignty too. Their identity, their mandates, and their coordination record are portable by right, not by operator grace. The substrate is designed so that participants can leave and take their history with them.