POLICY // AI INFRASTRUCTURE ECONOMICS

Clearance wars

The phase of AI competition where frontier capability ships not when it is built but when it is permitted — government clearance granted customer by customer.

The clearance wars are the phase of AI competition in which frontier capability ships not when it is built, but when it is permitted. The term describes a structural shift in what is scarce: once capability is abundant and multiple labs can produce comparable models, access — not intelligence — becomes the contested resource.

The inflection point was GPT-5.6, the first frontier model gated per-customer by US government clearance: capability rolled out tier by tier, customer by customer, with the government rather than the vendor deciding the order. The gate, not the model, became the story. Once that template exists, it generalizes — export controls on coding agents, per-jurisdiction deployment approvals, trust reviews of what runs inside your development environment.

For operators the consequence is a new axis of competitive planning: your AI roadmap is no longer only a function of what exists, but of what you are cleared to use, where, and when. Clearance status becomes an asset with market value — and the vocabulary of AI strategy acquires a word it did not need when capability itself was the frontier.

Frequently asked questions

What are the clearance wars?

The phase of AI competition where frontier capability arrives not when it is built but when the government permits it — clearance granted customer by customer. GPT-5.6, the first frontier model shipped through per-customer US clearance, marked the shift.

Why does clearance matter more than capability?

Because once several labs can build comparable models, capability stops being scarce — permission becomes the bottleneck. Who is allowed to use a capability, in which jurisdiction and on what schedule, decides more than who built it.

Source analyses

READ THE FULL ARGUMENT
The Model Wars Are Over. The Clearance Wars Begin.
READ THE FULL ARGUMENT
Coding Agent Bans Are the New Export Controls

Related terms

GLOSSARY
Joule Wars
GLOSSARY
The liability stack
GLOSSARY
Social permission to burn tokens
Michał Piszczek
Michał Piszczek
CEO / CTO / FOUNDER

Term defined and maintained by Michał Piszczek — CTO of Archdesk, author of the Joule Wars and Proof-Adjusted Autonomy frameworks. Quote freely with attribution to piszczek.pl/glossary (CC BY 4.0).