The Core Manifesto
Software should adapt to people, not force people to adapt to software.
Modern software provides extraordinary capabilities, yet many applications make ordinary work dependent on remote services, vendor accounts, opaque decisions, and business models that can change without the user's consent. These arrangements can be convenient, but convenience becomes dependence when a person cannot continue working, retrieve their records, or leave a provider without unacceptable loss.
Sovereign Software is a deliberate alternative: software designed so that ultimate authority remains with the person or organization using it, not with a vendor, an infrastructure operator, or an unaccountable algorithm. It need not reject networks, commercial software, artificial intelligence, or complex engineering. It rejects unnecessary surrender of control.
Four Foundational Principles, in a Deliberate Conceptual Order:
Authority belongs to the user. Users retain meaningful control of their data, essential capabilities, and ability to leave or replace providers.
Information outlives software. Records and intellectual work remain accessible, interpretable, and recoverable after applications, vendors, and runtimes disappear.
Independence is designed in. Capabilities that can reasonably operate on user-controlled hardware do not depend unnecessarily on external connectivity or permission.
Consequential behavior remains governable. Users can understand, inspect, authorize, and, where feasible, reverse or contest significant actions taken on their behalf.
A Relationship, Not a Ranking
- Sovereignty defines the goal.
- Longevity protects it across time.
- Locality provides a powerful means of independence.
- Transparency and Control make authority meaningful in operation.
The order communicates a relationship, not a scientifically measured ranking. All four matter, and no single numerical score can excuse a proven loss of fundamental user control. These principles do not prescribe a programming language, database, license, operating system, or user-interface style. They establish what an implementation must make possible.