The Merger Nobody Voted For: Inside the Push to Fuse the U.S. and Israeli Militaries
There’s a provision sitting inside the 2027 National Defense Authorization Act — the annual bill that funds and governs the entire U.S. military — that most Americans have never heard of. It doesn’t have a catchy name. It didn’t get a press conference. It was introduced quietly, tucked into a 1,000-plus-page bill, and it would do something the United States has never done with any country on earth, including our closest NATO allies: permanently wire our defense industrial base together with a foreign nation’s.
That provision is Section 224 (renumbered Section 219 in the House and Section 1217 in the Senate), officially titled the “United States-Israel Defense Technology Cooperation Initiative.” And whether you support Israel, oppose Israel, or don’t think about Israel most days, this is worth twenty minutes of your attention, because it’s not really about Israel. It’s about whether the United States still gets to decide, on its own, who builds our weapons, who touches our military data, and who has a seat inside the Pentagon’s decision-making process going forward.
What Section 224 Actually Does
Let’s start with the facts, because there’s a lot of noise on both sides of this one.
Section 224 was introduced on May 26, 2026, as part of the House Armed Services Committee’s draft of the FY2027 NDAA. It requires the Secretary of Defense to designate a senior “executive agent” whose job is to synchronize and expand cooperation between the U.S. and Israeli militaries across a specific list of technology domains: counter-drone and counter-unmanned systems, anti-tunneling and subterranean threat detection, missile and air defense, artificial intelligence, quantum computing, autonomous systems, directed energy weapons, advanced sensing, cyber defense and electronic warfare, and biotechnology and biomanufacturing.
It also calls for joint ventures, licensing agreements, co-production manufacturing partnerships, joint training exercises, and — this is the part that’s raised the most eyebrows on both the left and the right — “network integration” and “data fusion.” Those two terms are not clearly defined anywhere in the bill’s text, which means nobody outside the rooms where this was written knows exactly how far “integration” is meant to go.
The section didn’t come out of nowhere. It’s built from an earlier bill, the United States-Israel FUTURES Act, introduced by Senators Ted Budd and Kirsten Gillibrand and Representatives Ronny Jackson and Don Davis. That bill stalled as standalone legislation, so its core language got folded into the must-pass defense bill instead — a move critics on both sides describe as burying a controversial policy inside a bill that Congress essentially has to pass every year to keep the military funded.
The bill’s authors, House Armed Services Chairman Mike Rogers (R-AL) and the committee’s top Democrat, Adam Smith (D-WA), gave it bipartisan cover from leadership. When Representative Ro Khanna (D-CA) introduced an amendment in committee to strip Section 224 out entirely, it was voted down — and it was voted down by members of both parties, with only Khanna and Representative Sara Jacobs (D-CA) supporting the amendment. Representative Thomas Massie (R-KY), one of the few consistent voices against foreign military entanglements regardless of the country involved, has pledged to force a floor vote to strip it out when the bill reaches the House floor.
For context on how big a shift this is: the U.S. has provided Israel with more than $200 billion in inflation-adjusted military assistance since 1948, more than any other country on earth. But that relationship has always operated inside the traditional aid framework — Congress votes on the money, the money buys American weapons, and Israel is the customer. Section 224 would build something structurally different: a standing bureaucratic architecture that ties U.S. and Israeli research, production, and — per the “network integration” and “data fusion” language — potentially battlefield data systems together on an ongoing basis, outside the normal up-or-down vote on foreign aid.
Why Now
This didn’t happen in a vacuum. Israeli Prime Minister Benjamin Netanyahu has said publicly, as far back as January 2026, that he wants to move Israel away from dependence on American military assistance within the next decade. On June 1, 2026, Netanyahu sent a letter to Representative Marlin Stutzman (R-IN) thanking him for endorsing what Netanyahu called “my plan” — a “new framework of joint defense cooperation, codevelopment, coproduction and mutual investment” spanning missile defense, AI, unmanned systems, cybersecurity, and next-generation military platforms. Stutzman followed up with a nonbinding resolution calling for a new memorandum of understanding that would eventually end direct U.S. aid to Israel and replace it with Israel funding its own weapons purchases — while deepening the technology-sharing relationship instead.
Put plainly: the pitch from Israel’s government is “stop giving us checks, and instead let us build the future of your military with you.” Supporters frame this as fiscally responsible — Israel becomes a “partner” instead of an “aid recipient,” and American taxpayers spend less writing direct checks. Critics argue it’s the opposite of a good deal, because it trades a relationship Congress can vote to end each year for one baked permanently into the defense-industrial base, immune to future political shifts.
The current U.S.-Israel memorandum of understanding, negotiated under the Obama administration in 2016, provides roughly $3.8 billion a year and expires in 2028. Israel wants the next arrangement locked in before that clock runs out — and before a possible change in the makeup of Congress after the November 2026 midterms makes a deal like this harder to pass.
The Bipartisan Backlash
What’s genuinely unusual about this fight is who’s on which side. This isn’t a clean left-right split.
On the right, Marjorie Taylor Greene posted bluntly: “If Israel is a sovereign state then it doesn’t need to be merged with America’s military in section 224 of the NDAA, nor does it need a single penny of American tax dollars to fight its wars.” She tied her opposition directly to a separate, alarming development: the Pentagon’s Defense Intelligence Agency reportedly raised its counterintelligence threat assessment of Israel to its highest level in recent weeks, citing more aggressive-than-usual Israeli espionage activity against the United States, according to reporting from NBC News and The New York Times. Greene’s response: “The Pentagon raised threat of Israeli spying on the U.S. to the highest level and AIPAC is openly cheering Republicans for section 224 in the NDAA that merges our military with Israel’s military. Our government is being captured.”
Massie has taken a similar stance, and it’s cost him politically — he lost his primary this year after AIPAC-aligned groups spent millions against him, a fact he and Greene have both pointed to directly.
On the left, Senator Bernie Sanders has urged supporters to “defeat Section 224,” calling it a provision that “quietly expands U.S. military cooperation and weapons development with almost zero oversight” and warning it would give Israel “more military integration than any NATO ally.” Khanna has argued the measure amounts to a blank check for a relationship most Americans, per current polling, no longer want expanded. Senator Chris Van Hollen wrote in the New York Times that his own party has provided “reflexive and unconditional support to Israeli governments, even as their actions have increasingly undermined American interests and values.”
Outside groups spanning very different politics have also lined up against it: the Council on American-Islamic Relations, the Quincy Institute for Responsible Statecraft, the Arab Center Washington DC, and A New Policy, a PAC focused on reshaping U.S. Israel-Palestine policy, have all published opposition research or action alerts. The Quincy Institute’s Ben Freeman put it directly: “Netanyahu is proving right now that Israel’s interests are not always America’s interests. Trump is trying to negotiate an end to this conflict, and Netanyahu — over and over again — is doing things that violate the ceasefires and make ending the conflict impossible.”
Even the specific national security concern isn’t hypothetical. Writing in The American Conservative, Harrison Berger pointed to a chilling precedent for why “foreign components in U.S. systems inherently raises the risk of compromised integrity” — citing the 2024 attack in Lebanon in which Israeli intelligence turned thousands of pagers into remote-detonated bombs by compromising a supply chain before the devices ever reached their targets. That operation is widely regarded as a masterstroke of tradecraft. It’s also a live demonstration of exactly what a state actor can do when it gets deep enough into a supply chain — which is precisely what critics say Section 224 would hand Israel inside U.S. defense manufacturing.
Where the Public Stands
Here’s the part elected officials on both sides seem to be ignoring: the public isn’t asking for this.
A May 2026 Institute for Global Affairs poll found only 16% of Americans want the U.S. to keep supplying Israel with weapons without new restrictions. Thirty-eight percent want weapons transfers stopped entirely, and another 24% want them conditioned on how they’re used. Even among Republicans — historically the more pro-Israel of the two parties — only 35% back unrestricted weapons supply, while 47% want either conditions or a full halt. Gallup reported in February 2026 that, for the first time in years, Israelis no longer lead Palestinians in American sympathy, with independent voters now favoring Palestinians.
So the vote count in the House Armed Services Committee — bipartisan leadership pushing this through, a bipartisan handful trying to strip it out and losing — doesn’t reflect where the country actually is. That gap between what Washington is doing and what Americans want is, frankly, the whole story of this show. It’s the reason this newsletter and this channel exist.
Where the Bill Stands Now
As of this writing, Section 224 has cleared the House Armed Services Committee markup after Khanna’s amendment to strike it was voted down on June 4, 2026. It still needs to pass the full House, get reconciled with the Senate’s version (Section 1217, which — notably — uses looser, less restrictive language than the House version), and be signed by the president before it becomes law. Massie has said he’ll force a floor vote to try to strip it out when the full NDAA comes up. That fight hasn’t happened yet.
This is not settled law. It is an active fight, and it is one almost nobody outside of Beltway defense reporters and a handful of X accounts is currently watching.
Opinion: This Is What Losing Sovereignty Looks Like
Everything above this line is reporting. What follows is my opinion, and I want to be upfront that it is exactly that.
I think Israel is committing genocide in Gaza. That is not a fringe position I’m inventing for shock value — South Africa brought exactly that accusation against Israel to the International Court of Justice, the case is ongoing, and a growing number of governments, international legal scholars, and human rights organizations have reached the same conclusion based on the death toll, the destruction of civilian infrastructure, and statements made by Israeli officials themselves. Reasonable people disagree about where the legal line for “genocide” sits, and I’ll lay out that disagreement fairly below. But my own read, watching this unfold in real time for going on two years now, is that what’s happening in Gaza crosses that line.
And that’s exactly why Section 224 bothers me so much. This isn’t a moment where the United States should be looking for ways to tie its own weapons programs more tightly to the Israeli government. It’s a moment where a growing number of Americans — Republicans and Democrats both, according to the polling above — are saying “slow down, and maybe stop.” Congress’s answer to that public mood is to try to lock the relationship in so deep that no future Congress, no future president, and no future public opinion shift can easily undo it. That’s not representative government. That’s the opposite of it.
Here’s the sovereignty argument, and I want to make it as plainly as I can: a country is not fully sovereign if a foreign government has standing, structural, unchecked access to the design and data systems of its military. That’s not a controversial definition. It’s the whole reason “network integration” and “data fusion” are the two phrases in this bill that have people across the political spectrum the most alarmed — because nobody, including the bill’s own authors as far as anyone can tell, has defined where that access starts and where it stops.
And I want to be really clear about something, because I know exactly how this gets read otherwise: this isn’t an Israel problem. It’s a sovereignty problem. If Congress tried to quietly write “network integration” and “data fusion” provisions tying our military’s future AI and autonomous weapons systems to Canada, I’d be raising the same alarm. If it were Mexico, same thing. If it were the UK, France, Japan — doesn’t matter. The country’s name isn’t the issue. The structure is the issue. Any time a foreign government — friendly, hostile, allied, neutral, doesn’t matter — gets a standing seat inside the technology that will decide how American forces target, defend, and fight, that is a sovereignty problem, full stop. I don’t care whose flag is on it.
What makes the Israel case sharper right now isn’t some special animosity toward Israel. It’s that we have a live, concrete, undisputed example — the 2024 pager operation — of exactly what happens when a state actor gets deep access into a supply chain it doesn’t fully control. That operation killed and maimed people through a compromised device pipeline, and it was executed by the same government this bill wants to hand deeper access to American defense production. You don’t have to believe Israel would ever turn that capability against the United States to recognize that the capability itself — deep supply chain and data access — is the kind of thing a sovereign nation should be extremely careful about handing to anyone, ally or not.
There’s also the timing, which I think tells you almost everything you need to know about how this bill is being handled. It’s being pushed through during what proponents themselves describe as a “window” — Republican control of Congress, a lame-duck pro-Israel president, before the 2026 midterms potentially flip a chamber and make this harder to pass. That’s not language I’m putting in their mouths. That’s the plain read from the reporting: this is being rushed through specifically because the people pushing it know public support for unconditional backing of Israel is collapsing, and they want it locked into federal law before that erosion shows up at the ballot box in a way that stops them. When the argument for a policy is “we need to pass this now, before the public gets more say,” that should set off alarms regardless of the topic.
I also want to flag the DIA counterintelligence assessment, because it lands at almost the exact same moment as this vote and it’s being treated as a footnote instead of the headline it should be. Our own Pentagon reportedly raised its threat assessment of Israeli espionage against the United States to the highest level, right as Congress debates giving that same government’s defense sector deeper structural access to American military technology. I don’t know how you read those two facts side by side and conclude this is a routine defense cooperation update. Marjorie Taylor Greene, whatever you think of her on other issues, said the plain thing out loud: this looks like capture, not cooperation.
So when people say “America is occupied” — and I know that phrase gets thrown around loosely, sometimes by people who mean it as pure rhetoric — I think what they’re actually pointing at, underneath the hyperbole, is something real: the sense that American sovereignty is being quietly traded away, piece by piece, by people in Washington who face no real accountability for the trade, in favor of a foreign government’s stated interests over the American public’s stated interests. You don’t need “occupation” in the literal military sense to have a legitimate grievance here. You need exactly what we have: a foreign head of state writing a congressman a thank-you letter for helping engineer a “framework” that reshapes U.S. defense policy, while the American public — on both sides of the aisle — is saying, clearly and repeatedly in poll after poll, that they want the opposite.
I’ll say the fair version of the other side, because that’s what this show is supposed to do. Supporters of Section 224 aren’t wrong that Israel has real, demonstrated technological strengths — particularly in missile defense, drone countermeasures, and cyber capability — that genuinely could benefit American systems. Iron Dome technology, for instance, already has a track record of real-world combat testing that most American systems simply haven’t had. There’s also a legitimate fiscal argument: if this framework actually reduces direct cash aid over time and shifts Israel toward funding its own procurement, that is, in isolation, less money leaving U.S. taxpayers’ pockets. And backers argue that formalizing an “executive agent” role doesn’t create new authority so much as organize cooperation that’s already happening informally — Chairman Rogers has said exactly that, that the section “doesn’t create any new programs within the Department of Defense,” it just designates someone to coordinate what already exists.
I don’t find that reassuring, and here’s why: informal, ad hoc cooperation that Congress can end with a single appropriations vote is categorically different from a standing bureaucratic structure written into permanent law with vague terms like “network integration” and “data fusion” that nobody has bothered to define. If it’s really just coordinating what already exists, there’s no reason it needs to be shielded from the normal appropriations process the way critics say it is. The fact that its authors are pushing to lock it in now, ahead of a possible political shift, tells you they know that if this had to survive a real up-or-down debate later, in front of a public that’s turned skeptical, it might not.
What I Think Happens Next
Massie says he’ll force a floor vote to strip Section 224 out. Given how the committee vote went — bipartisan leadership holding the line, a small bipartisan minority pushing back and losing — I wouldn’t bet heavily on that amendment succeeding on the floor either, though the midterms next year could scramble the math for whatever the next version of this fight looks like.
What I’d ask you to do, regardless of where you land on Israel itself, is separate the two questions that are getting collapsed into one in this debate. Question one: what should U.S. policy toward Israel be? People disagree on that, genuinely and in good faith, and I’m not going to pretend that disagreement doesn’t exist. Question two: should any foreign government — Israel, Canada, Mexico, anyone — get standing, structural, poorly-defined access to the systems that build and run the American military? I think the honest answer to question two is no, categorically, regardless of how you answer question one. And right now, Congress is letting question one’s political pressure quietly answer question two for us, without ever actually having that debate in the open.
That’s the story nobody’s telling you. Now you know.