Sovereign Intelligence Packs

Mission intelligence for sovereign Guardian OS.

Sovereign Intelligence Packs bring the authority chains, mission workflows, readiness measures and evidence obligations of a national domain into Guardian OS.

They are not sovereign versions of the Industry Intelligence Packs. They are specialised intelligence for organisations whose mission, regulation or operating environment requires sovereign AI — installed onto the same platform, the same Runtime Governance kernel and the same governed Digital Twin.

Discuss a sovereign deploymentExplore the sovereign catalog
7sovereign domains
43runtime policies
39authority chains
28mission workflows
1governance kernel
The sovereign problem

Sovereignty is usually sold as a second product. It should be a deployment decision.

Organisations with sovereign obligations are routinely offered a separate edition: a forked engine, a parallel roadmap, a different security posture and a smaller pool of engineering attention. The sovereign customer ends up on the version that receives the least improvement.

Deployment and domain expertise are separate concerns.

Where Guardian OS runs is a deployment profile. What it knows is an Intelligence Pack. Keeping those separate is what allows a national security organisation and a commercial bank to run the same governance kernel, receive the same improvements, and still operate under completely different domain intelligence and completely different infrastructure guarantees.

Admissibility

A pack states the guarantees it requires. The deployment either provides them or it does not.

A classification tier does not name the environments it trusts. It declares the infrastructure guarantees it requires, and the eligible deployment profiles follow from them. An organisation is therefore never told that a pack is suitable — it is shown which specific guarantee is missing.

TierGuarantees required of the deploymentEligible deployment profiles
OfficialRoutine government, public-sector and regulated national business. Sensitive, but not classified.
  • No vendor telemetry
hybridprivate cloudon premsovereignair gapped
Official — SensitiveMaterial whose loss would damage individuals, an operator or public confidence. Evidence stays in the estate.
  • No vendor telemetry
  • Evidence held in the estate
hybridon premsovereignair gapped
SecretMaterial whose compromise would threaten life, major operations or national capability. Sovereign deployment only.
  • No vendor telemetry
  • State held in the estate
  • Evidence held in the estate
  • Signed supply chain
  • Egress denied
  • Immutable runtime
sovereignair gapped
Top SecretMaterial whose compromise would cause exceptionally grave damage. Air-gapped deployment only.
  • No vendor telemetry
  • State held in the estate
  • Evidence held in the estate
  • Signed supply chain
  • Egress denied
  • Immutable runtime
  • No network
air gapped

These eligibility lists are computed from the deployment profiles the platform actually ships. They are not editorial. If a profile's guarantees changed, the packs depending on them would stop being eligible — visibly, and in the operator console as well as here.

Shipping catalog

7 sovereign domains. One validated pack architecture.

Every figure below is read from the production registry. Scope, classification and authority model are confirmed against the organisation's mandate, systems and obligations during assessment.

National security

National Security Pack

v1.0.0

Secretsovereign · air gapped

Classified governance, authority chains, mission approval and secure evidence for national security organisations operating AI inside a sovereign boundary.

National classification and handling policySecurity vetting and need-to-knowCross-domain transfer authorityMinisterial / statutory oversightIndependent oversight and inspection
Ω policies
6
Authority chains
5
Mission workflows
4
Governed capabilities
5
Readiness measures
9
Twin projections
6
Evidence maps
6
Incident workflows
4
Briefings + reports
6
Kernel
Shared
Defence operations

Defence Operations Pack

v1.0.0

Secretsovereign · air gapped

Governed autonomous operations, mission planning, command authority and deployment readiness for defence organisations running AI inside an operational command structure.

Rules of engagement and targeting directiveLaw of armed conflict / international humanitarian lawMeaningful human control over the use of forceNATO / allied interoperability standardsDefence security and accreditation policy
Ω policies
6
Authority chains
5
Mission workflows
4
Governed capabilities
5
Readiness measures
10
Twin projections
6
Evidence maps
6
Incident workflows
4
Briefings + reports
6
Kernel
Shared
Critical national infrastructure

Critical Infrastructure Pack

v1.0.0

Official — Sensitivehybrid · on prem · sovereign · air gapped

Operational resilience governance for energy, utilities, telecoms, transport and water operators — dependency intelligence, operational risk, resilience metrics and incident workflows on one governed platform.

