Review Layered Sovereignty

The degree of independent control an organization or country possesses at each layer of a technology stack.

Control can differ across chips, energy, networks, cloud infrastructure, models, data, applications, and operations. Owning one layer does not create independence at every other layer.

A single claim of technological sovereignty can hide critical dependencies. Layer-by-layer analysis shows where control, substitution, and negotiation are actually possible.

An organization hosts an application locally but depends on a foreign cloud control plane, external model weights, and vendor-managed updates.

Layered sovereignty is not the same as complete self-sufficiency. It describes degrees of control and dependency at each layer.

Sovereignty is a stack, not a switch.

* [[system|System]] * [[capability-provenance|Capability Provenance]] * [[vendor-supported-demand|Vendor-Supported Demand]] * [[assumed-isolation|Assumed Isolation]]

* [European Commission Joint Research Centre, *Open but Not Powerless: Towards a Common Understanding of EU Digital Sovereignty*](https://publications.jrc.ec.europa.eu/repository/bitstream/JRC144908/JRC144908_01.pdf) — treats digital sovereignty as a multi-layered concept and examines dependencies across digital capabilities. * [European Commission, *Communication on European Tech Sovereignty*](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52026DC0503) — addresses autonomy and dependency across chips, infrastructure, software, cloud, AI, and the wider technology stack. These sources support the mechanism behind the Renaissance Solutions term; they do not establish its exact glossary definition.

* Map dependencies using [[system|System]] and [[capability-provenance|Capability Provenance]].