A frontier model launched in the period was pulled offline days later, under export controls and over concerns about its vulnerability-discovery capability. It returned on July 1, after government approval.
The episode is the most direct example of what pre-release review means in practice. An announced product, with customers starting to integrate, goes offline on a decision that is neither technical nor commercial.
For anyone building on someone else's model, that's the kind of risk rarely entering planning. Technical unavailability is covered by a fallback chain; regulatory interruption hits the entire supplier at once.
The operational lesson is the same as in any critical dependency: the fallback has to be a different supplier rather than another version of the same one, and it has to have been tested before it was needed.
The case also explains the sector's insistence, in the same period, on discussing release standards with government. Calendar predictability became a commercial asset.
