Reference Stack and Exit

A reference stack shows how the parts of Sovereign Source AI fit together. No single product is required. The stack shows governed execution, and it shows that the institution keeps control. The stack passes if the organization can replace providers, move runtimes, and continue critical operations. During these changes, the organization must keep its intent, knowledge, authority, and evidence.

Reference build

The seven layers map to components with separate responsibilities:

LayerReference components and roles
IntentTyped intent registry, requirements, experience contracts, and an SSIL interpreter or compiler
GovernanceInstitutional identity, authority records, external policy gates, classifications, and approvals
DecisionRouter for deterministic rules, statistical models, bounded models, reasoning models, and humans
CapabilitySkill registry, declared operation contracts, permission checks, and authenticated tool access
ExecutionDurable workflows, work orders, isolated workers, services, and deployment definitions
VerificationTests, evaluations, security analysis, requirement checks, release gates, and outcome measurement
EvidenceProvenance relationships, component inventories, artifacts, attestations, audit records, and historical outcomes

The ontology connects these components through shared institutional objects. Interfaces show those objects and their authorized actions. Storage keeps current state and historical evidence. The institution’s rules do not live only in the interface or in a model provider.

The four durable planes cover the whole stack:

Together they support the loop Intent → Decide → Constrain → Execute → Verify → Prove.

Seven sovereignty tests

The manifesto’s seven questions become concrete tests of the reference architecture:

  1. Can the primary vendor be replaced without rebuilding the institution? Contracts, ontology definitions, policies, workflows, and evidence stay usable outside that vendor’s application.
  2. Can the runtime move to another environment? Execution definitions, dependencies, state, and policy boundaries stay valid in the destination environment.
  3. Can the organization retain and reconstruct its data and knowledge? Exported records keep relationships, history, source material, and the context of each derivation.
  4. Can agent permissions and actions be inspected? Work orders identify authorized capabilities, applicable policy, approvals, and recorded actions.
  5. Can models be swapped without rewriting business logic? Typed contracts and the router keep institutional rules separate from the behavior of a specific provider.
  6. Can critical functions operate privately or in restricted networks? Required models, dependencies, authorization, and evidence services stay available inside the permitted boundary.
  7. Does the organization retain identity, keys, policy, authorization, provenance, and audit? The organization keeps control of these functions after the provider contract ends.

A documented export feature is only part of the answer. The institution must also show evidence that its operations can continue on the exported material.

Replacement paths

You can replace a part if its adapter keeps the same definitions for the institution. You can change one part and keep the records that depend on it:

Exit also depends on permissions and practical access. Source code is not enough without operational state, usable dependencies, keys, and deployment definitions. You must be able to move the whole governed system and its knowledge, not only the code.

Product layers

The product structure puts these responsibilities into six parts:

The core holds ontology, authority, intent, policy, and evidence. The control plane governs models and capabilities. The factory makes verified artifacts. The data platform keeps state and history. Enterprise bridges connect the systems that the organization already has. Vertical products adapt the shared architecture for specific domains.

Commercial services can supply any of these components. Each service must let you examine it. It must use portable contracts, and you must be able to replace it.

From the research

All topics