DECODING: Co-production, the new grammar of Western aid to Ukraine

Introduction: a word that changed the tone of an entire summit

Why "license" became the word of the Ankara summit

One word dominated the coverage coming out of the NATO summit held in Ankara on July 7 and 8, 2026: license. Donald Trump announced that Ukraine would receive a license to manufacture its own Patriot interceptors, a phrase that traveled through Western newsrooms within hours and was widely read as a breakthrough. I want to spend this piece decoding what that word actually means, legally and industrially, because the gap between the announcement and its real content matters enormously.

A license is not a factory. It is not even, by itself, a guarantee that manufacturing will happen at all. It is a legal permission, a starting point in a process that involves intellectual property, manufacturer consent, supply chains and years of technical transfer. Understanding that distinction is the entire purpose of this decoding.

What this piece will and will not claim

I will not tell you the Patriot license is meaningless. I will not tell you it is a solved problem either. What I want to do is walk through, step by step, what a license realistically requires before it becomes production, using the reporting and expert commentary available since the Ankara Declaration was published on July 8.

This matters beyond one weapons system. The pattern we see with the Patriot announcement, co-production replacing simple donation, is becoming the default grammar of Western aid to Ukraine, and understanding how it actually works will help readers evaluate every future announcement of this kind.

I think we owe readers more than repeating a triumphant quote from a podium. A license is a legal document, not a factory, and confusing the two does a disservice to everyone trying to understand what Ukraine actually gained in Ankara.

What a manufacturing license technically requires

Intellectual property, consent, and the manufacturers who were not in the room

A defense manufacturing license typically requires the consent, or at minimum the active cooperation, of the original manufacturer, in this case Lockheed Martin and RTX, which jointly produce the Patriot system. According to reporting from CBS News and Defense News, these companies had not been informed of the license at the time Donald Trump announced it in Ankara. That detail alone tells you the announcement preceded, rather than followed, the technical groundwork a license normally requires.

Licensing sensitive interceptor technology to a third country, even a close partner, typically involves government-to-government agreements, export control clearances, and negotiated terms covering everything from royalties to quality control standards. None of that appears to have been finalized in Ankara. What was announced was a political intention, not a completed legal instrument.

Why this distinction is not just legal pedantry

Some will say this distinction is a technicality that does not change the underlying direction of travel. I disagree, because the timeline consequences are massive. A completed license with manufacturer buy-in could move toward production within a defined schedule. A political announcement awaiting manufacturer engagement could stall for months while the actual legal and technical groundwork gets built after the fact.

Ukraine needs interceptors on a timeline measured in months, not years. The distance between a podium announcement and a signed licensing agreement is exactly the kind of gap that determines whether this promise helps Kyiv in time to matter, or arrives too late to change the trajectory of the war's next phase.

Announcing a license before informing the manufacturer is not a minor procedural oversight. It tells you the sequence was backwards, and sequence matters enormously when the promised outcome is measured in interceptors that stop missiles aimed at civilians.

The two technical bottlenecks nobody can wave away

Guidance systems, the hardest part to transfer

According to Marc DeVore, who chairs two advisory groups for the British Ministry of Defence, the two central obstacles to Ukrainian Patriot production are the interceptor's guidance systems and its engines. Guidance systems, in particular, represent some of the most closely guarded technology in the entire Western defense industrial base, precisely because their precision is what makes the Patriot system effective in the first place.

Transferring this technology is not comparable to transferring a manufacturing blueprint for a less sensitive component. It requires trust, verification mechanisms, and a willingness from Washington to accept some risk that the technology could eventually be studied, copied, or, in a worst case, compromised. That risk calculation takes time to resolve, regardless of political urgency.

Engines, the other constraint experts keep repeating

The second bottleneck, interceptor engines, involves a different but equally real constraint: specialized manufacturing expertise concentrated in a small number of facilities, mostly in the United States. Building a parallel production capability in Ukraine would require either transferring that expertise directly or establishing a new supply chain almost from scratch, both of which take years rather than months.

Fabian Hoffmann, a researcher who has written extensively on missile technology, has pointed to supply chain localization, ensuring components are actually produced close to where assembly happens, as the real bottleneck behind most co-production promises, more than any single missing piece of paperwork. This is echoed by Marc DeVore's own timeline estimate, which places realistic production no earlier than 2027, possibly 2028.

Every time I read an expert name specific technical bottlenecks like guidance systems and engines, I trust the timeline they offer more than any political promise. Engineers do not get to round up when they estimate how long a supply chain takes to build.

