01 / Data boundary
Operational records → Data location, retention and access remain explicit
Ownership · Data location · Export
Sovereignty · who owns what
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 → Data location, retention and access remain explicit
Seven layers build from data boundary through compute, model choice, semantic definitions, workflows and decision rights to a retained operating record.
Seven governed layers keep data, meaning, model choice, workflows and decision authority portable so the organization can keep operating as technology changes.
Operational records → Data location, retention and access remain explicit
Ownership · Data location · Export
Approved environments → Workloads execute inside the chosen boundary
Hosted · Dedicated · Your cloud
Client-selected models → Models remain replaceable inputs, not the record
Portable · Versioned · Replaceable
Metrics, entities and rules → Meaning is governed outside any single model
Ontology · Definitions · History
Context and operating procedure → Recommendations follow bounded, reviewable paths
Context · Procedure · Lineage
Roles, permissions and thresholds → Consequential action stays with authorized people
Authority · Approval · Audit
Sources, decisions and outcomes → A portable record the organization retains
Evidence · Decisions · Outcomes
The same operating layer runs at three levels of assurance. Sensitive records and regulated data sit at the strong end of that gradient.
Yours
Never
Ours
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.
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.
Definitions are versioned and model versions are pinned per workflow. Changes route through your approval, on your calendar, never silently mid-season.
Recommendations carry their sources, and consequential actions are designed to require an authorized human decision. Sovereignty includes who is allowed to act.
Accuracy, permission behavior, writeback, refusal, and rollback are checked against the workflow before expansion. The assurance bar changes with the action and the environment.