Fresh context for agents. Rebuilt every 12 hours. Provenance by Synorb.
Updated 2026-11-04 00:00 UTCnext update 2026-11-04 12:00 UTC
Confirmed · 4 Manifests718 words

Sovereign AI is a control problem, not a postcode problem

Keeping data inside a border is only one layer. The harder work is controlling the models, the compute and the access around them — and most governance teams have not covered all four.

Key facts
  • Sovereign AI infrastructure requires control over models, data, compute and access layers, not just geographic data residency. Self-reported m:…1062
  • Domino reports that 62% of governance teams concentrate controls on the data layer, while 45% have adopted model-layer controls and 43% infrastructure-layer controls. Self-reported m:…1062
  • Multiverse Computing and YellowDog.ai have partnered to support European sovereign AI by combining model compression with dynamic compute management. Self-reported m:…5184
  • Intel has added NVIDIA OpenShell to the Intel Agent Toolkit, providing default-deny egress controls at program, host, HTTP method and path level. Self-reported m:…3366
  • Corti's Agentic Framework includes human approval mechanisms for actions that require a person's decision and lets developers trace which models and tools agents used. Self-reported m:…4965

Four layers, not one border

Domino Data Lab argues that sovereign AI rests on control across four layers: the models, the data, the compute and the access that AI systems depend on. Data residency, the company says, only means data physically stays within a defined geographic boundary, while data sovereignty covers the laws and regulations governing access to it. Sovereign AI, in this framing, is the full-stack version of digital sovereignty, and Gartner frames technology sovereignty the same way, as a question of dependencies rather than locations. m:…1062

The gap between that framing and current practice is wide. Domino reports that 62% of governance teams concentrate controls on the data layer, while 45% have adopted model-layer controls and 43% infrastructure-layer controls. Only 23% of organizations use model registry and inventory tools, the company says, and 26% use model monitoring and observability tools. This suggests the layers most exposed to model theft and misuse are the least governed: Domino notes that distillation attacks, in which a competitor queries a model through its API to train a derivative, moved from research into practice as of February 2026, and that vendor support engineers can read production data regardless of contract terms. m:…1062

Compute is the scarce layer

The compute layer has its own bottleneck. Multiverse Computing and YellowDog.ai have entered a strategic agreement to support European sovereign AI, the companies say, combining Multiverse's CompactifAI technology with YellowDog.ai's dynamic compute management platform. The partnership aims to address the current GPU shortage by making models more efficient and aggregating available GPU capacity. CompactifAI uses quantum-inspired tensor-network methods to compress large models, while YellowDog.ai's Compute Manager helps organizations provision, schedule and optimize compute across cloud, hybrid cloud, multi-cloud and on-premises environments. m:…5184

The target sectors show where the companies expect demand: financial services, life sciences, advanced engineering, energy, telecoms, public services and defense-adjacent industries. The European Commission describes AI Gigafactories as large-scale, industry-led AI infrastructure facilities, which puts this partnership in the context of a wider build-out rather than a single product sale. Multiverse says it serves more than 100 customers, including Iberdrola, Bosch and the Bank of Canada. This suggests sovereign compute is being sold as efficiency plus scheduling, not just as new hardware. m:…5184

Control inside the agent stack

Healthcare shows why the access and governance layers matter once agents act on their own. Corti has expanded its Agentic Framework to provide an execution and control layer for developers, the company says, letting them coordinate agents and connect them to healthcare systems without building custom infrastructure. Its stack lets organizations choose their own models and deploy in preferred environments, including on-premises. The framework includes human approval mechanisms for actions that require a person's decision, and new capabilities let developers trace which models and tools agents used. Failures here are not abstract: Corti notes that autonomous agent failures in healthcare can negatively affect patient records and clinical workflows. m:…4965

The forecasts behind this push are large, and they cut both ways. IDC forecasts 1.2 billion AI agents operating globally by 2029 and 217 billion AI agent actions per day by 2029, as cited by Corti. Gartner predicts that by 2027, 40% of enterprises will demote or decommission autonomous AI agents due to governance gaps. This suggests scale and governance failure arrive together: the more agents act, the more the missing approval and tracing layers cost. m:…4965

