They Just Handed Israel the Keys to the Pentagon; And Called It a Routine Bill By Ryan Cox-Bedsworth | OCCUPIED While most Americans were going about their day, the House Armed Services Committee sat in a room this morning and debated whether to permanently fuse the United States military with the Israeli Defense Forces; then voted to keep it in the bill. They called it a “common sense” defense cooperation initiative. They said it was nothing new. They said anyone who had a problem with it was just letting politics get in the way. They lied. Section 224 of the FY2027 National Defense Authorization Act; titled the United States-Israel Defense Technology Cooperation Initiative; is not routine. It is not an extension of existing programs. It is a structural lock-in mechanism designed to make the merger of American and Israeli defense infrastructure legally irreversible, institutionally self-perpetuating, and politically impossible to undo. Here is what they did not tell you. The Executive Agent Nobody Can Touch The bill’s opening provision requires the Secretary of Defense to designate a single Executive Agent responsible for synchronizing all U.S.-Israel defense cooperation. That agent has authority that supersedes other DOD component heads; including the Defense Technology Security Administration, the agency specifically tasked with controlling foreign access to sensitive American technology. There is no congressional confirmation required for this position. Congress has no removal authority. An unelected, unconfirmed individual; appointed by Pete Hegseth; will have overriding authority over the most sensitive technology transfer decisions in the U.S. military, with no legislative check whatsoever. When one member on the committee said this structure “improves oversight and accountability,” he meant that oversight now runs through a single unaccountable official instead of through Congress. That is not oversight. That is a handoff. And about Pete Hegseth: this is the man whose primary military advisor is a dual-citizen attorney with a law practice in Jerusalem. The man put in charge of picking the person who will oversee this entire bilateral framework is himself operating under the influence of the same foreign lobby that wrote the framework. The idea that “Americans are still in charge” because the Secretary of Defense picks the executive agent collapses immediately when you look at who the Secretary of Defense is and who his top advisor is. The Language Is Vague on Purpose The word “synchronizing” appears in the operative text of the bill. It is not defined anywhere. This is not a drafting oversight. In DOD practice, synchronization means aligning planning cycles, operational timelines, and resource allocations. Applied here; with an unconstrained executive agent and no statutory definition; it could mean Israeli defense procurement priorities are embedded into American acquisition planning before Congress ever votes on a budget line. The same problem runs through “network integration” and “data fusion”; two terms that appear in the bill’s stated scope and are never defined. In military context, network integration means connecting command-and-control architectures. Data fusion means merging intelligence and sensor feeds into shared operational pictures. Left undefined and delegated to an unconfirmed official, this language could authorize Israeli military access to U.S. battlefield data streams, ISR feeds, and communications architecture with no specified limits and no oversight mechanism. Vague language in law is not a flaw. It is a feature. It becomes whatever the person interpreting it decides it means. And the person interpreting it was picked by a man who takes his military counsel from an Israeli attorney. The Lock-In Architecture Section (a)(1) directs integration of Israeli-origin technologies directly into U.S. programs of record. Once a technology is embedded in a program of record, removing it triggers contract modifications, recertification requirements, and industrial base disruption. The financial and political costs become prohibitive. Future administrations and future Congresses that oppose the arrangement will find themselves trapped; not by law, but by the economic gravity of what has already been built. Section (a)(3) then explicitly directs the transition of those technologies from research and development into procurement and acquisition pathways. Once a system enters procurement, it is governed by multi-year contracts, not annual appropriations. It is shielded from the budget process. It becomes, as a practical matter, permanent. Section (a)(4) establishes frameworks for Israeli defense companies to manufacture inside the United States; which sidesteps Buy-America provisions designed to protect the domestic defense industrial base. It also creates licensing agreements that could hand Israeli firms intellectual property for weapon systems they compete against directly in the international arms market. American taxpayer-funded R&D, handed to a foreign commercial competitor. There is no sunset clause in this bill. No congressional reauthorization requirement. No performance benchmarks. No withdrawal mechanism. The framework, once established, runs indefinitely. The Statutory Assumption That Will Cost Us Everything The most dangerous sentence in the bill is in Section (a)(2). It frames the entire arrangement around protecting “the national security interests of the United States and Israel”; as a single, unified concept. That is now written into operative statutory text. If this bill becomes law, it is no longer a policy preference or an administrative assumption that American and Israeli security interests are aligned. It is a premise embedded in federal law. The legal and policy space to argue that U.S. and Israeli interests diverge on a given technology, operation, or conflict; disappears. Think carefully about what that means. The Israeli Security Cabinet has already approved 34 new West Bank settlements, each a violation of international law. The Gaza health authorities have confirmed more than 70,000 Palestinian deaths. The ICC has issued warrants. The Leahy Law and the Foreign Assistance Act both have provisions that should have already triggered suspension of military assistance. They have not been enforced. This bill does not just continue that pattern. It buries it in statute. Any future administration that wants to hold Israel accountable under existing American law will find itself in conflict with a statutory premise that treats the two countries’ national security interests as inseparable. Any war Israel starts, we are now legally and institutionally pre-positioned to fight alongside them. They already got the automatic draft registration passed. The bodies have to come from somewhere. One Voice Called It Out. Then They Voted It Down. Rep. Ro Khanna brought the amendment to strip Section 224 from the bill. He was joined by Rep. Sara Jacobs of California. That was it. Two members out of the entire House Armed Services Committee willing to stand up and say this is not what American law should look like. Rep. Jacobs made the point clearly: in 2021, the Commerce Department blacklisted NSO Group; the Israeli firm behind Pegasus spyware; after its tools were turned against American officials and journalists. Two administrations, from both parties, left it on that list. That same company is currently attempting to re-enter the American market. Section 224 would fuse our defense and technology sectors with Israel permanently, in the exact domain where we have already been burned, with no human rights conditions and almost no oversight. The members who voted to keep Section 224 in the bill stood up one after another and said the same things. It’s a win-win relationship. We’ve gained so much from this partnership. They’re our closest ally. They’re the only democracy in the Middle East. Not one of them named a specific technology the United States gained from Israel that it could not have developed independently. Not one acknowledged that the “technologies” Israel is famous for; Iron Dome components, surveillance systems, counter-drone capabilities; trace heavily back to American funding, American research institutions, and American tax dollars cycled through Israeli defense contractors. The circular nature of that argument apparently didn’t register. This Is the Bill Netanyahu Wrote The legislation’s own sponsors acknowledge it derives from H.R. 7540 and S. 3855; the U.S.-Israel FUTURES Act; introduced by Rep. Jackson and Sen. Budd. The architecture of the provision aligns precisely with what the Israeli government has been lobbying for through official and unofficial channels for years. The Ranking Member, Adam Smith, actually said something worth noting before he voted to keep the provision: he criticized Netanyahu’s leadership, called out the endless wars, expressed frustration with the lack of any peace effort. Then he turned around and voted against the amendment to remove the bill’s most expansive provision institutionalizing cooperation with that same government. That is the complete picture of where we are. Even the members who understand what is happening are not willing to act on it. Members Claimed to Not See Any Letter Or Evidence That Netanyahu Wrote The Resolution US Representative Marlin Stutzman met with Israeli PM Benjamin Netanyahu in Jerusalem to discuss this resolution. Why are US Representatives meeting with foreign leaders and passing legislation that is based on the needs of the foreign government? Here is the proof: The Existing Laws Being Ignored Rep. Jacobs laid it out plainly. The Leahy Law prohibits military assistance to foreign forces that have committed gross violations of human rights. The Foreign Assistance Act prohibits arms transfers to countries blocking American humanitarian aid; and Israel
