In October 2022 the United States restricted exports of advanced computing hardware to China using thresholds expressed in processing performance and interconnect bandwidth. In October 2023 those rules were revised: interconnect bandwidth was dropped as a criterion and a performance density threshold added, explicitly because vendors had designed parts that sat just underneath the original line.
Read that sequence as an engineer rather than as a lawyer. A regulator published a performance specification. Industry designed to the spec, as industry always does. The regulator observed the result and amended the spec. That is a standards process, conducted between a government and a market, with the specification being a list of things you are not allowed to build.
Why this is an architecture problem now¶
Because a number in a control list propagates into every layer above it.
The part you can buy determines the memory bandwidth you have, which determines the model size that is practical, which determines whether a workload runs locally or must go to a provider in another jurisdiction, which determines where your data lives and which law applies to it. A threshold in a regulation reaches all the way up to a data protection question, and it does so without anyone in the middle making a decision.
It also fragments the hardware landscape in a way this trade has not had to plan for. Designing for one global compute market was the assumption underneath a decade of infrastructure work. The reasonable planning assumption now is at least two, diverging, with different parts available, different performance ceilings and different software ecosystems growing on each.
The practical consequences are mundane and annoying. Capacity planning becomes jurisdictional. A multi-region deployment may not have the same silicon in every region. "Buy the next generation" stops being a reliable answer to a performance problem, because the next generation may not be sold to you.
What it costs¶
Optionality, which was the quiet asset nobody was pricing.
Infrastructure built on the assumption that you can buy a faster part next year has a dependency on a political relationship, and that dependency is now explicit. The cost shows up as inventory, second sources and designs that deliberately leave performance on the table in exchange for using parts that are available everywhere. That is real money spent on resilience against a policy change rather than a technical one.
There is also a straightforward efficiency loss. Parts designed to sit under a threshold are worse than the parts that would otherwise have been built. Engineering effort goes into gaming a line instead of into making things faster. Nobody involved thinks this is a good use of anybody's time.
What it makes possible¶
Not everything downstream of this is bad, and the second-order effects are more interesting than the restrictions.
The clearest is that constraint has restarted architectural competition. When you cannot buy the fastest part, efficiency per unit becomes the thing worth optimising, and the work that follows is the sort this notebook has always found more interesting than brute scaling. Smaller models, better quantisation, sparsity and getting more out of memory bandwidth are all areas where the constraint is doing something that abundance was not.
The second is that it has made open instruction sets a strategic question rather than an enthusiast one. An ISA that nobody can revoke is worth a great deal more in 2025 than it was in 2020, and the investment flowing into RISC-V is substantially a response to exactly this. A control list is a powerful argument for an architecture whose specification cannot be withdrawn, even though implementations, tooling and the chips themselves remain controllable. And the licensing landscape for conventional ISAs looks different once licensing is understood as a point of leverage.
The third, and the one we would bet on, is a durable shift towards local inference. If access to frontier compute is politically contingent, then running what you can on hardware you own stops being a preference and becomes a continuity requirement. That suits smaller operators better than it suits large ones, and it pushes the whole field towards models that fit on affordable hardware. We think that is a good direction for reasons that have nothing to do with geopolitics.
Who ends up owning it¶
The uncomfortable structure is that very few actors have leverage here, and none of them is you.
Fabrication at the leading edge is effectively one company in one country, with the lithography equipment coming from effectively one company in another. That is the narrowest chokepoint in modern industry and it exists for technical reasons rather than commercial ones. Everything in the compute supply chain passes through it.
Export control turns that technical chokepoint into a policy instrument. The list is written by one government, revised unilaterally and has extraterritorial reach through the equipment and the design tools. A European or British company's architecture is being constrained by a process it has no vote in, and the current list is not the last one.
For a small operator the position is worse than it looks, because they will not be the ones who get allocations when a part is scarce. Restriction plus scarcity concentrates frontier capability in whoever is largest. So export control intended to preserve a strategic advantage also has the domestic effect of advantaging incumbents. That is not what it was for, and it is what it does.
Here at AxisOps our position follows from everything else in this notebook: build so the substrate can be swapped. Keep the build working on more than one architecture, prefer the model that runs on hardware you can actually buy and treat a dependency on a single part number as the risk it now provably is. We have argued for that on technical grounds for years. It turns out the strongest case for it is political.
What would change our mind¶
If the thresholds stabilise and the market re-converges, most of this becomes an expensive few years rather than a structural change, and the second-source work looks like wasted effort. The 2023 revision suggests otherwise, since the direction of travel there was tightening rather than settling, but a specification written by a government can be rewritten by the next one.