The arithmetic that used to govern this is gone.
A guided anti-tank missile is an expensive, export-controlled object built by a handful of companies. An FPV quadcopter is a hobby aircraft, a commodity flight controller, an analogue video link and an explosive charge fastened on with tape. Reporting from the current war puts those in the low hundreds of pounds each, against targets costing a thousand times more. Both Karabakh in 2020 and Ukraine since have been read as drone wars, and the larger systems got the headlines, but the cheap end is where the cost inversion happened.
The interesting question for this notebook is which component was ever the hard one.
The parts, and which of them was difficult¶
Airframe: commodity. Motors and batteries: commodity, driven by a consumer market that has nothing to do with weapons. Radio: commodity. Explosive: the oldest technology in the stack and not the constraint.
The hard part was always the terminal guidance. Getting an object onto a moving target in the last few seconds is the thing that justified the price of a guided weapon, and it required either a trained operator holding a lock or a seeker head with real engineering in it.
That is the part that has moved. Visual tracking of an object across frames at useful frame rates now runs on an inference accelerator costing tens of pounds, with models and training pipelines that are public because they were built for inspecting crops and watching car parks. A terminal guidance problem has become a computer vision exercise with an off-the-shelf answer.
This is the pattern this notebook keeps finding in other domains: the clever part migrates out of bespoke hardware and into software, and the hardware underneath becomes a commodity. It happened to networking. It happened to sequencing. It has happened here, and nobody involved intended the dual-use consequence.
What it costs¶
The attrition logic that follows is brutal and, from a purely engineering standpoint, correct. If the weapon is cheap enough you do not need reliability, you need volume, and a thirty per cent success rate at three hundred pounds a unit beats a ninety per cent rate at three hundred thousand. Every quality argument our trade makes about building things properly runs backwards in this one domain, which is worth sitting with.
The deeper cost is that the barrier to entry has fallen through the floor. Precision strike used to be an attribute of states with a defence industrial base. It is now within reach of any organised group with a budget, a soldering iron and an internet connection. There is no export control that addresses this, because the controlled item is a quadcopter you can buy in a shop and a model you can download.
What this makes possible, which is not all bad¶
The honest version of this argument has to include what the same technology does when it is not carrying a warhead, because it is the identical stack.
The autonomy that flies a strike drone flies a search and rescue aircraft over a mountainside at night, finds a casualty by thermal signature and does it without risking a crew. The same airframes map flood damage, inspect infrastructure nobody can safely climb and deliver blood products across a country with no roads. Those are running deployments, not projections, and they exist because the components got cheap for military reasons.
There is also a defensive argument worth making plainly. A cheap precision weapon is an asymmetric one, and asymmetry favours whoever is defending territory against a larger force. A country that cannot afford an air force can now impose real cost on an armoured column. Whether that is good depends entirely on who is invading whom, which is the problem with saying anything general about dual-use technology.
Where the loop closes¶
The part that matters, and the reason this is an engineering question rather than a policy one.
Today most of these systems have a person in the loop, holding a view through goggles and steering until impact. The human is there partly for ethics and largely because the link usually works. Both reasons are eroding. Electronic warfare is making the link unreliable, and the engineering response to an unreliable link is to push more decision-making onto the aircraft. Terminal autonomy, where the operator designates and the machine finishes the job after the link drops, is the obvious next step and is a software change to systems already flying.
Nobody can currently check the claim. "Human in the loop" is an assurance about a system's behaviour, and there is no mechanism by which an outside party can verify it. You cannot tell from the outside whether a given airframe had a person authorising the final second or a model doing it. You cannot tell afterwards from the wreckage. The distinction on which the legality of these systems is being argued is, at present, an unverifiable claim made by the operator.
This lab has spent a lot of words on attestation and reproducible builds: on proving what code is running on a machine. That work has an obvious and uncomfortable application here. An attested autonomy stack, where a system can prove which model and which policy it was running at a given moment, is technically feasible with mechanisms that exist. Nobody is building it, because no operator wants their weapons to produce evidence.
Who ends up owning it¶
The models are open, the airframes are commodity, and the supply chain for small drones runs substantially through one country, which has already demonstrated that it will restrict exports when it suits. A military capability resting on consumer parts from a strategic competitor is a strange position, and it explains the scramble to build domestic drone manufacturing everywhere at once.
The second chokepoint is the inference silicon, which is a much shorter list of suppliers than the airframes, and already subject to export control for unrelated reasons. Autonomy capability tracks access to accelerators, and access to accelerators is decided by export policy written for a different purpose.
The ugly part is the civilian side. The counter-drone systems now being installed around airports, stadiums and borders are a detection and identification infrastructure pointed at the sky, and they do not distinguish between a weapon and a camera. The capability to find, classify and down a small aircraft in a city is being built for sound reasons and will be available for other ones.
Here at AxisOps our position is that this is the clearest case we know of where a defensive capability and an offensive one are the same artefact, and that the right engineering response is verification rather than refusal. If autonomy in weapons cannot be prevented, and we do not think it can, then the thing worth building is the apparatus that makes claims about it checkable. That is infrastructure work of the kind this lab does, and nobody is funding it.
Where this breaks¶
Whether attested autonomy would ever be adopted without a treaty requiring it, and whether any such treaty is reachable while the capability is this cheap and this widely distributed. The technical problem looks tractable. The political one does not.