Merged at the Trigger: Section 224, the NDAA, and the Quiet End of American Military Sovereignty

Buried in the House Armed Services Committee's chairman's mark for the 2027 National Defense Authorization Act — released Tuesday, May 26, without a press conference, without a presidential address, and without a single word of public debate — is a provision that represents the most significant restructuring of American military sovereignty in the post-World War II era. Section 224, titled the "United States-Israel Defense Technology Cooperation Initiative," would, in the words of the Quincy Institute's Ben Freeman, provide "a higher level of military-industrial integration than the US has with any other country in the world." That includes the United Kingdom. That includes Canada. That includes every NATO ally the United States has fought alongside for 80 years. No alliance partner in American history has been offered what Section 224 proposes to give Israel — and it was buried in a defense bill without telling you it was there.

What Section 224 Actually Says

The statutory text of Section 224, as published in H.R. 8800, requires the Secretary of Defense to designate an executive agent specifically responsible for synchronizing cooperative efforts between the United States and Israel across bilateral defense technology research, development, testing, evaluation, integration, and industrial cooperation. The scope of that cooperation covers virtually every domain of modern warfare: artificial intelligence, quantum computing, autonomous weapons systems, directed energy weapons, cybersecurity, biotechnology, missile defense, and data fusion — the process by which US military sensor data and Israeli military sensor data are merged into a single shared operational picture.

That last item — data fusion — deserves specific attention beyond its technical description. Data fusion means that the intelligence picture your military is operating from becomes the intelligence picture their military is operating from. In real time. In active conflict zones. The United States military's operational awareness — the sensor feeds, the targeting data, the signals intelligence, the battlefield picture — becomes Israeli military operational awareness under a data fusion framework. The distinction between the two militaries' decision-making processes becomes, in those moments, theoretical rather than practical.

Section 224 would also expand Israeli co-production facilities on American soil — facilities already operating in Arkansas and Mississippi — creating a network of US-based manufacturing jobs tied directly to Israeli defense contracts. The strategic logic of that expansion is not subtle. Jobs in congressional districts create constituent interests. Constituent interests create votes. The Israeli government would gain, through the mechanism of American employment, a structural lobbying asset in every congressional district where those facilities operate — independent of AIPAC, independent of donor networks, embedded directly into the economic life of the community. It is influence through payroll, and it is permanent.

The Data Question Congress Has Not Answered

Before examining the constitutional and moral dimensions of Section 224, there is a foundational operational question that its architects have not publicly addressed — one that is simultaneously practical, strategic, and deeply revealing about the nature of what is actually being proposed.

The United States government cannot reliably share intelligence data between its own agencies. That is not a partisan characterization. It is the documented conclusion of the 9/11 Commission, 25 years of congressional testimony, multiple GAO audits, and the lived experience of every major national security failure since 2001. In July 2001, an FBI agent in Phoenix wrote a memo warning of a coordinated effort by bin Laden to train terrorists in US flight schools. No one in the FBI's bin Laden unit saw it before September 11. The CIA had identified two of the 9/11 hijackers — Hazmi and Mihdhar — as al-Qaeda operatives in January 2000. It did not share that information with the FBI. Both men boarded American Airlines Flight 77 on September 11, 2001. Three thousand people died in part because two agencies of the same government, in the same city, working on the same threat, did not share what they knew.

In the two decades since, the CIA, FBI, DOJ, DOD, DIA, and DHS have all maintained separate intelligence fusion centers. Congressional testimony noted bluntly that "creating and maintaining multiple intelligence centers is a recipe for continued confusion and failure to coordinate." A 2026 Federal News Network report found an average of 137 cyberattacks per week against US and UK government networks in 2025 — a 25% increase year over year — with data security described as under severe and escalating pressure. Senator Chuck Grassley spoke on the Senate floor as recently as March 26, 2026, noting that inter-agency intelligence coordination remains an ongoing challenge requiring active oversight.

That is the domestic reality. Now hold it against what Section 224 proposes.

Section 224 proposes to share real-time military data — sensor feeds, targeting systems, AI decision networks, autonomous weapons platforms, cybersecurity architecture, and quantum computing research — with a foreign military, across borders, in active conflict environments, under an integration framework that Section 224 itself does not define in terms of data governance. The bill text requires the Secretary of Defense to designate an executive agent for synchronization. It does not specify what data will be shared. It does not specify what data will be withheld. It does not define the classification boundaries of the shared network. It does not establish an oversight mechanism for reviewing what Israel has accessed and what it has done with that access. It does not address what happens to shared data if the strategic interests of the two countries diverge. It does not address what happens to American operational security if Israeli networks are compromised.

The question that nobody in the House Armed Services Committee has answered publicly is this: if the United States government cannot build a reliable intelligence-sharing architecture between the FBI, CIA, DHS, DOD, and DIA after 25 years of trying and three thousand dead Americans as the motivation, on what basis does Congress believe it can build a secure, governed, accountable real-time data fusion network with a foreign military? What data governance framework will define what goes to Israel and what does not? Who reviews that boundary? Who enforces it? Who audits compliance? Who is accountable when the boundary is crossed?

