Control of AI matters
more than model size.
The organizations that get value from AI can defend their numbers to an auditor. They can replace a vendor without a rebuild, and move a runtime without a rewrite. They can trace each artifact to an intent that they own.
The problem
Many organizations use AI. Few of them control it.
A model on your own server can still lock you in. The lock can come from APIs, identity, proprietary data, or prompts that nobody documented. It can also come from agent runtimes, workflow engines, cloud infrastructure, or one provider that you cannot replace. An open-weight model on your server does not make you sovereign. A self-hosted application does not make you sovereign.
Sovereignty is a property of the full system.
What sovereign means
A system is sovereign when you can own, inspect, govern, deploy, change, move, and run all of it without any single external provider.
This covers source code, application state, data, documents, ontologies, prompts, models, embeddings, agents, skills, and tools. It covers APIs, MCP servers, workflows, dependencies, datasets, weights, infrastructure, secrets, and identity. It covers authorization, audit, provenance, evidence, deployment definitions, builds, jurisdictions, and approvals. It also covers your right to export or replace each of them.
You can use commercial services. You must keep control and a credible way to leave.
A sovereign system can answer yes to these seven questions:
- Can you replace the main vendor without a rebuild of the institution?
- Can you move the runtime to another environment?
- Can the organization keep its data and knowledge, and build them again?
- Can you inspect the permissions and actions of each agent?
- Can you change models and keep the same business logic?
- Can critical functions run privately or in restricted networks when the rules require it?
- Does the organization keep control of identity, keys, policy, authorization, provenance, and audit?
The architecture
Sovereign Source AI has seven layers that support each other:
- Intent What a person or institution wants to do. It is a typed object that links to requirements, constraints, authority, and outcomes that you can measure.
- Governance Authority, policy, data classification, jurisdiction, model and tool permissions, network access, and approvals. Authorization is outside the model. A model can propose an action. It cannot give itself permission.
- Decision Deterministic rules, bounded models, statistical inference, LLMs that reason, and human judgment.
- Capability You declare each operation and its permissions. The system makes them available as Sovereign Skills and MCP-style interfaces.
- Execution Isolated agents, workers, workflows, services, and infrastructure.
- Verification Tests, evaluations, policy checks, security analysis, simulation, approvals, and measurement of outcomes. These checks change claims into evidence.
- Evidence Durable provenance records that link intent to decisions, actions, artifacts, releases, and outcomes.
Each layer has a topic page. Start with the architecture overview, or read how you can replace each part and leave.
The evidence chain shows the full history of each artifact. It has 13 steps:
- source
- observation
- interpretation
- intent
- requirement
- decision
- work order
- execution
- artifact
- verification
- approval
- deployment
- outcome