The German precedent, a co-production deal that already exists

Drones made in Germany, delivered to Ukraine, no ambiguity

While the Patriot license remains a political intention awaiting technical completion, a genuinely completed co-production agreement was signed in Ankara between Germany and Ukraine: deep-strike drones, manufactured on German soil, delivered directly to Kyiv. This agreement gives us a concrete, already-operational example of what co-production actually looks like when it moves past the announcement stage.

The contrast between the two cases is instructive. The German-Ukrainian drone deal involves less sensitive, more modular technology than a Patriot interceptor, which partly explains why it could move to signature faster. But it also shows that when manufacturers are engaged from the start, rather than informed after a presidential announcement, co-production can actually happen on a workable timeline.

What separates a real agreement from a symbolic one

The defining feature of the German agreement is sequence: negotiation, manufacturer engagement, and signature, in that order, before any public announcement. The Patriot license inverted that sequence, announcement first, technical groundwork to follow. That inversion is precisely why one agreement is operational today and the other remains, for now, a promise awaiting its legal architecture.

This is not a minor stylistic difference between two governments. It is the difference between an agreement Ukraine can actually build on this year, and one it will have to keep waiting for through 2027 or 2028.

Germany quietly did the hard diplomatic work before making an announcement, while the Patriot license reversed that order for maximum headline effect. I know which approach I trust more to actually deliver hardware to Ukrainian soldiers.

Why Washington benefits politically from this model, regardless of timeline

A promise that deflects criticism without depleting American stocks

Richard Shirreff, former Deputy Supreme Allied Commander Europe, offers a blunt read of the political incentive behind the Patriot license: "The Americans can check a box and say the problem is solved. They may be willing to take a victory lap without having actually fixed the problem." This is not a claim about bad faith so much as an observation about incentives: an announcement costs nothing today, while an actual interceptor shipment costs a scarce and valuable stockpile item today.

Marc DeVore makes a similar point about the license letting Washington off the hook for criticism about insufficient support, without requiring the United States to draw down its own limited interceptor reserves, reserves already strained by the recent war between Washington, Israel and Iran.

Why this incentive structure matters for how we read future announcements

Understanding this incentive does not require assuming Donald Trump or his administration acted in bad faith. It simply means recognizing that a co-production announcement is, structurally, a lower-cost gesture than an immediate transfer of finished interceptors from American stockpiles. Both Kyiv and outside observers should factor that structural reality into how much weight they give any single announcement.

This is precisely why decoding the actual content of these announcements matters more than repeating their headline framing. The incentive to announce something impressive exists independently of whether that something can be delivered on the timeline implied by the announcement itself.

I don't think Washington acted in bad faith here, but I do think the incentive to announce something dramatic without immediate cost is real, and pretending otherwise would be its own kind of dishonesty toward readers trying to understand this war.

The time factor: why eighteen months is the optimistic scenario

What "eighteen months to three years" actually contains

Experts cited across multiple outlets converge on a production timeline somewhere between eighteen months and three years for a genuinely operational Ukrainian Patriot line, assuming the licensing and technical transfer proceed without major setbacks. Marc DeVore's own estimate, placing realistic production no earlier than late 2027, sits toward the more optimistic end of that range.

Each stage in that timeline, licensing finalization, facility construction or conversion, supply chain establishment, workforce training, testing and certification, carries its own risk of delay. Assuming all of them proceed smoothly is itself an optimistic assumption, one that history in defense manufacturing rarely rewards without exception.

What this means for the war Ukraine is fighting today

The practical consequence is stark: whatever this license eventually produces will not help Ukraine survive the interceptor shortage it faces this year or next. It may shape the war's later phases, or the post-war reconstruction of Ukrainian defense industry, but it does not answer the question of what stops the missiles fired next month.

That distinction should reframe how we evaluate the Ankara announcement. It is a long-term industrial decision dressed, in its initial presentation, as an urgent wartime solution. Both framings can be true simultaneously, but conflating them misleads anyone trying to understand what actually changed for Ukraine this month.

Eighteen months to three years is not a footnote, it is the headline fact hiding behind the headline announcement. I want readers to walk away from this piece knowing that number better than they know the applause line from Ankara.

The Neptune option and the opportunity cost nobody mentioned

Converting an existing missile line, a tempting shortcut

One option discussed by defense analysts involves converting parts of Ukraine's existing Neptune missile production line, currently used for anti-ship and deep-strike weapons, toward interceptor-adjacent manufacturing. This would theoretically shorten the timeline by leveraging infrastructure and expertise that already exist on Ukrainian soil, rather than building entirely new capacity from scratch.