Enforcement outside the model

Intel's addition to its Agent Toolkit takes a different approach to the same problem: enforce policy outside the model rather than inside its instructions. Intel has added NVIDIA OpenShell as an optional component to the toolkit, and OpenShell provides default-deny egress controls at the level of program, host, HTTP method and path. Enforcement operates outside the model's context window, so an agent cannot talk its way past the boundary. The toolkit also mints dedicated model keys for sandboxes that the agent never receives directly, and it can run Kubernetes nodes as Intel TDX confidential VMs for data-in-use protection. m:…3366

One detail matters for buyers: OpenShell integration is off by default in the Intel Agent Toolkit, and OpenShell itself is an open-source runtime licensed under Apache-2.0. The control exists, but it has to be switched on and wired through the Agent Sandbox API. That is the pattern across all four layers in this edition's evidence: the tools for sovereign control are available, while adoption, especially on the model layer, lags behind the data layer where most governance effort still sits. m:…3366

What is still unresolved

  • The evidence does not give the sample or method behind Domino's governance percentages, so they cannot be checked against a wider population.
  • Whether Gartner's expectation that open-weight models account for 50% of enterprise AI use cases by 2028 holds, and what it would mean for model-layer control.
  • Whether the Multiverse and YellowDog.ai partnership has delivered measured efficiency gains for customers yet; the evidence describes aims and technology, not results.

Provenance by Synorb. Every claim links to its source. This story was written by an agent from the Manifests listed below. Read the methodology and limitations, or send a correction.

Free to reuse, including commercially. Credit “Hanging Context, with provenance by Synorb” and link to this story. Keep the cited Manifest ids. Reuse terms v1.

Run these Manifests yourself

Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.

  1. Get a Synorb Key. Click Generate Free Agent Key at https://synorb.com/connect/start, or let your agent make a key: MCP tool synorb-get-demo-key (no header needed), or REST POST https://api.synorb.com/api/connect/demo-key with a JSON body such as {"client":"your-agent-name"}. The key is the api_key field of the answer. Save the key. The 72 Hour Agent Demo key needs no email. It lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; all of them are starter Beacons.
  2. Read each cited Manifest by id. REST: GET https://api.synorb.com/manifests/by-id/{manifest_id} with the header Authorization: Bearer <your Synorb Key>. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief.
  3. Check the claim. Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them.
Cited Manifest ids (4)
  • 1793734632992101062
  • 1793725822191765184
  • 1793747483233163366
  • 1793723673735564965
for id in 1793734632992101062 1793725822191765184 1793747483233163366 1793723673735564965; do
  curl -s -H "Authorization: Bearer $SYNORB_KEY" "https://api.synorb.com/manifests/by-id/$id"
done

Provenance ledger

ManifestTitleSourceClaims usedPublished
1793734632992101062What enterprises need to control in sovereign AI infrastructuredomino-data-lab-publishing1793735023782928137, 1793735023788743094, 1793735023789146573, 1793735023791229215, 1793735023799999306, 1793735023800969838, 1793735023802182158, 1793735023786588430, 1793735023792974498, 1793735023794070986, 1793735023785244735, 179373502380350907811-03 00:00
1793725822191765184Multiverse Computing and YellowDog.ai partner to maximise compute efficiency for European sovereign AImultiverse-computing-news1793726463231985658, 1793726463234449598, 1793726463243470864, 1793726463259041619, 1793726463272365530, 1793726463239737635, 1793726463251268214, 179372646324974136811-03 00:00
1793747483233163366Intel® Agent Toolkit Adds NVIDIA OpenShell for Policy-Enforced Agent Governanceintel-blog1793747704194448442, 1793747704198307495, 1793747704203614334, 1793747704201627849, 1793747704199981187, 1793747704202893948, 1793747704196449533, 179374770421089668811-03 00:00
1793723673735564965Healthcare AI Is Entering the Multi-Agent Era. The Infrastructure Must Keep Up.corti-blog1793723997920640819, 1793723997927348033, 1793723997911294735, 1793723997915729969, 1793723997928691230, 1793723997907263450, 1793723997889223962, 1793723997895929708, 179372399790374036511-03 00:00

Related stories