/dɪˈpɛn.dən.si ɪnˈvɜː.ʃən/From Latin dependere ("to hang from, to be dependent on") + inversio
("a turning upside down"). The term deliberately echoes the software engineering principle of "dependency
inversion" (which inverts the direction of code dependencies) while repurposing it to name a condition in
which the claimed direction of control is inverted — the user believes they control the system, but the
system's dependencies control the user.
Definition
The condition in which a self-hosted application's sovereignty claim is undermined by dependencies on
third-party infrastructure at layers beneath the application. The user controls the application layer — they
installed the software, they manage the instance, they hold the credentials. The user does not control the cloud
server the application runs on, the DNS service that resolves its address, the certificate authority that
validates its identity, or the operating system that executes its code. Each uncontrolled layer is a point at
which a third party's decisions can override the user's intentions.
Self-Hosting as Partial Sovereignty
Self-hosting is not inherently theatrical. It is a genuine step toward sovereignty at the application layer,
and that step has real value — it removes one layer of dependency and gives the steward direct control over
configuration, data access, and update timing. The theatrical element enters when self-hosting is marketed or
understood as full sovereignty, when the partial control at the application layer is mistaken for comprehensive
control across the stack. The Material Stack analysis reveals the gap: a self-hosted Nextcloud instance on a
DigitalOcean droplet is sovereign at the application layer and dependent at the architectural, network, and
geological layers. The sovereignty is real but bounded, and the boundary must be documented.
The Tenancy Metaphor
Self-hosting on rented infrastructure is tenancy with extra steps. The tenant decorates their apartment,
chooses their furniture, controls their locks. The tenant does not own the building, does not set the lease
terms, and cannot prevent the landlord from selling the property, raising the rent, or complying with a court
order to grant access. The analogy is precise at the Material Stack level: the self-hosted application is the
apartment, the cloud provider is the landlord, and the terms of service are the lease. Dependency Inversion
names the condition in which the tenant believes they own the building because they installed their own locks.
Excavation Note: Dependency Inversion was identified as the second of four Sovereignty Theater
mechanisms in "Sovereignty Theater" (2025). The term deliberately echoes the software engineering "dependency
inversion principle" (Robert C. Martin, 1996), repurposing the concept from code architecture to infrastructure
analysis. In software engineering, dependency inversion is a design virtue. In infrastructure analysis, it is a
diagnostic condition.