The appeal is obvious: existing engineers, existing facilities, existing supply relationships, all of it faster to repurpose than to build new. But repurposing is never free, and the cost here is not measured only in money.

What Ukraine would give up to gain interceptor capacity this way

Every production line diverted toward interceptor-adjacent work is a production line no longer building the deep-strike weapons that have allowed Ukraine to hit Russian refineries and military infrastructure far behind the front. That is a real opportunity cost, not a hypothetical one, and it is rarely mentioned in coverage that treats co-production announcements as unambiguously positive news.

Ukraine's own military planners will have to weigh that trade-off carefully, and I have not seen public reporting indicating they have already made that choice. It remains, for now, one option among several, not a confirmed path forward.

Nobody at the podium in Ankara mentioned that fixing the interceptor shortage this way might mean fewer deep-strike missiles hitting refineries in Russia. Trade-offs like that deserve to be named, not buried under applause.

Europe's parallel push to reduce dependency on a single supplier

Why European allies are not simply waiting on Washington

Independently of the Patriot license timeline, several European allies have accelerated their own efforts to reduce dependency on American-supplied interceptors, partly through investment in domestic systems like the French-Italian SAMP/T, and partly through exploratory co-production discussions of their own, including the German-Ukrainian drone model already in motion. The Ankara Declaration explicitly encourages this kind of diversification across the Alliance's collective industrial base.

This push is not a rejection of American leadership on air defense, where the Patriot system remains the most proven option in the field today. It is a recognition that concentrating critical capability in a single supply chain, however trusted, creates a strategic vulnerability that a war of this duration has made impossible to ignore.

What genuine diversification would require from European industry

Building real alternative capacity requires the same ingredients as the Ukrainian Patriot license: guidance system expertise, engine manufacturing capability, and years of sustained investment rather than a single summit announcement. Europe possesses more of this underlying industrial base than Ukraine currently does, which is precisely why European co-production discussions may, in some cases, move faster than the American-Ukrainian license.

Whether that promise translates into delivered hardware on a meaningful timeline remains, as with every claim in this piece, a question that only actual contracts and factory openings can answer, not further declarations of intent.

I would rather see Europe quietly build its own interceptor capacity than keep depending entirely on a single American supply chain, and I don't think wanting that makes anyone less committed to the transatlantic alliance.

Turkey's industrial role, beyond hosting the summit

A drone manufacturing reputation that predates this war

Turkey's role in this story extends beyond simply hosting the summit in Ankara. The country has built, over the past decade, a genuine reputation in drone manufacturing, most visibly through the Bayraktar systems that have already seen combat use in multiple conflicts, including in Ukraine itself in the war's earlier phases.

This existing industrial base positions Turkey as a potential co-production partner for future agreements, not merely a diplomatic host. Recep Tayyip Erdogan's simultaneous negotiation over F-35 reintegration adds another layer: a country trying to leverage its industrial relevance to the Ukrainian war effort into broader reacceptance within Western defense structures.

Why Netanyahu's objection complicates this picture

Israeli Prime Minister Benjamin Netanyahu's public objection to Turkish F-35 reintegration, declaring Turkey "not a friendly state to the United States," illustrates how co-production and industrial diplomacy do not happen in a vacuum. Regional rivalries and competing security interests among Western partners themselves can slow or complicate agreements that might otherwise proceed on pure industrial logic.

This is a reminder that the grammar of co-production is not purely technical. It is embedded in a broader diplomatic context where allies do not always agree with each other, even as they collectively try to support Ukraine against Russia.

Watching Netanyahu and Erdogan spar over F-35 jets while Ukraine waits for interceptors is a reminder that Western unity is real but never simple, and pretending otherwise would flatten a genuinely complicated picture.

Ukraine as knowledge exporter, not just recipient

What Kyiv brings to the table that the West does not have

One dimension of co-production rarely discussed in Western coverage: Ukraine is not merely a recipient of technology in these agreements. Ukrainian engineers have developed, under combat conditions no Western military has faced at this intensity, expertise in drone warfare, electronic countermeasures, and rapid battlefield adaptation that Western manufacturers themselves have started studying.

The German-Ukrainian drone agreement, in this light, is not a one-way technology transfer. It is closer to a genuine exchange, German manufacturing capacity combined with Ukrainian combat-tested design knowledge, each side contributing something the other lacks.

Why this framing matters for how future agreements get negotiated

