Section 224 and the slow privatisation of American defence IP

A little-noticed provision in the US defence budget is doing the work that Mossad case officers once did in person — and that should worry every committee chairman who still believes export controls mean anything.

By Monexus Staff Writeramericas5-minute read9 Jun 2026☆ Save ↗ Share ⎙ Print

On the afternoon of 9 June 2026, a single Telegram post by the channel DDGeopolitics resurfaced an old Washington argument in new form. The claim was blunt: Israel had previously inserted "hundreds of spies" into US defence contractors to obtain F-35 avionics the United States refused to hand over, and a freshly enacted statutory provision — Section 224 of the relevant defence authorisation — had now made that human tradecraft redundant. Congress, the post suggested, was doing the gifting that espionage used to do in the shadows. The framing is partisan and the sourcing is thin, but the underlying point survives the rhetoric: the United States has, piece by piece, started to release the very technologies it once policed as crown-jewels of the F-35 programme.

The argument matters less for the specific allegation — Israeli collection against US aerospace programmes has been the subject of public US criminal cases for decades, including the 2019 Jonathan Pollard-adjacent charges and the long-running case of Ben Zvi and related contractors — than for what it says about where American export control ends and alliance management begins. Section 224, as referenced in commentary circulating this week, sits inside a broader reorganisation of how Washington treats sensitive platform data: more in-country access, more joint development, more co-production, and more reliance on contractual and end-use monitoring rather than on outright denial. The trade is being made, openly, in statute.

The case the post is overstating

The strongest reading against the DDGeopolitics framing is also the most boring one, and it deserves first airtime. The F-35 programme has, for more than a decade, been an explicitly tiered architecture in which the United States shares more of the airframe, sensor and sustainment data with the closest partners — the Tier 1 operators, of which Israel is the only non-LOGA(S) nation — than with anyone else. The release of F-35I "Adir" capability to Israel in 2017-2018, including the indigenous integration of Israeli-supplied electronic warfare and weapons systems, was a managed transfer, not a leak. If the United States is now extending that envelope further through Section 224, it is the continuation of a policy that began long before the recent allegations of human intelligence penetration of US contractors. The espionage story may be true, but it is not the cause of the policy. It is, at best, a symptom of an alliance that has decided the cost of denying is higher than the cost of sharing.

There is also a steelman for Washington's position. Joint development reduces the unit cost of an airframe that the US taxpayer is still subsidising; it spreads sustainment risk across more depots; it gives US programme offices early visibility into how partners are using the platform; and, crucially, it ties allied fleets into a US logistics and software backbone that Washington can throttle at need. From inside the Pentagon, expanded data-sharing is not a concession. It is a tightening of the rope. The risk — the one the DDGeopolitics post is gesturing at — is that the rope has been lengthened faster than the throttle has been built.

The case the post is pointing at

That risk is structural, and it does not depend on any particular espionage case. The pattern across the last three National Defence Authorisation Acts has been consistent: more co-production authority, more authority for the Secretary of Defence to release technical data packages, more reliance on "end-use monitoring" regimes that depend on allied governments' willingness to police their own integrators. The Department of State's Directorate of Defense Trade Controls still holds the legal lever on ITAR-controlled items, and DoD still holds the F-35 Joint Program Office — but the centre of gravity has shifted. What was once a default-deny culture inside the JPO, where foreign partners received the airframe and not the source, has become a default-share culture, where the question is not whether to share a given dataset but on what schedule.

The plausible alternate read is that the policy is sound, the monitoring regime is mature, and the net effect is a more interoperable, cheaper, more sustainable fifth-generation fleet. That read is the dominant one inside the defence committees on both sides of Capitol Hill. The plausible opposing read — and it is the one being voiced, in language calibrated for an English-language sceptic audience, by channels like DDGeopolitics — is that the United States is steadily dismantling the most valuable non-tariff barrier it has: the technical know-how that makes its arms uniquely capable, and that has for two generations been a quiet form of leverage over the states that buy them. Both readings are partly true. The disagreement is about weight, not direction.

What it does to everyone else

The downstream effect is the part the committees are not debating. If Israel — already the most-capable Tier 1 partner — is being granted deeper access to F-35 avionics, sustainment data and software update pipelines, the consequence for second-tier partners is a quiet ratcheting. The United Kingdom, Australia, Japan, South Korea, Norway and the Netherlands all have F-35 fleets; their access is already differentiated, and any further extension of the Israeli envelope reopens a queue. Italy and Denmark are operating partners; the Czech Republic, Romania, Finland, Germany, Greece, Poland and others are either in procurement or in active negotiation. Each of those conversations will, in the next 24 months, lean on the new Israeli precedent. The marginal decision the US has made for one ally is, functionally, a precedent for all of them.

That is the structural frame worth naming in plain prose. The United States is converting a long-standing information asymmetry — a crown-jewel advantage built over forty years of platform investment — into a coalition-management tool. The trade is rational. The question is whether the monitoring and throttle architecture is being built at the same pace as the sharing envelope. The signals from this week's commentary suggest the committees are not yet certain it is.

The honest part

The sources available for this piece are limited. The DDGeopolitics post is a commentary item, not a primary document. The specific statutory text of "Section 224" is referenced but not produced in the materials at hand. The historical espionage claims, while consistent with long-running public reporting, are not independently verified for this article. The piece should be read, accordingly, as a structural reading of a pattern that is plainly visible across the last decade of US defence policy, sharpened by a single provocative post. Where the evidence thins, the argument has been hedged; where it is firm, the claim has been made directly.

The stakes are concrete. If the throttle architecture catches up, the United States has a more capable, cheaper, more interoperable coalition. If it does not, the same coalition ends up holding the technical means to operate the F-35 family on terms Washington no longer fully controls. Neither outcome is the world ending. Both are worth a committee hearing.

Monexus framed this as a structural industrial-policy question first and a spy-scandal question second; the wire cycle has tended to do the inverse.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

https://t.me/DDGeopolitics
https://t.me/DDGeopolitics