Version: 1.0 — June 2026
Status: Ratified
Canonical Language: English
Sovereign intelligence shall not depend on a single language, jurisdiction, cloud provider, or implementation.
We, the contributors of SovereignStack, establish this Constitution to govern the development, governance, and evolution of the Sovereign Intelligence Network. This document is the supreme governing document of the project. All RFCs, standards, and project policies derive their authority from this Constitution.
SovereignStack exists to realize a world in which intelligence itself — artificial and human — can operate freely across sovereign boundaries without compromising the autonomy, privacy, or security of any participant.
Every participant in the Sovereign Intelligence Network retains full sovereignty over their own data, models, compute, and decisions. No participant may compel another to act against their sovereign will.
All protocols and standards shall be designed for maximum interoperability across implementations, jurisdictions, and hardware platforms.
Every operation in the network must be cryptographically verifiable. Trust is not assumed — it is proven through signatures, Merkle audits, and provenance graphs.
Agents, sessions, capabilities, and intelligence assets shall be portable across nodes, clouds, and jurisdictions without vendor lock-in.
The governance, code, standards, and decision-making processes of SovereignStack shall remain open, transparent, and accessible to all participants.
The TSC is the highest governing body of the project. It is responsible for:
- Ratifying amendments to this Constitution
- Approving or rejecting RFCs
- Appointing and removing Core Maintainers
- Resolving disputes escalated through the governance process
- Defining the strategic roadmap
Composition: 5–9 members, serving staggered 12-month terms.
Core Maintainers manage the day-to-day technical direction of the project. See GOVERNANCE.md for detailed roles.
Working Groups are temporary or permanent bodies focused on specific domains such as Security, Federation, Memory, and Conformance.
Domain experts who evaluate RFCs for technical soundness, security implications, and ecosystem compatibility.
All significant changes follow the RFC process:
Draft → Discussion → Accepted → Implemented → Stable → Deprecated
An RFC is ratified when:
- Minimum 14-day review period has elapsed
- TSC majority vote in favor
- No unaddressed security concerns
In cases of critical security vulnerabilities or existential threats to the network, the TSC may fast-track amendments with 48-hour review and 2/3 majority vote.
Any participant may fork the project at any time, in accordance with the license.
All participants have the right to inspect the full audit trail of the reference implementation.
Participants may exit the network at any time and retain full ownership of their data, models, and sessions.
All participants have the right to contribute, propose RFCs, and participate in governance discussions without discrimination.
The Open Autonomous Sovereign Architecture (OASA) defines three certification tiers:
| Level | Name | Requirements |
|---|---|---|
| L1 | Sovereign-Ready | Conformance with core object model, URI standard, and audit |
| L2 | Secure-Runtime | L1 + encryption at rest, policy enforcement, identity verification |
| L3 | Strict-Sovereign | L2 + hardware attestation, offline capability, no external dependencies |
Nodes may declare one or more jurisdictions. Cross-border data transfers must comply with all applicable legal frameworks, including GDPR, EU AI Act, and others.
Any contributor may propose an amendment to this Constitution via pull request.
Amendments must remain open for public comment for a minimum of 30 days.
Amendments require a 2/3 supermajority vote of the TSC and a 14-day community review period.
In the event of project dissolution, all assets — including specifications, code, and documentation — shall remain available under the project's open-source license. The Merkle audit root shall be permanently archived on at least three independent public repositories.
This Constitution is ratified by the consensus of the SovereignStack contributors and does not require individual signatures. All contributions to the project imply acceptance of this Constitution.
Appendix A: GOVERNANCE.md — Detailed governance procedures
Appendix B: CONTRIBUTING.md — Contribution guidelines
Appendix C: CODE_OF_CONDUCT.md — Code of conduct
Appendix D: OASA.md — OASA specification