These are not rhetorical questions. They are the minimum due diligence requirements for any data-sharing arrangement of this sensitivity — and Section 224 does not answer a single one of them. It requires the Secretary of Defense to synchronize. It does not require him to protect. The absence of that protection framework is not an oversight. It is a choice — and it is a choice that the American public has not been asked to ratify.

The Pollard precedent makes the stakes of that choice concrete. Jonathan Pollard was a US Navy intelligence analyst who pleaded guilty in 1986 to providing classified American intelligence to Israel. He was sentenced to life in prison. The CIA's 1987 damage assessment concluded that his espionage inflicted substantial harm to US intelligence collection and partners — damage so extensive and so sensitive that the full assessment remains classified to this day. Pollard was paroled in 2015, moved immediately to Israel, and received a reception in Tel Aviv that his supporters described as a hero's welcome. The documented harm from one human source — one analyst with selective access — was severe enough to keep classified for nearly 40 years. Section 224 proposes to give the Israeli military institutional, automated, real-time access to American military data networks. The governance framework for that access does not exist in the bill. It has not been publicly designed. It has not been publicly debated. And the committee that drafted the provision has not held a single public hearing on the question.

What This Is — And What It Is Not

Supporters of Section 224 will make several arguments that deserve honest engagement before being weighed against the objections.

The alliance argument holds that the United States and Israel share significant strategic interests in the Middle East, share intelligence through existing frameworks, and have cooperated on missile defense for decades. The Arrow system, Iron Dome, David's Sling — all joint products of US-Israeli defense cooperation. Section 224 deepens an existing relationship rather than creating a new one. That framing is accurate as far as it goes. What it does not address is the categorical difference between cooperation on specific weapons systems and the wholesale fusion of defense sectors across every domain of emerging warfare simultaneously. The US cooperates on specific systems with many allies. It has fused its defense sector with none of them. Section 224 is not deeper cooperation. It is a different thing entirely.

The technology argument holds that Israel's military technology in specific domains — cyber, autonomous systems, urban warfare — is genuinely advanced, and accessing that technology benefits American warfighters. This is accurate. It does not address whether the cost of that access — the surrender of operational independence, the entanglement of command structures, the expansion of foreign influence over American defense policy, and the absence of data governance — is proportionate to the benefit.

The strategic argument holds that in a deteriorating security environment — active conflict in the Middle East, Chinese military buildup in the Pacific, Russian aggression in Europe — the United States needs the deepest possible alliance relationships to maintain military superiority. This is the strongest argument for Section 224. It is also the argument that has been made for every entangling alliance in history — and every entangling alliance in history has eventually required the entangled party to make choices between its own interests and its partner's that it would not otherwise have made.

The Sovereignty Question Nobody Is Asking

The foundational question that Section 224 raises is not whether Israel is an ally. It is whether any ally — regardless of the depth of the relationship, regardless of shared interests, regardless of genuine affection and historical partnership — should have the structural capacity to direct American military action, shape American military capability, and embed its own strategic priorities into the American defense apparatus without the explicit, informed consent of the American people.

The answer that Section 224 provides — buried in a defense authorization bill without public debate — is that the question does not need to be asked. The provision was drafted by the House Armed Services Committee with bipartisan support. It was released Tuesday. It received almost no mainstream media coverage. The American public, whose sons and daughters serve in the military whose sovereignty is being restructured, was not consulted.

The Constitutional architecture of American military power assigns the war-making authority to Congress and the command authority to the president as commander-in-chief, specifically to ensure that the military serves the interests of the American republic and its people — not the interests of any foreign government, however friendly. When the defense sectors of two countries are fused across AI, cyber, autonomous systems, and data networks, the chain of command does not disappear. But it becomes structurally dependent on the continued alignment of interests between the two countries. The moment those interests diverge — and in any long-term relationship between sovereign nations, they will — the American military finds itself operating inside an integrated architecture it cannot easily exit without degrading its own capabilities. That is not a hypothetical. That is what integration means.

The Dereliction Question: Duty, Loyalty, and the Limits of the Legal

The question of whether supporting Section 224 constitutes dereliction of duty by the members of Congress and the president who would sign it deserves a direct answer rather than rhetorical inflation.

Dereliction of duty, in the constitutional sense, requires a failure to fulfill the obligations of office. Every member of Congress takes an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic, and to bear true faith and allegiance to the same. The president takes an oath to preserve, protect, and defend the Constitution. Neither oath contains a carve-out for allied nations. Neither oath permits the subordination of American military sovereignty to the strategic priorities of a foreign government — even a friendly one, even a democratic one, even one with which the United States has deep and genuine shared interests.

Section 224 does not technically violate any existing statute. It is not treason in the legal definition — the Constitution defines treason narrowly as levying war against the United States or adhering to its enemies, giving them aid and comfort. Israel is not an enemy of the United States. No court would entertain a treason charge based on Section 224. That legal clarity does not resolve the moral question, which is distinct from the legal one.