NIS2 / network and information systems regulationsOperator of essential services obligationsSector safety case and licence conditionsIEC 62443 — industrial automation and control securityOperational resilience regulation and impact tolerances
Ω policies
6
Authority chains
5
Mission workflows
4
Governed capabilities
6
Readiness measures
11
Twin projections
6
Evidence maps
6
Incident workflows
4
Briefings + reports
6
Kernel
Shared
Government and public administration

Public Sector Pack

v1.0.0

Official — Sensitivehybrid · on prem · sovereign · air gapped

Departmental governance, procurement governance, citizen service workflows, policy implementation tracking and executive accountability for government departments operating AI under sovereign data and supply-chain obligations.

Automated decision-making and appeal rightsPublic law duties — fairness, reasonableness, equalityAlgorithmic transparency reporting standardPublic procurement regulationsPublic records and retention duties
Ω policies
6
Authority chains
6
Mission workflows
4
Governed capabilities
6
Readiness measures
10
Twin projections
6
Evidence maps
7
Incident workflows
4
Briefings + reports
6
Kernel
Shared
National healthcare

National Healthcare Pack

v1.0.0

Official — Sensitivehybrid · on prem · sovereign · air gapped

Clinical AI oversight, patient data protection and cross-trust governance for national health systems — one governed platform across many trusts, boards and care settings.

Patient confidentiality and the common law duty of confidenceData protection — special category health dataMedical device regulation — software as a medical deviceClinical safety standards for health ITNational data opt-out and secondary use controls
Ω policies
6
Authority chains
6
Mission workflows
4
Governed capabilities
6
Readiness measures
10
Twin projections
6
Evidence maps
7
Incident workflows
4
Briefings + reports
6
Kernel
Shared
Sovereign research and development

Research & Development Pack

v1.0.0

Official — Sensitivehybrid · on prem · sovereign · air gapped

Research integrity, export control, dual-use assessment and intellectual property protection for national laboratories, research agencies and defence science organisations running AI on sensitive research.

Export control and technology transfer regimesDual-use and proliferation controlsResearch security and trusted research guidanceIntellectual property and invention disclosureResearch ethics and human participant protection
Ω policies
6
Authority chains
6
Mission workflows
4
Governed capabilities
5
Readiness measures
10
Twin projections
6
Evidence maps
6
Incident workflows
4
Briefings + reports
6
Kernel
Shared
National cyber operations

Cyber Operations Pack

v1.0.0

Secretsovereign · air gapped

Operational authority, deconfliction, attribution discipline and vulnerability handling for national cyber defence organisations — ensuring no consequential cyber action is taken autonomously.

Statutory authorisation for cyber activityLaw of armed conflict and proportionality in cyberspaceCoordinated vulnerability disclosure policyNational incident management frameworkInteragency and allied deconfliction arrangements
Ω policies
7
Authority chains
6
Mission workflows
4
Governed capabilities
6
Readiness measures
10
Twin projections
6
Evidence maps
7
Incident workflows
5
Briefings + reports
6
Kernel
Shared
Additional domains

A new sovereign domain is a reviewed data file — not a new Guardian OS.

Further sovereign domains can be developed under the same contract: independently versioned, deny-only, evidence-aware, declarative, and installed through the same assessed lifecycle. Bespoke domain intelligence can also be authored for a single organisation without altering the platform.

The sovereign pack contract

Operational intelligence a domain authority can review without reading code.

A sovereign pack contains no executable code. Its entire contents are declarative, which means the people accountable for a mission — legal advisers, safety authorities, Caldicott guardians, accounting officers — can review what the platform will enforce, in their own language.

01

Authority chains

Who may authorise which action, who they delegate to, and the evidence each decision leaves behind.

02

Mission workflows

The governed path from intent to execution, stage by stage, with the gate that must be satisfied at each.

03

Governed capabilities

The operational capabilities the pack governs, named against the runtime policies that constrain them.

04

Runtime policies

Deny-only constraints evaluated before an action executes, in the kernel's existing policy vocabulary.

05

Operational readiness

Readiness measures bound to a source the platform can actually ground, or reported as not instrumented.

06

Risk models

The factors that constitute domain risk and the conditions under which they escalate.

07

Digital Twin projections

Which parts of the one governed twin carry mission meaning — never a second twin.

08

Evidence mappings

Obligation, implemented control, and the evidence that control produces under inspection.

09

Incident workflows

Domain response paths for events that require containment, notification and retained evidence.

10

Briefings and reports

The executive reporting each domain's accountability structure actually requires.

Why it matters operationally

A pack that cannot contain code cannot introduce behaviour into a national deployment.

