Section 224
How Congress Is Building Israel Permanently Into the Pentagon’s Future War Machine
A single clause in the FY2027 National Defense Authorization Act would move the US-Israel military relationship from financial aid to institutional merger, across every major domain of modern warfare, and make it structurally irreversible. Here is what it does and why American readers need to understand it now.
Section 224 of the House Armed Services Committee’s draft FY2027 National Defense Authorization Act is sixty-seven words in summary form. The clause, titled the “United States-Israel Defense Technology Cooperation Initiative,” requires the Secretary of Defense to designate an executive agent responsible for synchronizing cooperative efforts between the United States and Israel across bilateral defense technology research, development, testing, evaluation, integration, and industrial cooperation. The NDAA is the legislation through which Congress sets American military policy and authorizes defense programs each fiscal year. It is a $1.15 trillion bill, and it is the document that builds the Pentagon’s future: program by program, office by office, contracting vehicle by contracting vehicle. Congress has now written Israel into that future as a statutory partner, housed inside the Pentagon itself, at the level of research and industrial cooperation rather than weapons transfers.
The analysts who have read Section 224 carefully have reached a consistent conclusion: that this provision would arguably do more to intertwine the two countries’ militaries than the more than $200 billion in inflation-adjusted military assistance the United States has provided Israel since 1948. The precise claim requires an explanation to be meaningful, because the argument is not quantitative. It is structural. Aid, at any scale, carries with it the architecture of political choice. It requires annual authorization, appears in appropriations debates, and can be reduced, conditioned, or cancelled by future Congresses with the political will to act. Section 224 operates under a different logic entirely. Once research programs are shared, testing infrastructure is jointly operated, industrial production lines are co-managed, and data architectures are built together, the relationship ceases to present itself as a series of discrete political decisions. It presents itself as a technical reality that future administrations inherit and manage rather than choose. Before Section 224, the United States and Israel had a relationship built on financial transfers and specific co-development agreements, each of which required some form of political authorization. Section 224 converts that relationship into institutional infrastructure lodged permanently inside the department that builds American weapons, and the distance between those two models is where the argument about American sovereignty and democratic accountability lives.
How Section 224 Entered the Bill
Section 224 did not originate as an NDAA initiative. It arrived through the legislative mechanism of absorption: the provision began as a standalone bill called the US-Israel Future of Warfare Act, introduced by Representative Ronny Jackson of Texas, a former White House physician who has positioned himself as one of the most aggressive advocates for Israeli military cooperation in the Republican caucus. The standalone bill did not advance through committee. Its core language was instead folded into the NDAA, a procedure that is both routine in Washington and significant in this context. Routine, because legislation that lacks the political oxygen to survive independent scrutiny is regularly embedded in must-pass annual bills, acquiring the status of law without the deliberation its consequences would otherwise require. Significant, because the question that Section 224 answers, whether the United States should build a permanent institutional mechanism for merging its military technology development with a foreign state’s, is one that, stated plainly, would require a national conversation. Stated as a sixty-seven-word executive agent clause inside a $1.15 trillion defense authorization bill, it requires nothing: no Senate ratification, no treaty process, no public hearings on the provision’s strategic implications, and no vote that a constituent could easily identify or hold a representative accountable for. The provision’s drafters understand that the NDAA’s complexity is not incidental to their strategy; the design of Section 224 depends on the public not registering it as the decision it is.
What the Provision Actually Covers
The technology domain list in Section 224 is the first place the ambition of the provision becomes concrete. Al Jazeera’s reporting on the bill identified the priority areas the legislation envisions for cooperation: counter-unmanned systems across aerial, maritime, and ground platforms; anti-tunnelling and subterranean threats; missile and air defense technologies; artificial intelligence, quantum machine learning, and autonomous systems; directed energy and advanced sensing; cyber defense, electronic warfare, and digital resilience; biotechnology, biomanufacturing, and medical defense. Each of those domains represents a major sector of American military investment over the coming decades. Together, they describe something close to the entire frontier of modern and future warfare.
Two phrases embedded in the legislative framing have drawn specific and serious attention from defense analysts: “network integration” and “data fusion.” These are not vague terms in the military context, and their inclusion is not accidental. Network integration, in defense acquisition and command-and-control architecture, refers to the connection of communications and information systems across platforms, services, and in this case national militaries. Data fusion refers to the integration of sensor and data streams from multiple sources, systems, and domains into a unified operational picture. Both concepts sit at the core of the United States’ Joint All-Domain Command and Control program, the multi-billion-dollar architecture through which the Pentagon is attempting to link its air, land, sea, space, and cyber capabilities into a single integrated command network. If network integration and data fusion with Israel are among the goals of the executive agent’s synchronization mandate, the implications run considerably deeper than co-developing a next-generation drone or sharing missile defense code. They potentially reach into the intelligence feeds, sensor architectures, and real-time targeting data streams that constitute American military situational awareness at the operational level.
The inclusion of biotechnology, biomanufacturing, and medical defense in the domain list is unusual in a military cooperation provision and has received less public scrutiny than the AI and cyber elements. These are inherently dual-use fields: their applications span legitimate defense medicine, pandemic preparedness, and advanced biological research, but their presence in a military integration statute raises oversight questions that the provision does not address. The breadth of the domain list is not the product of legislative ambition running ahead of specifics. The people who drafted this language specified each domain deliberately, and the comprehensive scope is the point.
Title XII: Section 224 as Capstone
Section 224 does not operate as an isolated provision. Title XII of the House draft contains a dedicated subtitle on Israel that should be read as a coherent legislative package rather than a collection of independent clauses. Section 1221 extends the War Reserve Stockpile Authority for Israel through January 1, 2029, the mechanism through which the United States pre-positions weapons and military equipment on Israeli soil for deployment in regional conflicts. Section 1222 extends US-Israel subterranean cooperation through December 31, 2029 and broadens its scope from tunnel detection specifically to all subterranean threats of every type. Section 1223 extends cooperation to counter unmanned systems in all warfighting domains, including aerial, maritime, and ground platforms, through the same date. Section 224 sits at the end of that sequence as the coordinating architecture that governs all of it. It is the mechanism that gives the specific cooperations an executive home inside the Pentagon, ties them to budget lines, assigns institutional responsibility for synchronizing their development, and ensures their continuity across changes in administration, changes in political temperature, and changes in public opinion.
The Title XII subtitle, read in sequence, reveals a legislative posture that is systematic rather than opportunistic. The provisions extend and deepen the relationship in three dimensions simultaneously: time, operational domain, and institutional depth. The question that the full subtitle leaves open, and that Section 224’s drafters have not been asked publicly to answer, is whether any future Secretary of Defense, confronted with the executive agent’s statutory mandate to synchronize cooperation across research, development, testing, evaluation, integration, and industrial cooperation, would retain the practical political space to exercise that mandate narrowly.
Two Hundred Billion Dollars, and Why the Aid Frame Misses the Point
The United States has provided Israel an estimated $200 billion in inflation-adjusted military assistance since Israel’s founding in 1948, making Israel the largest cumulative recipient of American military aid in history, according to the Quincy Institute’s analysis. The Council on Foreign Relations places the combined figure, including economic assistance, at over $300 billion in inflation-adjusted terms. The current governing framework, the 2016 memorandum of understanding covering fiscal years 2019 through 2028, committed $38 billion over ten years: $33 billion in Foreign Military Financing and $5 billion for missile defense, disbursed at approximately $3.8 billion annually. Emergency supplementals since October 7, 2023 have added substantially to that total, including an $8.7 billion package passed in April 2024, of which $5.2 billion was designated for air defense assets. By any measure, Israel is the pre-eminent recipient of American military resources in the post-World War II era.
Ben Freeman of the Quincy Institute argued in Responsible Statecraft that Section 224 would arguably do more to intertwine the two militaries than all of that prior assistance combined. The framing is worth taking seriously rather than dismissing as hyperbole, because the underlying analytical distinction it is drawing is precise. Every dollar of the $200 billion in military aid was authorized through a political process that, however inadequate its accountability mechanisms, preserved the theoretical capacity for democratic revision. Arms transfer notifications under the Arms Export Control Act give Congress the opportunity, if it chooses to exercise it, to block specific weapons transfers. Annual appropriations create the recurring political occasion for debate and conditioning. Foreign Military Financing requires reporting requirements that generate at least a paper record of the choices being made. The Obama administration’s 2016 MOU, often cited as evidence of the relationship’s unconditional character, was nonetheless a publicly visible commitment that required a deliberate political decision by an elected administration and that could, in principle, be revised by a successor.
Integration operates by different rules. Research programs, once initiated, generate shared intellectual property that neither party owns independently. Testing infrastructure, once built jointly, creates operational dependencies that shape subsequent procurement decisions. Industrial co-production arrangements, once established, create employment and contractual relationships that generate their own political constituencies. The relationship stops presenting itself as a political question and starts presenting itself as an operational and industrial fact. Making the core of the bilateral relationship politically invisible as public opposition to it builds is Section 224’s central strategic function, and the people who designed the provision understood that when they wrote it.
The Executive Agent and How Permanence Is Made
The phrase “executive agent” is carrying significant institutional weight in Section 224, and it is worth explaining precisely what it means within the Department of Defense’s organizational structure. Under DoD Directive 5101.1, an executive agent designation assigns a single military service, unified command, or defense agency the responsibility and authority for leading DoD activities in a specified functional area on behalf of the Secretary of Defense. The executive agent designation is not honorary or advisory. It produces a portfolio: plans, programs, staffed billets, program officers, budget justifications, reporting requirements, and the alignment of planning assumptions across the bureaucratic stakeholders relevant to the designated domain.
Congress is not passing a resolution encouraging the Pentagon to cooperate more closely with Israel. It is mandating the creation of a specific kind of institutional actor inside the department, with statutory standing and a defined portfolio encompassing research, development, testing, evaluation, integration, and industrial cooperation across the full range of bilateral defense technology. The designated service or agency will stand up an office. It will fill positions, assign program officers to Israeli counterpart relationships, identify contractors for joint work, and begin generating the budget justifications and planning documents that shape future weapons programs. Each cycle of that institutional activity deepens the relationship’s entrenchment in ways that are largely invisible to the public and largely irreversible by the time any political actor is in a position to scrutinize them.
The contractors who receive initial contracts under the executive agent’s portfolio will pursue follow-on contracts. Program officers who build working relationships with their Israeli counterparts will advocate, within the normal channels of defense acquisition management, for expanding those relationships. Budget lines created to support the executive agent’s work will appear in subsequent budget submissions as existing commitments rather than new proposals, requiring active political effort to reduce rather than passive inaction to preserve. Steven Simon, in a Quincy Institute brief cited by Responsible Statecraft, identified the critical political consequence of this dynamic: shifting the relationship from an aid model to an integration model moves it out of visible appropriations politics and into the opaque machinery of defense acquisition, where oversight is limited, political accountability is minimal, and the public has no easy mechanism for forming or expressing a view on the decisions being made. When Congress votes on a $3.8 billion annual military aid package, that vote generates press coverage, advocacy responses, and some measure of public accountability. When the executive agent’s office approves a joint AI development program with Rafael Advanced Defense Systems as part of its Section 224 mandate, that approval will appear in a program office document distributed to a small number of people with the appropriate clearances, none of whom are accountable to the public for the decision in any direct or observable way.
The Industrial Dimension: Arkansas to the Future
In East Camden, Arkansas, a missile factory jointly operated by Raytheon and the Israeli defense company Rafael Advanced Defense Systems opened in November 2025. Built through their joint venture R2S, the facility is the first plant in the United States capable of producing Tamir and SkyHunter interceptors from start to finish on American soil. Tamir is the interceptor at the core of Israel’s Iron Dome system. SkyHunter is its American-branded variant, adapted for the Marine Corps’ Medium Range Intercept Capability program. On May 4, 2026, R2S delivered the first batch of SkyHunter interceptors to the Marines under a multi-year program whose initial production contract is worth $1.25 billion, financed in part through American foreign aid flowing back into Israeli defense procurement and through the joint venture into American manufacturing employment. Workers in East Camden now build missiles for two armies on the same production line.
This is what the Iron Dome co-development relationship has produced across three decades of iteration: a joint venture between an American prime contractor and an Israeli defense company, employing American workers in an American congressional district, with a nine-figure production contract and a political constituency that effectively prevents serious congressional challenge to the underlying bilateral arrangement. The trajectory from initial cooperation agreement to mature co-production relationship followed a predictable path. US funding for Iron Dome began under the Obama administration. Co-development expanded to co-production as the partnership matured. Rafael and Raytheon established R2S as the institutional vehicle for American production. The Camden facility, completed in November 2025 with an initial $1.25 billion contract to supply Israel with Tamir interceptors, is the current terminal point of that trajectory. David’s Sling, the next tier of Israel’s layered air defense architecture, followed an analogous path: US funding, co-development between Rafael and Raytheon, and co-production arrangements now embedded in both countries’ procurement planning. Arrow-3, the upper tier, is a joint program between Boeing and IAI. Each of these systems began as a specific cooperation agreement and matured into a production relationship that is now built into the procurement structure of both militaries.
Section 224 does not confine this model to missile defense. It extends the logic to AI, cyber, quantum computing, autonomous systems, directed energy, and biotechnology. Each of those domains would, under Section 224’s mandate, produce its own version of R2S: joint ventures or co-production arrangements between American prime contractors and Israeli defense companies, including Rafael, Elbit Systems, and Israel Aerospace Industries, employing American workers in American congressional districts, tied to production contracts that acquire their own political constituencies over time. Freeman argued in Responsible Statecraft that this expansion would give the Israeli government a stronger foothold in American domestic politics than its already substantial network of lobbyists, political donors, and advocacy organizations currently provides. The argument is precise and the mechanism is well understood in American political economy: when a defense program employs workers in a congressional district, the representative of that district ceases to evaluate the program on its foreign policy merits and begins evaluating it on its employment consequences. The political economy of the bilateral relationship, already formidable, would be systematically replicated across the defense industrial base.
The Oversight Gap: From Appropriations to Acquisition
Military aid to Israel, in the form of Foreign Military Financing, runs through the State Department’s budget and requires annual authorization and appropriation through the congressional process. It appears in published budget documents, is subject to Government Accountability Office audit requirements, and can trigger the Arms Export Control Act’s notification requirements when specific arms transfers are involved. Advocacy organizations track the figures. Congressional offices that wish to condition or oppose specific packages have procedural mechanisms to do so: holds, conditioning amendments, notification requirements, committee hearings. The accountability is incomplete and can be circumvented, as the Biden administration demonstrated by approving more than one hundred arms deals below the notification threshold after October 2023. But the formal architecture of visibility exists and creates at least the possibility of political accountability.
Defense acquisition operates under a categorically different set of institutional rules. Programs managed by a DoD executive agent appear in the Future Years Defense Program, the Pentagon’s classified and semi-classified planning document, as program element lines requiring specialist knowledge to locate and interpret. They are subject to oversight by the Armed Services Committees, but that oversight is technical, occurs largely through classified briefings rather than public hearings, and produces results on timelines that bear no relationship to the pace of public political deliberation. The contractors and program offices involved have access to the relevant oversight processes in ways that advocacy organizations and the general public do not. The Government Accountability Office audits acquisition programs, but its findings frequently require years to produce and do not generate the immediate political accountability that an annual aid authorization does, however imperfectly.
The critical point Simon identified is that moving the core of the US-Israel military relationship from the appropriations process into the acquisition process is not a neutral administrative change. It is the removal of the relationship from the domain of democratic visibility into a domain where the public has no direct mechanism for observation or influence, and where the institutional actors with standing to shape the relationship’s development are the program officers, defense contractors, and executive agent staff who manage it rather than the elected representatives or constituents who bear its strategic and financial consequences.
Lock-in and the Problem of Successive Administrations
Mark Hilborne of King’s College London’s School of Security Studies told Al Jazeera that Section 224 points toward a relationship that might survive changing administrations in the United States because the relevant development cycles are very long and would become entrenched over time. The observation deserves to be understood in terms of what those development cycles actually look like in the technology domains Section 224 covers.
An AI-enabled autonomous systems program initiated under the executive agent’s mandate might require between eight and fifteen years to reach operational deployment. A directed energy weapons program, from initial research collaboration to fielded system, runs a similar timeline. Quantum computing applications for military command and control are likely decades from operational relevance. These timelines mean that programs initiated in fiscal year 2027 under the executive agent’s statutory mandate will reach maturity under administrations that did not make the initial decisions about which research pathways to pursue, which Israeli industrial partners to work with, or which technical standards to adopt. Those successor administrations will find that joint intellectual property has been produced, co-production relationships have been established, interoperability standards have been written into weapons systems specifications, and data fusion architectures have been built into the intelligence and targeting infrastructure of American forces. Unwinding any component of that would require actively dismantling programs that have generated both operational capabilities and domestic political constituencies, a combination that democratic governments have historically found prohibitively costly to pursue.
A weapons transfer can be halted at the next appropriation without disrupting operational capacity. A co-development program that has been running for six years and has produced shared intellectual property, joint testing data, and interoperability specifications built into the next generation of American combat platforms does not have a clean discontinuation point. The lock-in that Hilborne is describing is not a political metaphor but a description of how technical and economic dependencies compound across long defense acquisition cycles until the option of discontinuation carries genuine operational costs.
The Bipartisan Opposition and What It Costs
Representative Ro Khanna of California, a Democrat and member of the House Armed Services Committee, announced he would offer an amendment to strip Section 224 during the June 4, 2026 committee markup. Representative Thomas Massie of Kentucky, a Republican, pledged a floor amendment if the provision survived the committee vote. “If the provision in the NDAA to integrate/synchronize the U.S. and Israeli militaries (section 224) makes it out of committee,” Massie wrote on X, “I’ll offer an amendment to strip it from the bill on the floor. We are a sovereign country.” Khanna responded: “And I will be offering an amendment in the committee itself to strip section 224 out, @RepThomasMassie. Trump can’t kill the Massie/Khanna partnership no matter how much he posts on Truth Social.”
The bipartisan character of that opposition matters, but so does the context in which it has been declared. Massie lost his Republican primary on May 19, 2026, to Ed Gallrein, a retired Navy SEAL recruited and endorsed by President Trump, in what the Associated Press described as the most expensive US House primary on record, with more than $32 million in advertising spending. Pro-Israel political organizations joined Trump allies in funding the campaign against Massie, who has represented Kentucky’s 4th Congressional District since 2012. The race targeted Massie for his opposition to the Iran war, his work with Khanna on the Epstein Transparency Act, and his broader resistance to Trump’s legislative agenda. He conceded in Hebron, Kentucky, to a crowd that chanted “No more wars” and spoke of young voters whose views, he said, were still with him. He leaves Congress in January 2027.
Representative Derrick Van Orden of Wisconsin attacked Massie publicly after his statement against Section 224, accusing him of anti-Semitism and arguing that the provision would allow the United States to “leverage advanced Israeli technologies.” Massie’s response was brief: he asked Van Orden whether the integration deal would qualify the United States for “those advanced Israeli pagers,” a reference to Israel’s September 2024 operation in which pagers and other communications devices carried by Hezbollah members were remotely detonated, killing dozens and wounding thousands of people, a number of whom were civilians and emergency responders. The exchange was conducted over X and lasted minutes. But it described the political terrain of the issue with considerable accuracy: a chamber in which questioning the depth of US-Israel military integration still carries a serious political cost, in which the accusation of anti-Semitism is deployed as a first response to substantive policy criticism, and in which the bipartisan opposition that has correctly identified the problem must operate against an institutional and financial asymmetry that Massie’s primary outcome has now quantified at $32 million. Khanna can offer his committee amendment, and he may press it to a vote. But the political machinery that backed Section 224 into the NDAA, and that spent eight figures to remove the most effective Republican critic of unconditional Israeli military support from the Congress, is not operating at the margins of American legislative politics.
Public Opinion Against, Policy Moving Forward
A New York Times poll published in May 2026 found that only 30 percent of Americans said Donald Trump made the right decision in ordering military strikes against Iran, while 64 percent said it was the wrong decision. An Institute for Global Affairs survey released the same week found that only 16 percent of Americans supported continuing weapons transfers to Israel without additional restrictions; 38 percent said the United States should stop supplying weapons to Israel entirely; and 24 percent said military aid should be conditioned on how the weapons are used. The polling reflects a shift in American public opinion on the bilateral relationship that has been building over multiple years and that has accelerated since October 2023. It also describes a public and a Congress moving in opposite directions.
That divergence is legible once the mechanism is understood. Relationships insulated from democratic accountability deepen as public opposition builds, because the institutional processes through which deepening occurs operate in spaces that public pressure cannot easily reach. When the relationship is governed by annual aid authorizations, public opinion can in principle be brought to bear through the normal mechanisms of representative democracy: constituent calls, electoral consequences, organized advocacy, and press attention that generates political cost for individual legislators. When the relationship is governed by executive agent portfolios, co-development programs, joint ventures, interoperability standards, licensing agreements, and data fusion protocols, the legible surface area of the policy contracts to near zero. The formal mechanisms of accountability remain theoretically available; in practice they require a level of technical expertise, institutional access, and organized political capacity that is distributed asymmetrically between the relationship’s critics and its proponents. Congress’s response to a public that polls at 38 percent in favor of ending weapons transfers to Israel entirely is to pass Section 224, moving the core of the military relationship out of appropriations politics and into the acquisition machinery where that public opinion has no direct access, and where the interests capable of sustaining the relationship’s growth can operate without the friction that democratic visibility creates.
The Sovereignty Argument
American officials have consistently described the United States as the senior partner in the bilateral relationship with Israel: the superpower dispensing aid, weapons, and diplomatic cover at the United Nations, with Israel as a militarily capable but resource-dependent beneficiary. That framing captures a real asymmetry of scale. It systematically understates the structural dependencies that run in the other direction. The American political class has, over decades, built a system in which Israeli strategic priorities are reliably advanced through US legislative, industrial, and bureaucratic channels, through a combination of electoral influence, lobbying infrastructure, and media engagement that represents the most effective foreign policy advocacy operation in American history. The Massie primary, in which more than $32 million was spent to remove a Republican congressman for, among other things, his opposition to unconditional Israeli military support, is the current iteration of that infrastructure’s capacity.
Section 224 would extend the relationship’s entrenchment from the political layer into the technical and industrial layer, and the two layers would then reinforce each other. Israeli threat assessments, procurement priorities, and industrial capabilities would be built into the planning assumptions of American defense development at the level of the executive agent’s working relationships, program requirements, and budget justifications, before reaching any visible political deliberation. The question of whether American weapons development should be optimized to incorporate Israeli strategic priorities alongside American ones would cease to be a political question contested in Congress and would become a technical question managed in the executive agent’s office and the program offices aligned with it.
Writing a foreign military partner into the management architecture of your own future war-making systems is not a feature of normal alliance management. NATO integration, to which advocates of Section 224 sometimes appeal by comparison, involves mutual collective defense obligations codified in a treaty ratified by the Senate, with institutional structures subject to multi-decade democratic deliberation across more than thirty member states. Section 224 involves no mutual defense commitment, no Senate-ratified treaty, no reciprocal obligation from Israel, and no institutional transparency mechanism of any kind. It involves a sixty-seven-word executive agent designation inside an NDAA subtitle, enacted without the deliberation that its strategic consequences would require.
The critical unanswered question that Section 224 generates is not whether the United States and Israel will continue to cooperate militarily. They will, and there are genuine arguments for specific forms of cooperation. The question is what happens to American defense planning and American strategic autonomy when the executive agent’s working assumptions, built over years of synchronized development with Israeli military and industrial counterparts, conflict with a future American administration’s strategic preferences in a region where Israel is simultaneously an ally and a principal actor in ongoing conflicts. The provision offers no answer to that question, and its drafters have not been asked to provide one.
The people who wrote Section 224 understand that administrative language travels further than honest declarations precisely because it generates less political resistance. A formal statute explicitly titled the United States-Israel Military Integration Act would require a national debate and would face organized opposition. A management function buried in Title II of a $1.15 trillion NDAA, entering through the absorption of a standalone bill that could not pass on its own merits, requires only that the markup vote go as planned and that the provision survive the legislative process without generating the public attention that might force a real reckoning. Procedure is how dependency passes into law, and once the executive agent’s office exists, the briefings are being produced, the contractors are under contract, the planning assumptions have been built into the development programs of the next generation of American weapons systems, and the relationship has moved another notch away from political choice and toward state architecture.