Recognizing Ukraine's contribution as genuine expertise, not just battlefield desperation, changes the negotiating posture for future co-production deals. It positions Kyiv less as a supplicant waiting for Western generosity and more as a technical partner whose knowledge has independent value, a framing that could accelerate future agreements if Western negotiators fully internalize it.

I think this reframing deserves more attention than it currently receives, because it changes not just the tone but potentially the terms of every future co-production discussion involving Ukraine.

Ukraine walks into these negotiations with real expertise earned under fire, not empty hands, and I think Western negotiators sometimes underestimate how much that shifts the actual balance of the conversation.

The risks European allies may be underestimating

Hosting costs and the fragmentation risk

Co-production agreements are not free for the European or Ukrainian side hosting the manufacturing. Facility construction, security requirements for sensitive technology, and workforce training all carry real costs that tend to receive less attention than the political announcement itself. Ukrainian facilities, in particular, face an additional risk category entirely absent from a German or Polish context: the possibility of direct Russian strikes on manufacturing sites, which would need to be factored into any realistic assessment of where production actually gets located.

There is also a coordination risk: as more allies pursue separate co-production agreements with Ukraine, differing standards, certifications, and technical specifications could fragment what should ideally be a coherent, interoperable production ecosystem. Without active coordination, likely falling to NATO itself under Mark Rutte's leadership, this fragmentation risk could slow the very acceleration co-production is meant to deliver.

Why these risks argue for coordination, not retreat

None of these risks argue against co-production as a model. They argue for building coordination mechanisms now, before a dozen separate bilateral agreements create a patchwork that is harder to manage than the shortage it was meant to solve. The Ankara Declaration's language about expanding collective industrial capacity gestures toward this need, without yet specifying exactly how that coordination will work in practice.

I raise these risks not to argue against the direction the West has chosen, but because naming them honestly is the only way to actually manage them before they become a genuine obstacle rather than a manageable one.

I support the shift toward co-production, and I still think we need to name its risks honestly rather than treating every new bilateral agreement as an unambiguous win with no downside worth discussing.

South Korea, the quiet precedent nobody is loudly citing

Indirect supply through Poland, without the fanfare

South Korea has, for months, supplied munitions and equipment to Ukraine's war effort indirectly, primarily through arrangements routed via Poland, without the kind of presidential podium announcement that accompanied the Patriot license. This quieter model offers an instructive contrast: steady, functional supply relationships that do not require dramatic unveiling to actually deliver results.

South Korea's own defense industry, built over decades of investment driven by its own security situation facing North Korea, gives it manufacturing depth that could, in theory, be leveraged further for Ukraine's benefit, if diplomatic and logistical coordination between Washington, Brussels and Seoul improves.

Why quiet precedents deserve as much attention as loud ones

I think the South Korean model deserves more attention in coverage of Western support for Ukraine, precisely because it demonstrates that effective co-production and supply relationships do not require the theatrical framing that accompanied the Patriot announcement in Ankara. Quiet, well-coordinated logistics can move as much material, sometimes more reliably, than headline-grabbing declarations.

If Western coordination with Seoul improves, this indirect model could scale into something considerably more significant than its current, largely unremarked, contribution to Ukraine's war effort.

South Korea has been quietly helping Ukraine for months without needing a podium moment, and I think that quiet reliability deserves at least as much respect as the announcement everyone is still talking about.

What NATO's own declaration signals about next steps

Rutte's mandate to report back on implementation

The Ankara Declaration tasks NATO Secretary General Mark Rutte with reporting on implementation progress at the Alliance's next summit, a structural mechanism that at least creates a checkpoint for accountability on commitments made in Ankara, including the co-production push. Whether that reporting mechanism produces genuine pressure to deliver, or simply another round of diplomatic language, will depend on how seriously member states treat the review.

This kind of built-in accountability checkpoint is not nothing. It gives journalists, analysts and Ukrainian officials themselves a specific moment to measure what actually got built against what got promised in Ankara, rather than letting the announcement fade from public attention entirely.

What I will be watching for at that next checkpoint

I will be watching, at that future reporting moment, for concrete markers: has the Patriot licensing agreement actually been finalized with Lockheed Martin and RTX engagement, has the German-Ukrainian drone model been replicated by other allies, and has any measurable interceptor production capacity actually come online in Ukraine or among its partners. Those markers, not further rhetoric, will tell the real story.

Until that checkpoint arrives, the honest assessment remains what this piece has argued throughout: a meaningful doctrinal shift toward co-production is underway, but its concrete output for Ukraine's immediate air defense needs remains, for now, a promise rather than a delivered capability.

