After genocide findings, ICC proceedings, ICJ litigation, collapsing public support, and growing international isolation, Congress is considering legislation that would make the U.S.-Israel military relationship harder to unwind than ever before.
By Omar Afra
Congress is debating whether to move portions of the U.S.-Israel relationship beyond democratic politics altogether. The hilarity of that statement is not lost on us.
When the ranking Democrat on the House Armed Services Committee starts drafting legislation that could deepen military, technological, industrial, procurement, intelligence, and research integration with a foreign state, it deserves alot more than ‘scrutiny.’ Particularly when that foreign state has spent more than a year facing genocide findings from Amnesty International, B’Tselem, Physicians for Human Rights Israel, a United Nations commission of inquiry, and mounting international legal scrutiny, it deserves considerably more. Representative Adam Smith’s proposal is not another symbolic resolution, not another tranche of weapons money, not another round of Beltway incense waved over the phrase “shared values.” It is an attempt to move foreign collusion into the plumbing of government itself through technology sharing, procurement coordination, research partnerships, and institutional arrangements that future administrations may find far more difficult to unwind than to create.
The provision is reportedly Section 224 of the House Armed Services Committee’s draft version of the fiscal year 2027 National Defense Authorization Act, titled the “United States-Israel Defense Technology Cooperation Initiative.” The measure remains early in the legislative process, but the structure matters. According to reporting from The New Arab, the proposal appears in the House Armed Services Committee draft NDAA, the annual defense-policy bill that sets military priorities and spending. Al Jazeera reported that the provision could bind the two countries’ weapons industries closer than ever, deepening cooperation across weapons research, production, and technology. Democracy Now identified the same provision as Section 224 of the 2027 NDAA and described it as a proposal to bring the U.S. and Israeli military systems into far closer alignment.
The usual Washington trick-fuck is to describe this kind of thing as cooperation, then let the word do half the laundering. Cooperation sounds benign. It sounds like joint exercises, staff meetings, shared acronyms, conference rooms with bottled water, some retired colonel explaining interoperability to people who already agreed before the hearing began. The problem is that national-security cooperation rarely stays inside the neat little box used to sell it. Broad authorities become programs. Programs become offices. Offices become budgets. Budgets become constituencies. Constituencies become facts on the ground. By the time the public notices, the decision has already migrated from policy into infrastructure.
From Support to Integration
For decades, Washington’s relationship with Israel has been conducted through familiar channels: aid packages, weapons transfers, intelligence cooperation, diplomatic protection, missile-defense funding, and periodic declarations that the alliance remains “unbreakable.” Whether one supported those policies or opposed them, they remained recognizably political. Congress voted. Presidents signed. Future administrations retained at least some ability to change course.
Smith’s proposal operates at a different level. The significance does not lie in the basic fact of strengthening ties with Israel. Congress has been doing that for decades, usually with the solemnity of a church service and the accounting discipline of a casino. The significance lies in the type of relationship being constructed. Research partnerships, defense-industrial coordination, technology-sharing arrangements, procurement integration, interoperability standards, and institutional cooperation tend to outlive the political coalitions that create them. Once agencies, contractors, universities, laboratories, military planners, and procurement offices begin building systems around those relationships, reversal becomes substantially harder than approval.
That distinction is where the story lives. Aid can be reduced. Weapons transfers can be delayed. Diplomatic language can shift. Institutional integration is stickier. It creates habits, offices, personnel, contracts, technical standards, and classified assumptions that are not easily pulled apart by a future president who decides the relationship has become strategically or morally indefensible.
Supporters will say this is just what allies do. That answer is lazy and assumes we all have the intellect of a ham-sandwich. The United States has alliances all over the world. It has intelligence-sharing structures, joint procurement programs, treaty obligations, basing agreements, and industrial partnerships. None of that makes this proposal ordinary. The United States is not merely cooperating with a foreign state in a calm strategic environment. It is considering deeper military integration with a government whose conduct in Gaza has produced genocide findings from leading human-rights organizations and unprecedented international legal scrutiny.
The Genocide Context Congress Already Knows
Amnesty International concluded in December 2024 that Israel was committing genocide against Palestinians in Gaza. Its report, You Feel Like You Are Subhuman, examined killing, serious bodily and mental harm, destruction of civilian infrastructure, forcible displacement, obstruction of life-saving goods and humanitarian aid, restrictions on power supplies, and statements by Israeli decision-makers. Amnesty’s summary stated that its research found sufficient basis to conclude that Israel had committed and was continuing to commit genocide against Palestinians in Gaza. Amnesty’s public release was not coy about the finding.
B’Tselem, one of Israel’s most prominent human-rights organizations, later published Our Genocide, writing that since October 2023 Israel’s military onslaught in Gaza had included mass killing, the creation of unlivable conditions, serious bodily and mental harm to an entire population, destruction of basic infrastructure, and forcible displacement on a huge scale. Physicians for Human Rights Israel reached the same conclusion. Amnesty welcomed the Israeli organizations’ reports in July 2025, describing them as a milestone after B’Tselem and PHRI concluded that Israel was committing genocide against Palestinians in Gaza. That mattered because these were not foreign critics parachuting into the issue. They were Israeli organizations documenting the actions of their own state.
A United Nations commission of inquiry has also accused Israel of genocide in Gaza. The Associated Press reported that the UN Human Rights Council’s independent commission found Israel responsible for committing four of the five acts defined as genocide under the 1948 Genocide Convention. Israel rejected the findings, as it has rejected Amnesty’s conclusions and other genocide accusations. The existence of Israel’s denial does not erase the institutional fact before Congress: major human-rights organizations, Israeli human-rights groups, UN investigators, genocide scholars, and international legal bodies have placed Gaza inside the vocabulary of genocide for more than a year.
Congress is not operating in ignorance. Nobody on the House Armed Services Committee can credibly say they missed the Amnesty report, the ICJ case brought by South Africa, the ICC proceedings, the UN investigations, the B’Tselem report, the PHRI finding, the starvation data, the destroyed hospitals, the leveled neighborhoods, the mass displacement, the footage, the satellite imagery, the bodies, the famine warnings, or the repeated targeting of civilian infrastructure. The argument in Washington is not happening before the facts arrive. The facts have been sitting on the table. Congress is stepping around them.
Why Now Is the Whole Game
The political environment around Israel has changed. The old bipartisan consensus still exists inside Congress, but outside Congress it is rotting in visible ways. A March 2025 Gallup poll found that only 46 percent of Americans sympathized more with Israelis than Palestinians, the lowest level in Gallup’s 25 years of tracking the question. Sympathy for Palestinians reached 33 percent, a record high in that trend. Gallup’s 2026 data found 57 percent of Americans in favor of an independent Palestinian state, nearly matching the highest level the organization had measured. Gallup also found Israel’s favorable rating at 46 percent and favorable views of the Palestinian Territories at a new high of 37 percent.
Pew’s numbers point in the same direction. In April 2026, Pew Research Center reported that 60 percent of U.S. adults held an unfavorable view of Israel, up from 53 percent the year before and nearly twenty points higher than in 2022. Pew also found that 59 percent had little or no confidence in Benjamin Netanyahu to do the right thing regarding world affairs. Among adults under 50 in both parties, majorities rated Israel and Netanyahu negatively. In October 2025, Pew reported that 70 percent of Democrats and Democratic-leaning independents viewed the Palestinian people favorably, while only 18 percent of Democrats viewed the Israeli government positively.
That is the context in which Netanyahu’s government has every incentive to bank as many structural concessions as possible while Washington’s official machinery remains friendly. The Trump administration gives Israel a window. Congressional leadership gives Israel a window. The defense industry gives Israel a window. The foreign-policy diarrhea-blob, with its donor circuits and think-tank laundering facilities, gives Israel a window. A government facing declining public support abroad, legal jeopardy, and reputational collapse will naturally try to convert temporary political cover into durable institutional advantage. That is not a conspiracy theory. That is how power behaves when it sees the weather changing.
Testset has argued elsewhere that Democrats cannot keep treating unconditional support for Israel as a cost-free position while their own voters move in the opposite direction. See “Democrats Can Support Israel or Win Elections. They Cannot Do Both.” The Adam Smith proposal fits that same larger pattern: elected officials moving to entrench a policy consensus that is weakening among the public, then acting surprised when voters eventually notice the rigged wiring behind the drywall.
The Ratchet Effect
Defense programs do not become permanent because they remain persuasive. They become permanent because they accumulate dependencies. Contractors hire around them. Congressional districts benefit from them. Agencies write budgets around them. Research institutions build labs around them. Military planners fold them into doctrine. Lobbyists defend them. Think tanks produce white papers explaining why any reduction would invite catastrophe. The program becomes less a policy than an ecosystem.
Washington has lived this pattern repeatedly. Surveillance authorities passed after September 11 metastasized into a durable intelligence architecture. FISA expansion created secret legal and bureaucratic habits that proved hard to contain. The F-35 became less a plane than a politically distributed industrial organism, with suppliers spread across so many states and districts that cancellation became almost impossible regardless of cost criticism. AUKUS began as a strategic technology and submarine partnership, but it also created long-term industrial, nuclear, procurement, and training commitments that will shape policy for decades. Five Eyes intelligence-sharing functions less like a temporary arrangement than a permanent operating environment for the security services that participate in it.
None of those examples are identical to Section 224. They are examples of how national-security architecture behaves once built. The public sees the announcement. The durable action happens later, through agency interpretation, budget lines, classified guidance, contractor dependence, and bureaucratic momentum. That is why ambiguity in defense legislation is never harmless. It is an invitation for future expansion.
If Section 224 creates a coordinating mechanism for U.S.-Israel defense technology cooperation, the next questions are not theoretical. Who controls the scope? What technologies are included? What data flows are permitted? What procurement relationships become favored? What joint development programs become eligible for funding? What reporting requirements exist? What limits apply to Israeli access to U.S. systems, research, or industrial processes? What happens when an Israeli firm becomes embedded inside a supply chain servicing American military needs? What happens when the next administration wants distance but discovers distance now threatens programs, jobs, contracts, and readiness assumptions?
Follow the Contractors
Military integration creates beneficiaries. It is not an abstraction. American defense demons such as Lockheed Martin, RTX, Northrop Grumman, Boeing, General Dynamics, and L3Harris already operate inside a procurement environment where foreign military sales, missile defense, sensor systems, drones, munitions, avionics, command-and-control platforms, and surveillance technologies generate enormous recurring revenue. Israeli defense firms such as Elbit Systems, Israel Aerospace Industries, and Rafael Advanced Defense Systems occupy their own deeply embedded position in drones, missile defense, surveillance, targeting, border systems, and battlefield electronics.
Every new research initiative, interoperability framework, procurement preference, technology-sharing channel, and joint development program creates another place for these interests to attach. The money rarely announces itself as ideology. It arrives as technical necessity. Then the same companies and their lobbyists explain that pulling back would damage readiness, weaken the alliance, or endanger troops.
That is how a political decision becomes an industrial constituency. Once enough people get paid to treat integration as permanent, permanence starts being described as common sense.
The Taiwan Test
The strongest argument against this proposal may not come from Gaza at all. It comes from the Pentagon’s own China rhetoric.
American defense officials repeatedly describe China as the central strategic challenge of the century. Pentagon planning documents emphasize supply-chain resilience, industrial capacity, secure technologies, redundancy, and freedom of action in a future Pacific crisis. Taiwan is routinely described as one of the most dangerous flashpoints in the world. If those warnings are serious, then Congress should be reducing unnecessary external dependencies inside America’s defense ecosystem, not creating new ones.
A Taiwan contingency would stress U.S. military logistics, shipbuilding, munitions production, air defense, cyber capacity, intelligence systems, satellite architecture, semiconductor supply chains, and allied coordination. The last thing any serious planner should want is a defense architecture more entangled than necessary with another foreign military operating under its own political pressures, regional conflicts, intelligence priorities, and industrial interests.
This is not an argument for isolation. It is an argument for strategic hygiene. A country preparing for a possible confrontation with China should be extremely careful about where it builds technological dependency. If the United States needs sovereign capacity in munitions, AI systems, cyber tools, drones, sensors, manufacturing, and battlefield software, then Congress should explain why deeper integration with Israel enhances that sovereignty rather than diluting it.
Supporters of Section 224 should not be allowed to hide behind alliance language. They should identify the limits. They should say which technologies are excluded. They should explain how data is protected. They should state whether Israeli firms could gain preferential access to U.S. procurement pathways. They should describe what a future administration would need to do if it wanted to unwind the structure. They should explain why a Congress that claims to fear Chinese leverage over supply chains is comfortable building additional leverage points for another foreign state inside the military-industrial base.
Gaza Is Not Happening in Isolation
Israel’s conduct in Gaza cannot be separated from its conduct across the region. Southern Lebanon has been treated as a laboratory for destruction, displacement, and territorial pressure. Testset has covered this in “Gaza-fication in Southern Lebanon: Israel’s Village Destruction Looks Less Like War Than Ethnic Cleansing” and “The Colonial Thirst for Southern Lebanon.” The pattern is not simply military exchange along a border. It includes destruction of villages, attacks on civilian infrastructure, agricultural devastation, displacement, and a long-running strategic fixation on water, land, and the Litani River.
That matters because American military integration with Israel is not integration with a neutral software vendor. It is integration with a military currently engaged across Gaza, the West Bank, Syria, Lebanon, and Iran-adjacent theaters, while operating under a political leadership that has shown no meaningful restraint in turning civilian space into pressure architecture. When U.S. lawmakers deepen military and technological cooperation under these conditions, they are not merely supporting deterrence. They are building American systems closer to a regional war machine already accused of genocide in Gaza and accused by critics of ethnic-cleansing patterns in southern Lebanon.
Lebanon is where the Taiwan argument and the Gaza argument meet. A future American administration may want to restrain Israel in Lebanon, distance itself from another regional escalation, or reduce exposure to Israeli decision-making during a wider war. That becomes harder if cooperation has been converted into shared systems, joint programs, and industrial dependency. The more integrated the architecture, the more every Israeli war becomes an American management problem.
The Political Coalition Behind the Cement
The pro-Israel consensus in Washington is not sustained by public opinion alone. It is sustained by donors, lobbying groups, primary threats, evangelical theology, defense contractors, congressional habits, and a foreign-policy class trained to treat criticism of Israel as a career hazard. AIPAC and allied groups have spent heavily in Democratic primaries to punish critics and protect incumbents. Republican support is fueled not only by strategic arguments but by Christian Zionist theology, including end-times narratives that treat Israeli state power as a religious instrument rather than a normal foreign-policy question.
Testset has covered that theological machinery in “A Sharp, Sober Analysis by Omar Afra: Unpacking Christian Zionism’s End-Times Theology.” The relevance here is not academic. A foreign-policy consensus shaped by donors, arms manufacturers, and apocalyptic religious blocs is now being asked to make decisions about advanced military technology, procurement integration, and future American strategic flexibility. That is a bad room to leave unattended.
The point is not that every supporter of Section 224 shares the same motive. Some believe the U.S.-Israel military relationship genuinely serves American interests. Some see Israel as a critical regional partner. Some are responding to donors. Some are afraid of lobbying pressure. Some are ideological. Some are just doing what Washington has trained them to do. Motive matters less than structure. The structure being contemplated would give today’s political coalition influence over tomorrow’s military architecture.
What Congress Needs to Answer
Section 224 should not advance through the defense bill as a quiet technical provision. If Congress wants deeper U.S.-Israel military integration, members should defend it in plain English. They should answer whether the initiative creates an executive agent or coordinating office, what authority that entity would possess, which agencies would participate, which technologies would be eligible, what role Israeli defense firms would play, what protections exist against transfer to third parties, what reporting Congress would receive, and how a future administration could terminate or limit the arrangement.
They should also explain why this is happening now. Not in the abstract. Now, after Amnesty’s genocide report. Now, after B’Tselem and PHRI. Now, after the ICJ proceedings. Now, after the UN commission findings. Now, after Gallup and Pew show a measurable deterioration in public support for Israeli government policy, especially among younger Americans and Democrats. Now, while southern Lebanon is being battered and Gaza remains the central moral catastrophe of the century.
The public is usually asked to debate Israel through regurgitated slogans: ally, democracy, security, antisemitism, terrorism, shared values. Those words do useful work for people who do not want procurement questions asked in public. The harder questions are mechanical. What gets built? Who gets access? Who gets fuuuuuuuuuuucking paid?
Congress appears to be converting a political relationship into a structural one. Structural relationships are harder to reverse than political decisions. That is the danger. It is not hidden in some secret doctrine. It is visible in the architecture, the timing, the ambiguity, the contractor incentives, the legal context, and the predictable behavior of national-security institutions once they are given a new channel to expand.
The people promoting this should have to defend the whole fucking thing, not just the glossy brochure version. But really, there is no defending this shit.
Omar Afra is a writer, cultural producer, and founder of Testset. His work focuses on culture, technology, power, war, and the infrastructure beneath public life. He also builds cedar pergolas. More at testset.media/authors/omar-afra.

Comments