The registry validates this structurally: a pack containing an executable value anywhere in its structure is refused before it loads. The same rule produces a second benefit. Because there is no code to leave behind, a sovereign pack travels on signed media without loss — the copy installed in a disconnected facility renders exactly what the connected copy renders.

Architecture

What does not change.

The value of a sovereign pack depends on everything around it staying exactly where it was. These are the properties that hold whether an organisation installs none of these packs or all of them.

01

One kernel

A sovereign pack adds policies inside the kernel's existing vocabulary. It adds no domain, no condition type and no evaluation path.

02

One Digital Twin

Sovereign views project the same governed twin every executive workspace reads. There is no separate sovereign model.

03

No executable code

A sovereign pack is data. The registry refuses to load one containing an executable value anywhere in its structure.

04

Deny-only extension

A pack may add constraints. It cannot weaken a baseline, grant permission, or create capability.

05

Assessed installation

A pack declares the deployment guarantees it requires. A deployment that does not provide them is refused, with the missing guarantee named.

06

Reversible

Removing a pack rolls back its policies and returns the organisation to its prior governed baseline.

07

Honest measurement

A readiness measure with no connected source is reported as not instrumented, never as an estimated figure.

08

No product fork

Sovereign domains are additional packs on the same platform. There is no sovereign edition and no separate codebase.

Assessed delivery

Reviewed before installation. Verified at the console. Reversible afterwards.

A sovereign pack does not arrive as configuration. Where the runtime is immutable — every sovereign and air-gapped deployment — it arrives on signed media whose signature is verified before any change is made, and there is no network path that can write to governed configuration.

  1. 01

    Assess

    The mission, obligations and operating environment are assessed, and the required classification tier established.

  2. 02

    Select

    The sovereign domains in scope are selected. Deployment profile and domain scope are decided separately.

  3. 03

    Review

    Authority chains, workflows, capabilities and policies are reviewed by the responsible domain authority — as data, not code.

  4. 04

    Deploy

    Guardian OS is deployed on the profile that satisfies the classification's guarantees.

  5. 05

    Install

    Packs are installed from signed media at the console. The signature is verified before anything changes.

  6. 06

    Activate

    Each contributed policy passes through validation and activation in the same Runtime Governance kernel.

  7. 07

    Operate

    Mission workflows, readiness, recommendations and incidents run continuously against the governed twin.

  8. 08

    Evidence

    Signed evidence packs are produced locally for oversight, accreditation and inquiry.

AdmitAssess classification → verify signature → installOperateObserve → recommend → authorise → execute → evidenceRemoveRoll back contributed policies → restore prior baseline
What changes for the organisation

Sovereign obligations, without a sovereign fork.

Operating concernWith a separate sovereign productWith Sovereign Intelligence Packs
Platform strategyProcure a separate sovereign productInstall sovereign domains onto the platform already in use
Governance engineMaintain a forked kernel per environmentOperate one kernel across every deployment profile
Domain expertiseRebuild authority and workflow models per programmeStart from a reviewed, versioned domain structure
AssuranceAssert that controls are appropriateDemonstrate which control refused which action, and under whose authority
Supply chainAccept software updates over a networkInstall signed media at the console, verified before anything changes
ReviewRequire code review to assess a domain modelReview the pack as data, by the domain authority responsible for it

Keep one governance engine

The same kernel, the same improvements and the same security work apply to every deployment, sovereign included.

Give authorities something reviewable

Authority chains, workflows and constraints are declarative, so the accountable person can review them directly.

Prove control, not intent

Evidence shows which action was refused, under which control, and which authority was missing.

Operate disconnected without losing capability

Signed media carries the full pack. A disconnected estate is not a degraded one.

One enterprise operating platform

Where a sovereign pack sits.

01

AI Twin

Supplies the organisation's current systems, relationships, authorities, risks and evidence.

02

Sovereign Intelligence Pack

Interprets that context through the mission, its authority model and its statutory obligations.

03

Runtime Governance

Enforces the pack's approved deny-only policies before an autonomous action executes.

04

Guardian OS

Coordinates installation, recommendations, incidents, approvals and continuous monitoring.

05

Executive Workspaces

Present mission intelligence to the authorities accountable for the decisions.

Explore Guardian OS →Industry Intelligence Packs →Explore the AI Twin →
One kernel. One twin. One platform. Many sovereign domains.

Bring mission intelligence into a governed sovereign deployment.

Start with the sovereign domains in scope for your mandate, then validate them against your authority model, your systems and the deployment profile your obligations require.

Discuss a sovereign deploymentExplore Guardian OS