Sovereignty · who owns what
Your operating record stays yours.
Seven governed layers keep data, meaning, model choice, workflows and decision authority portable so the organization can keep operating as technology changes.
Review the sovereignty model →Operational records → Residency, retention and access remain explicit
- Ownership
- Residency
- Export
Seven layers build from data boundary through compute, model choice, semantic definitions, workflows and decision rights to a retained operating record.
Chosen per workload, not sold as a toggle.
The same operating layer runs at three levels of assurance. Sensitive records and regulated data sit at the strong end of that gradient.
Stated plainly, in writing.
Yours
- Your operating data
- Your metric definitions and their version history
- The decision ledger and outcome history
- Models or tuning artifacts contractually assigned to your operation
- Exportable in agreed open formats under the engagement terms
Never
- Your data sold, shared, or used to train another client's intelligence
- Provider retention or training use outside the approved terms
- Definitions or model versions changed beneath you without your approval
- Unapproved export fees, surprise egress penalties, or audit-as-revenue
Ours
- The platform and runtime
- The agent framework
- The delivery teams
- The product roadmap
The exit door stays unlocked.
No model lock-in
The layer is model-agnostic. Your ontology, workflows, and record live outside any model, so models stay swappable inputs. A better model next year is an upgrade, not a migration.
Your record is scoped to your use
Where a workflow earns a task-specific model or tuning artifact, ownership, reuse, retention, and export are defined in the engagement terms. Your operating playbook does not become another client's feature.
No rules changed beneath you
Definitions are versioned and model versions are pinned per workflow. Changes route through your approval, on your calendar, never silently mid-season.
Human authority is retained
Recommendations carry their sources, and consequential actions are designed to require an authorized human decision. Sovereignty includes who is allowed to act.
Evaluation is part of the boundary
Accuracy, permission behavior, writeback, refusal, and rollback are checked against the workflow before expansion. The assurance bar changes with the action and the environment.