/ˌəʊ.pən sɔːs əʊˈpæs.ɪ.ti/From English open source (software whose source code is publicly available,
coined in 1998 by Christine Peterson) + Latin opacitas ("shadiness, darkness"), from opacus
("shaded, dark"). The oxymoronic compound is deliberate: openness at one layer of the stack coexists with
opacity at every layer beneath it, and the openness is used to conceal the opacity.
Definition
The condition in which open-source code running on closed infrastructure produces auditable dependency rather
than sovereignty. The user can read the code, verify its behavior, and confirm that the software does what it
claims. The user cannot verify what the infrastructure beneath it does — what data the hosting provider logs,
what agencies have access, what retention policies govern its operation, what happens when the provider changes
terms. Open-source software is a necessary but insufficient condition for sovereignty. Without open
infrastructure, open code produces transparent captivity.
The Transparency Trap
Open-source advocacy has long argued, correctly, that code transparency is a prerequisite for trust. If you
cannot read the code, you cannot verify what it does. The inverse does not follow: if you can read the code, you
can trust the system. The system is not the code. The system is the code running on hardware, in a facility, on
a network, under a jurisdiction, governed by terms, maintained by operators whose decisions are not disclosed in
the source repository. Open-source code provides transparency at the format and application layers of the
Material Stack. It provides no transparency at the geological, architectural, network, or platform layers. The
stack beneath the code remains opaque, and the opacity is where the sovereignty claim fails.
Auditable Dependency
The condition that Open-Source Opacity produces is not ignorance but informed dependency — the user knows
exactly what the software does and has no knowledge of what the infrastructure does. This is a more
sophisticated form of Sovereignty Theater than closed-source dependency, because it satisfies the user's demand
for transparency while leaving the material conditions of sovereignty unaddressed. The user feels sovereign
because they can read the code. They are not sovereign because they cannot read the stack. The feeling and the
reality diverge, and the divergence is the theater.
Excavation Note: Open-Source Opacity was identified as the fourth of four Sovereignty Theater
mechanisms in "Sovereignty Theater" (2025). The oxymoronic structure of the term — open paired with opaque — is a
deliberate signal that the condition it names is internally contradictory: genuine openness at one layer
coexisting with genuine opacity at every other layer, with the openness serving to legitimize the opacity.