The moral question is this: is it consistent with the oath of office — with the duty to defend the sovereignty and independence of the American military — to deliberately create a structural architecture in which the defense capabilities, intelligence picture, weapons production, and research agenda of the American military are fused with those of a foreign government to a degree that makes independent action operationally difficult? Without a data governance framework. Without public hearings. Without a formal presidential address. Without the informed consent of the American people. The answer to that question is not determined by whether the provision is legal. It is determined by whether it serves the American people first — which is what the oath requires.

The members of Congress who voted for, sponsored, or will vote for Section 224 without demanding full public debate, without holding open hearings, without requiring answers to the data governance questions this dispatch has raised, and without giving the American people the opportunity to weigh in on a decision that restructures the sovereignty of their military — those members are at minimum failing the transparency obligation that democratic representation requires. Whether that failure rises to dereliction is a judgment the American people are entitled to make. They cannot make it if they do not know the provision exists. That is why it was buried.

The Moral Accounting: Every Objection That Has Standing

The first objection is democratic consent. The American people have not been asked whether they want their military fused with Israel's. Public polling consistently shows that a majority of Americans oppose unconditional military support for Israel. A provision of this magnitude should require a national conversation, public hearings, and an explicit legislative mandate — not burial in a defense authorization bill.

The second objection is data sovereignty. The US government has not solved domestic inter-agency data sharing after 25 years and 3,000 deaths as motivation. Section 224 contains no data governance framework — no specification of what will be shared, what will be withheld, who audits compliance, or what happens when the boundary is crossed. The American people have a right to know what their military's data will and will not be shared with a foreign government before that sharing architecture is built. They have not been told. The bill does not tell them.

The third objection is proportionality. The United States has provided Israel with more than $200 billion in inflation-adjusted military assistance since 1948. It has provided diplomatic cover, intelligence sharing, weapons systems, and political support at the cost of its relationships with Arab nations and its credibility as a neutral broker. Section 224 proposes to deepen that commitment to an unprecedented level at a moment when American public opinion is moving in the opposite direction. The proportionality argument — what America gains versus what it gives — has not been publicly made, debated, or justified.

The fourth objection is entanglement. Washington's Farewell Address warned specifically against "permanent, inveterate antipathies against particular nations and passionate attachments for others" that produce governments "slaves" to their affections. Jefferson's first inaugural called for "entangling alliances with none." Section 224 does not create a temporary alliance. It creates permanent structural integration — jobs, facilities, supply chains, data networks, research programs — that becomes progressively harder to exit the longer it operates.

The fifth objection is conflict automaticity. When two militaries are fused at the level Section 224 describes — shared data networks, co-produced weapons, joint research programs, integrated command structures — an attack on one becomes operationally indistinguishable from an attack on both, regardless of what any law says. The practical effect is a mutual defense obligation that Congress has never voted on, the president has never formally proposed, and the American people have never been asked to accept. It is an Article 5 commitment created not by treaty but by integration.

The sixth objection is intelligence sovereignty and the Pollard precedent. The CIA's 1987 damage assessment concluded that Pollard's espionage inflicted substantial harm to US intelligence collection and partners — from one human analyst with selective access. That damage assessment remains classified nearly 40 years later. Section 224 proposes institutional, automated, real-time access to American military data networks with no equivalent oversight framework. The gap between what caused the Pollard damage and what Section 224 enables is not marginal. It is categorical.

The seventh objection is precedent. If the United States fuses its defense sector with Israel's without public debate and without a formal treaty ratified by the Senate, it establishes the model for doing the same with any future ally under any future administration. The precedent is not the content of the specific integration. The precedent is that military sovereignty can be transferred through a buried provision in a defense authorization bill without the American people's knowledge or consent. That precedent, once set, cannot be unset.

Call to Action: The NDAA Vote Is the Line

Section 224 has not passed. It is in the chairman's mark of the House Armed Services Committee. It must survive committee markup, a full House vote, Senate consideration, conference between the two chambers, and presidential signature before it becomes law. Each of those steps is a point of intervention.

Contact your representative and senator today — specifically about Section 224 of the 2027 NDAA. Ask them whether they have read it. Ask them whether they support it. Ask them specifically: what data governance framework governs what American military data will and will not be shared with Israel under Section 224 — and where can the American public read it? Demand written responses. Make them go on record before the vote.

Demand public hearings. The House Armed Services Committee has the authority to hold open, public hearings on Section 224. The American people deserve to hear the data governance architecture explained in public — who defines the boundary between shareable and protected data, who audits compliance, and what the accountability mechanism is when that boundary is crossed. Those hearings have not been scheduled. Demand they are.

Ask the question Washington asked in 1796 that has never been more relevant: whose interests does this serve — and are those interests the same as yours? The United States government could not share intelligence between the FBI and CIA after three thousand Americans died on a clear September morning. Now Congress wants to share real-time military data with a foreign government — with no governance framework, no public debate, and no accountability mechanism. Does that question have an answer you are satisfied with — and if not, does your congressman know you are asking it?

V64OTD // THEY BURIED IT IN THE BILL BECAUSE THEY KNEW YOU'D OBJECT IF THEY ASKED.