Status checked: July 21, 2026
Central finding
The legislation commonly described online as “combining the United States and Israeli militaries” has not been enacted into law as of July 21, 2026.
The proposal would not legally merge the United States Armed Forces with the Israel Defense Forces. It would create a much more extensive framework for joint military-technology research, development, testing, production and procurement.
The proposal began as the bipartisan United States–Israel Framework for Upgraded Technologies, Unified Research, and Enhanced Security Act of 2026, abbreviated as the U.S.–Israel FUTURES Act. Similar language was subsequently placed in Section 224 of a draft National Defense Authorization Act, where it was titled the United States–Israel Defense Technology Cooperation Initiative. The standalone House and Senate bills had not advanced out of committee when the NDAA language became publicly controversial.
Therefore, there is currently:
- No enacted law merging the two militaries.
- No final presidential signature.
- No final House and Senate passage of this provision.
- No complete congressional roll-call vote showing who voted specifically for Section 224.
- No legal transfer of command over American forces to Israel or Israeli forces to the United States.
Any article claiming that Congress has already “combined the U.S. and Israeli militaries” is overstating both the proposal’s contents and its legislative status.
1. What is the legislation called?
The original proposal was introduced as the:
United States–Israel Framework for Upgraded Technologies, Unified Research, and Enhanced Security Act of 2026
Its acronym spells FUTURES.
The House version was introduced by:
- Representative Don Davis, Democrat of North Carolina
- Representative Ronny Jackson, Republican of Texas
Companion legislation in the Senate was introduced by:
- Senator Ted Budd, Republican of North Carolina
- Senator Kirsten Gillibrand, Democrat of New York
The bipartisan sponsorship was deliberate. Supporters presented the proposal as an American defense-innovation measure rather than simply another foreign-aid program.
The standalone bills reportedly remained in committee. However, much of their structure and language reappeared in Section 224 of a draft defense-authorization bill under the name:
United States–Israel Defense Technology Cooperation Initiative.
2. Has it passed?
No—not into law.
The distinction among legislative stages is essential:
| Legislative stage | Status |
|---|---|
| Introduced as standalone House and Senate bills | Yes |
| Received bipartisan sponsors | Yes |
| Endorsed by outside organizations | Yes |
| Advanced out of committee as standalone legislation | No, based on the available record |
| Language added to a draft NDAA | Yes |
| Passed both houses in identical form | No verified evidence |
| Signed by the president | No |
| Currently binding federal law | No |
The draft NDAA language may have been approved during a committee drafting or markup process, which is sometimes described casually as having “passed.” That does not mean the provision has passed Congress.
A bill becomes law only after the House and Senate approve identical legislative text and the president signs it, or Congress overrides a veto. That process had not been completed for this initiative by July 21, 2026.
3. Would it combine the two militaries?
Not in the ordinary meaning of the word combine.
The United States military and the Israel Defense Forces would remain separate institutions with:
- Separate chains of command
- Separate personnel
- Separate military laws
- Separate national governments
- Separate budgets and appropriations
- Separate constitutional and legal authorities
An Israeli official would not automatically gain authority over American troops. An American president would not automatically gain command of the Israel Defense Forces.
However, the proposal could integrate portions of the two countries’ defense-development systems much more closely. That distinction explains why some critics use terms such as “military integration,” even though no institutional merger would occur.
4. What would the initiative do?
The publicly described provisions would direct or encourage expanded bilateral work in military and dual-use technologies. The areas mentioned include:
- Artificial intelligence
- Quantum technologies
- Cybersecurity and cyberwarfare
- Directed-energy and high-powered laser systems
- Counter-drone technology
- Unmanned systems
- Missile and air defense
- Battlefield communications
- Advanced sensing
- Defense manufacturing
- Other emerging military technologies
The framework would support several forms of cooperation.
Joint research and development
American and Israeli military bodies, government laboratories, universities and private companies could conduct coordinated research on technologies that both countries consider militarily useful.
Joint testing
Technology could be tested through facilities, military exercises or operational environments associated with both countries.
Co-production
American and Israeli companies could manufacture components or complete systems together.
Joint ventures
Companies or research institutions from the two countries could create formal partnerships to compete for projects and develop military products.
Licensing agreements
Military technology, intellectual property or manufacturing rights could be licensed between eligible American and Israeli entities, subject to export-control and security rules.
Accelerated fielding
Supporters want technology to move more rapidly from research into operational use by American or Israeli military forces.
U.S.-based production
The initiative reportedly encourages production partnerships inside the United States, allowing advocates to present it as both support for Israel and investment in American manufacturing. AIPAC specifically promoted provisions encouraging U.S.-based co-production, joint ventures and partnerships with Israeli industry.
5. What is genuinely new?
The United States and Israel already cooperate extensively in military technology. Their existing programs include missile-defense development, weapons procurement, joint exercises, intelligence cooperation and research.
The proposed initiative appears intended to make that cooperation:
- Broader across emerging technologies
- More permanent
- More systematically managed
- More accessible to private companies and universities
- More closely connected to weapons production
- Less dependent on one-off congressional programs
- More integrated into ordinary Pentagon research and procurement processes
The significance is therefore not that military cooperation would begin for the first time. It is that cooperation could become a more institutionalized part of the American defense-innovation system.
Critics describe that as deep integration. Supporters describe it as modernizing an established strategic partnership.
6. Who introduced and publicly supported it?
Congressional sponsors
The four principal sponsors identified in the available record were:
| Legislator | Party | State | Role |
|---|---|---|---|
| Don Davis | Democratic | North Carolina | House sponsor |
| Ronny Jackson | Republican | Texas | House sponsor |
| Ted Budd | Republican | North Carolina | Senate sponsor |
| Kirsten Gillibrand | Democratic | New York | Senate sponsor |
These sponsors establish that the initiative had support from members of both parties. Sponsorship is stronger evidence of support than voting for a large NDAA containing hundreds of unrelated provisions.
Foundation for Defense of Democracies Action
FDD Action publicly supported the proposal. Its senior director of government relations, Tyler Stapleton, argued that it would improve cooperation among the public, private and academic sectors and accelerate the development, testing and deployment of defense technologies beneficial to U.S. personnel and Israel.
AIPAC
AIPAC endorsed the legislation and highlighted:
- Joint research and development
- Cooperation with Israeli technology companies
- Co-production
- Joint ventures
- U.S.-based manufacturing partnerships
Available lobbying disclosures were reported as showing that AIPAC lobbied Congress and the Department of Defense concerning the FUTURES Act during the first quarter of 2026.
An endorsement or lobbying disclosure demonstrates advocacy. It does not prove that AIPAC wrote the legislative language or controlled how individual lawmakers acted unless documentary evidence establishes that connection.
7. Who opposed it?
Representative Thomas Massie
Republican Representative Thomas Massie of Kentucky opposed the initiative and participated in an effort to remove the provision from the defense legislation.
Massie has generally opposed foreign military aid and expansive overseas military commitments, including assistance to Israel. His opposition is therefore consistent with a broader noninterventionist and fiscal position rather than opposition limited exclusively to this proposal.
Representative Ro Khanna
Democratic Representative Ro Khanna of California joined Massie in opposing Section 224 and seeking to strip it from the NDAA.
The Massie–Khanna opposition is politically notable because it brought together:
- A libertarian-leaning Republican critic of foreign aid
- A progressive Democrat critical of military escalation and unconditional support for Israel
Their objections concerned the risk of deeper military-industrial entanglement and insufficient scrutiny of how the arrangement could affect U.S. policy.
Senator Bernie Sanders
Senator Bernie Sanders publicly warned that the provision could move the two countries’ defense establishments toward an unprecedented degree of integration without adequate congressional examination. The broader debate was still pending in July 2026.
8. Who voted for it?
This question cannot yet be answered with a verified member-by-member list because there has not been a separate final roll-call vote on the initiative itself.
There are three reasons.
The standalone bills did not receive final floor votes
The House and Senate FUTURES bills reportedly remained in committee. Therefore, the House’s 435 members and the Senate’s 100 members did not cast recorded final votes on those standalone measures.
The NDAA contains hundreds of provisions
Even when lawmakers vote for a complete NDAA, that vote does not necessarily demonstrate support for every section. A member may oppose Section 224 but vote for the final bill because it funds military salaries, weapons, bases or unrelated national-security programs.
Conversely, a member could support Section 224 but vote against the NDAA over spending, domestic-policy riders or another foreign-policy issue.
Committee action may not identify support for one section
If Section 224 was included in a committee-approved draft, a vote for advancing the whole committee bill is not the same as a direct vote for the Israel provision. Unless the committee held a recorded vote specifically on an amendment to add, remove or modify Section 224, it is not responsible to label every committee member who approved the larger package as a supporter of the individual section.
The most reliable current list of affirmative supporters is therefore the legislation’s named sponsors and organizations that publicly endorsed it—not every lawmaker who may have supported a wider defense bill.
9. Was there a vote to remove it?
Massie and Khanna were reported to have led an attempt to strip the provision from the defense measure. However, I did not find an authoritative, completed member-by-member roll call establishing that a final House vote specifically on removing Section 224 had occurred by July 21, 2026.
That should not be confused with the separate July 15, 2026 House vote on $3.3 billion in annual military assistance to Israel.
In that vote:
- 104 representatives voted to remove the aid.
- 314 voted against removing it.
- 10 voted present.
- Massie was the only Republican supporting the amendment.
- 103 Democrats supported it.
That amendment failed. But it concerned annual Foreign Military Financing, not the U.S.–Israel Defense Technology Cooperation Initiative.
The two matters are politically related but legally distinct.
10. Does the proposal commit the United States to defend Israel?
Based on the publicly described language, the initiative is a defense-technology cooperation framework, not a formal mutual-defense treaty.
It does not appear to say that:
- An attack on Israel automatically constitutes an attack on the United States.
- The United States must deploy troops whenever Israel enters a war.
- Israel may order American forces into combat.
- Congress permanently transfers its war powers to either government.
- The United States and Israel become a single military organization.
A formal defense commitment comparable to NATO’s Article 5 would require much clearer language and would raise major constitutional and treaty questions.
Nevertheless, critics argue that extensive technological and industrial integration could create a form of practical dependency. Once the two countries jointly own, manufacture, maintain and rely upon military systems, it could become politically or operationally more difficult for the United States to suspend cooperation during a disagreement.
That is a serious policy concern, but it is different from an automatic legal obligation to enter Israel’s wars.
11. Could Israel obtain sensitive American technology?
Potentially, but not automatically or without restrictions.
The initiative would likely interact with existing laws and regulations involving:
- Arms Export Control Act requirements
- International Traffic in Arms Regulations
- Export licensing
- Classification rules
- Counterintelligence reviews
- Foreign ownership and influence controls
- Congressional notification requirements
- Intellectual-property agreements
- End-use monitoring
- Restrictions on re-export or third-party transfer
A broad cooperation program may expand the number of opportunities for technology transfer, but it does not necessarily repeal those controls.
The policy concern is whether exceptions, streamlined approvals or institutional pressure might make transfers easier over time. Determining that would require examining the final statutory text, implementing regulations and individual agreements. Because no final law exists, claims about exactly what technology will be transferred remain speculative.
12. Would American taxpayers fund Israeli companies?
The initiative could permit or encourage projects involving Israeli companies, but the exact financial distribution would depend upon subsequent appropriations, contracts and cost-sharing agreements.
Possible arrangements include:
- Pentagon contracts awarded to American companies partnering with Israeli firms
- Grants to research consortia
- Cooperative research agreements
- Israeli contributions to joint programs
- U.S. production of Israeli-designed technology
- Israeli production of jointly developed components
- Licensing fees
- Shared intellectual-property arrangements
Supporters emphasize that U.S.-based co-production could create American employment and give the Pentagon access to useful Israeli technology.
Critics argue that the program could use American public money to strengthen Israel’s private defense industry while weakening congressional leverage over Israel.
Both outcomes could occur within the same program. A contract may benefit an Israeli company, an American prime contractor, American workers and both militaries simultaneously.
13. Does this replace annual military aid?
No.
The proposal is separate from the regular U.S. assistance package established under the 2016 memorandum of understanding, which normally provides:
- $3.3 billion annually in Foreign Military Financing
- $500 million annually for missile-defense cooperation
- $3.8 billion in ordinary annual support
The technology initiative would create another channel of cooperation. It would not inherently terminate or replace the existing aid arrangement.
This means the initiative could expand the relationship beyond the traditional model in which the United States provides money for Israel to purchase weapons. It would move toward a model in which the countries jointly develop and produce some military technologies.
14. Arguments made by supporters
Supporters contend that the initiative would:
- Give U.S. forces access to Israeli defense innovations.
- Accelerate the development of counter-drone and missile-defense systems.
- Improve protection for American service members.
- Expand American defense manufacturing.
- Allow technologies to be tested against real-world threats.
- Counter Iran and Iranian-aligned armed groups.
- Improve cyber and artificial-intelligence capabilities.
- Reduce duplication between allied research programs.
- Strengthen supply-chain resilience.
- Formalize a relationship that already exists.
These arguments assume that Israeli technology and operational experience provide measurable value to American national security.
15. Arguments made by critics
Critics contend that the initiative could:
- Deepen U.S. involvement in Israel’s regional conflicts.
- Make the Pentagon institutionally dependent on Israeli technology.
- Transfer sensitive American technology without sufficient scrutiny.
- Subsidize Israel’s defense industry.
- Reduce U.S. leverage over Israeli governments.
- Make future aid restrictions more difficult.
- Create commercial constituencies that lobby to preserve the relationship.
- Bypass public debate by placing the program inside a massive NDAA.
- Connect American military planning more closely to Israeli strategy.
- Insulate the relationship from changes in public opinion.
Critics also object to the process. Adding substantial policy language to a large annual defense bill can make it difficult for legislators to oppose one provision without voting against military salaries, national-defense programs and hundreds of unrelated measures.
16. What the proposal would integrate
A precise description matters.
| Could become more integrated | Would remain institutionally separate |
|---|---|
| Defense research | National command authority |
| Technology testing | Military personnel |
| Weapons development | Military justice systems |
| Manufacturing | National budgets |
| Procurement arrangements | Decisions to declare or conduct war |
| Private defense companies | Constitutional authority |
| Universities and laboratories | Formal sovereignty |
| Intellectual property | Chains of command |
| Maintenance and supply systems | Membership in each country’s armed forces |
The proposal concerns defense-industrial and technological integration, not a literal merger of armed forces.
17. The existing relationship makes the proposal important
The initiative would build on a relationship that already includes:
- Joint missile-defense programs
- Iron Dome cooperation
- Arrow missile-defense development
- David’s Sling
- Directed-energy research
- Joint military exercises
- Intelligence sharing
- American weapons procurement
- U.S. prepositioned military stocks in Israel
- Israel’s status as a major non-NATO ally
- Israel’s participation in the U.S. Central Command region
Because this foundation already exists, even administrative language about expanding cooperation can have substantial effects. A new permanent framework can influence future Pentagon budgets, research priorities and corporate partnerships long after the original political debate has ended.
18. Why the inaccurate “military merger” description spread
The description appears to combine several real facts with an exaggerated conclusion.
The real facts are that the proposal would encourage:
- Joint research
- Joint development
- Joint testing
- Joint production
- Joint ventures
- Licensing
- Manufacturing partnerships
- Closer defense-industry relationships
From those provisions, critics infer that the two defense establishments would become deeply intertwined.
The unsupported leap is describing this as if American and Israeli forces were becoming a single army. The proposal does not abolish either military’s independent command or sovereignty.
A more accurate headline would be:
Congress is considering legislation to deepen U.S.–Israel military-technology and defense-industry integration.
Final Thoughts
The recent proposal does not formally combine the U.S. military and the Israel Defense Forces. It seeks to create a permanent and potentially far-reaching framework for bilateral military-technology cooperation.
It began as the bipartisan U.S.–Israel FUTURES Act, sponsored by Don Davis, Ronny Jackson, Ted Budd and Kirsten Gillibrand. AIPAC and FDD Action publicly supported it. Thomas Massie, Ro Khanna and Bernie Sanders emerged among its most visible critics.
Most importantly, the legislation had not become law as of July 21, 2026. The standalone bills had not received final House or Senate votes, and the similar NDAA provision was still part of an ongoing legislative process. There is consequently no valid list of every member of Congress who “voted to combine the militaries.”
The proposal deserves scrutiny because it could make American and Israeli defense research, industry and procurement substantially more interconnected. But verified reporting should describe it as a proposed defense-technology integration framework—not an enacted merger of two national militaries.
Continue the Exploration
Whether you consider yourself pro-Israel, pro-Palestine, pro-American, critical of American foreign policy, politically undecided, or you’re only beginning to learn about this history, we invite you to keep exploring.
History is rarely changed by reading a single article. Understanding grows when we become willing to examine not only events, but also the assumptions, identities, cultures, fears, loyalties, and narratives that shape the way every one of us interprets those events. Two people can look at the same facts and reach very different conclusions, not because one necessarily cares more than the other, but because each is viewing them through a different lens.
Our goal is not to tell you what to think. It is to encourage the kind of awareness that allows us to think more clearly, ask better questions, recognize our own biases, and remain open to learning—even when the answers are uncomfortable.
If this article sparked your curiosity, consider exploring our collection of articles on identity, culture, perception, awareness, belief, fear, conflict, and the psychology of being human. These subjects may seem unrelated at first, but they often reveal the deeper patterns that influence politics, history, and human relationships across every nation and generation.
For readers who want to explore these questions even further, our book, Proof That You’re God, examines how identity, perception, and consciousness shape the way we experience ourselves, one another, and the world we share. Whatever conclusions you ultimately reach about Israel, Palestine, the United States, or any other subject, we hope your understanding continues to expand through curiosity, careful investigation, and a willingness to question both the world around you and the assumptions within yourself.
