Michael Darius Eastwood · Independent AI alignment researcher
Published
Under the US Export Administration Regulations, an export happens not only when a physical item crosses a border, but also when controlled technology or software is released to a foreign person, wherever they are located. This is the "deemed export" rule. It was written for a world of blueprints, source code disks, and visiting engineers, and it has quietly survived intact into the cloud era. Its core question is now: when a user in Amsterdam queries a US-hosted large language model, and the model releases inference outputs to them, has an export occurred?
Three arguments say "yes, and it is controlled." The model weights are technology within the definition. The inference API is a release. The model has capabilities on the current Commerce Control List's dual-use registers. Therefore each foreign-person query is a deemed export and requires a licence (general or specific).
Three arguments say "no, or not quite." The weights are not released, only the outputs. The outputs are text, not technology. The commercial impact of treating every query as a licensable export would collapse the API economy overnight. Therefore the deemed-export rule must be read narrowly around cloud inference.
The June 2026 directive did not resolve the doctrinal question. It side-stepped it. The order was directed at the provider, not at users; the provider was told to withdraw the service from a specified set of jurisdictions inside twenty-four hours. In effect BIS treated the API as the export instrument and the withdrawal as a licence condition. This is administratively clean, because it does not require classifying each query, and legally slippery, because it treats a cloud service the way an earlier decade would have treated a shipment of physical goods.
The blog's contribution is to name the doctrinal ambiguity clearly. It argues, in effect, that a directive-based approach can work in the short term but cannot scale: at some point BIS or the courts must either extend the deemed-export doctrine to cover cloud inference at query granularity, or accept that provider-level directives are the operative instrument and legislate around them. Either move has second-order consequences the current framework does not address.
First, provider-level directives create a very strong incentive for providers to route inference through jurisdictions that will not honour the directives. That undermines the deemed-export logic before it has been argued.
Second, if inference itself is the controlled export, small open-weights models running on rented Chinese GPUs become the arbitrage path. Provider-level directives cannot reach that path. Substrate-level attestation (see FlexHEG, arXiv:2506.15093) can, at some cost.
Third, the deemed-export doctrine was drafted for a world where technology transfers were events. AI cloud services make transfer a continuous condition. Every framework that assumes events must be re-derived for a continuous world.
The Fable 5 shutdown is register row 10, classified CONVERGENT with the January 2026 book that named "The Chokepoint" and argued that infrastructure-as-leverage would become an explicit policy instrument. The Harvard Law Review blog piece is one of several public artefacts making the transition from doctrine to reality legible.
From the book Infinite Architects: Intelligence, Recursion, and the Creation of Everything by Michael Darius Eastwood.