I will hold NATO to the accountability checkpoint it built into its own declaration, because a promise with no built-in review mechanism is just a headline, and Ukraine deserves better than a headline.

What allies still disagree about behind the scenes

Certification standards nobody has fully aligned yet

Even among allies broadly supportive of co-production, disagreements persist over certification standards for jointly manufactured components, an unglamorous but critical detail that determines whether an interceptor built partly in one country and finished in another can actually be certified as combat-ready under NATO-wide standards. These disagreements rarely reach public communiqués, but they shape how fast co-production agreements can actually move from signature to delivery.

Resolving these standards typically requires technical working groups, cross-border inspections, and legal harmonization that takes months even under the best circumstances. None of that work disappears simply because a political leader announces a license from a podium in Ankara.

Why this technical friction deserves more attention than it gets

I think this kind of behind-the-scenes friction deserves more coverage than it typically receives, because it is exactly the sort of detail that explains why co-production announcements so often take longer to materialize than their initial framing suggests. The gap is not usually bad faith. It is unglamorous technical and legal work that nobody puts on a summit stage.

Until these certification questions are resolved for the Patriot license specifically, any production timeline remains, by definition, provisional rather than firm, regardless of how confidently it gets described in public statements.

Certification standards will never make a headline, and that is exactly why I wanted to name them here. The unglamorous paperwork is often the real obstacle standing between a promise and a delivered interceptor.

Conclusion: a grammar still under construction

What we can say with confidence about co-production today

Co-production is becoming the dominant grammar of Western aid to Ukraine, replacing simple donation with shared manufacturing arrangements that, in theory, build lasting capacity rather than one-off transfers dependent on a single ally's stockpile decisions. The German-Ukrainian drone agreement shows this grammar can work when manufacturers are engaged from the start. The Patriot license shows what happens when the announcement outruns the technical groundwork.

Both examples belong to the same emerging pattern, and understanding the difference between them is the clearest way to evaluate whether any future co-production announcement deserves celebration or skepticism, or, more likely, some careful combination of both.

The sentence I want readers to remember from this decoding

A license is a legal starting point, not a finished capability. Whether it becomes real production depends on manufacturer engagement, technical transfer, and years of patient industrial work that no summit communiqué can compress into a single announcement, however dramatic that announcement sounds from a podium in Ankara.

That is the grammar the West is still learning to speak fluently. Ukraine, in the meantime, keeps living with the consequences of every gap between the announcement and the delivery.

I will keep decoding each new announcement the same way I decoded this one: not to dismiss it, but to measure it honestly against what it actually requires before it becomes real. Ukraine deserves that precision more than it deserves another headline.

Signed Maxime Marquette, columnist

Columnist's transparency note

What I know and what I don't know

I know that the Ankara Declaration was published by NATO on July 8, 2026, that Donald Trump announced a Patriot manufacturing license for Ukraine during that summit, and that according to reporting from Defense News and CBS News, Lockheed Martin and RTX had not been formally informed of the announcement at the time it was made. I know that Marc DeVore estimates realistic production could not begin before late 2027 or 2028, based on his stated assessment of the guidance system and engine bottlenecks.

I do not know the exact current status of licensing negotiations as this piece is written, nor do I have independent access to classified assessments of interceptor stockpile levels among NATO members. Where I cite expert estimates rather than official figures, I have identified them as such throughout this piece.

Method

This decoding draws on the official Ankara Declaration published by NATO, Reuters reporting on Zelensky's confirmation of a political-level agreement, and the detailed critical analysis published by Euromaidan Press on July 10, 2026, which first compiled the expert reservations from Marc DeVore and Richard Shirreff cited throughout this piece. Additional detail on the announcement's reception came from Defense News, Janes and DW.

My editorial position is stated openly: I support expanded Western industrial capacity to help Ukraine defend itself against Russian aggression, and I believe readers are better served by a precise account of what a licensing announcement actually requires than by treating podium rhetoric as equivalent to delivered hardware.

Sources

Primary sources

Critical analysis of the Patriot license announced in Ankara — Euromaidan Press, July 10, 2026

Official Ankara summit declaration — NATO, July 8, 2026

Zelensky confirms political-level agreement on Patriot license — Reuters, July 9, 2026

Secondary sources

Details on the Patriot license promised to Ukraine — Defense News, July 8, 2026

Details on multi-year financing for aid to Ukraine — Janes, July 9, 2026

Trump signals support for Patriot production in Ukraine — DW