This is AI Frontiers, today. Software sovereignty and who holds the veto over your stack. Owning something is not the same as controlling it. Sovereignty is graded control over the choke points of the stack. The question is not whether you own every component, it is whether someone else can deny access, change the terms, inspect sensitive data, restrict deployment, or capture the value you create above a dependency. A country can fund a domestic model and still depend on foreign chips, foreign cloud capacity, proprietary orchestration, external support, and contracts that make exit impractical. There are five places another actor can stop you. Silicon, Cloud, Orchestration, The Model, The Contract. Start with Silicon. United States export controls began on the 7th of October 2022. They expanded on the 17th of October 2023. A rule published on the 13th of January 2025 introduced worldwide licensing constraints for advanced chips and model weights, with compliance set for the 15th of May, 2025. The rule was withdrawn before that date. That withdrawal makes the point rather than weakening it. Access to this layer changes by administrative decision. Europe's answer is measurement, not flags. The European Commission's cloud sovereignty framework assesses sovereignty across 48 criteria in eight categories, including openness, transparency, and independence in the technological stack, rather than treating data location as the whole question. The Cloud and AI Development Act sets four assurance levels. Level two requires providers to demonstrate independence from third countries and transparency over their software supply chain. European sovereignty is a purchasing discipline, not a nationality test. Demand for control is rising. The analyst firm IDC reported in 2026 that 63% of organizations were more likely to adopt sovereign cloud services because of geopolitical events. It projects that by 2028, 60% of multinational firms will split AI stacks across sovereign zones, with integration costs tripling. But duplication only pays when it removes a real dependency. Copy a commodity service and you transfer money from your own margin to another infrastructure layer. So run the practical test, identify the dependency that can stop deployment or extract the highest rent, then measure how easily you can substitute it, and apply the contractual rule. If a supplier cannot explain how you will leave, its sovereignty claim describes dependence, not control. That's AI Frontiers.