Codify — Article

FUTURES Act (S.3855) creates U.S.–Israel defense tech cooperation initiative

Creates a DoD-led program to accelerate Israeli-origin and jointly developed defense technologies into U.S. systems, with reporting obligations and three years of authorized funding.

The Brief

The FUTURES Act directs the Secretary of Defense, with concurrence from Israel’s Minister of Defense, to stand up a U.S.–Israel Defense Technology Cooperation Initiative to speed collaborative research, testing, prototyping, and industrial partnerships that move Israeli-origin and jointly developed technologies into U.S. military systems. The initiative covers a broad set of domains — from counter‑UAS and anti‑tunneling to AI, directed energy, biotech, and network integration — and requires DoD coordination across relevant components and Federal agencies.

For compliance officers, acquisition leads, and industry executives, the bill matters because it creates a formal channel for prioritizing Israeli capabilities for U.S. adoption, establishes structured pathways for co‑production and licensing, and mandates oversight and public updates. Those operational changes will affect acquisition timelines, export‑control workflows, and partnership strategies for both U.S. and Israeli defense firms.

At a Glance

What It Does

The bill requires the Secretary of Defense, with Israeli concurrence, to establish a cooperative initiative that identifies Israeli‑origin or jointly developed technologies for U.S. integration, runs collaborative R&D, facilitates transition into procurement pathways, and supports joint industrial arrangements such as licensing and co‑production.

Who It Affects

Affected parties include DoD components (from DARPA to the Missile Defense Agency and USSPACECOM), U.S. and Israeli defense firms pursuing co‑production or licensing, capability development and prototyping organizations, and acquisition program offices responsible for integrating new systems into programs of record.

Why It Matters

The initiative formalizes a cross‑agency mechanism to accelerate foreign‑origin tech insertion, potentially shortening the time from prototype to fielding while creating new regulatory and acquisition touchpoints — from export controls to sustainment planning — that stakeholders must manage.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

Under the bill the Department of Defense must stand up a named initiative — the United States‑Israel Defense Technology Cooperation Initiative — in partnership with Israel’s Ministry of Defense. The Initiative is explicitly missioned to spot Israeli‑origin or jointly developed technologies that have operational utility for U.S. systems, shepherd them through collaborative research and prototyping, and create commercial frameworks (joint ventures, licensing, and U.S.‑based co‑production) that make industrial integration feasible.

The statute lists specific technology domains the Initiative should prioritize: counter‑unmanned systems (air, sea, ground), anti‑tunneling, missile and air defense (including an explicit reference to 'Golden Dome for America'), AI/quantum/autonomy, directed energy, cyber and electronic warfare, biotech and medical defense, data fusion and logistics, and broader defense industrial cooperation. It requires DoD to coordinate internally — naming components such as the Irregular Warfare Technical Support Directorate, Defense Innovation Unit, DARPA, Missile Defense Agency, and U.S. Space Command — and externally with the Departments of State and Commerce to ensure legal and export‑control consistency.Transparency and oversight are built into the program: DoD must brief Congress within 180 days on initial steps and then deliver annual reports covering activities, progress on integrating technologies into acquisition programs, partnerships formed, and recommendations for future priorities and authorities.

Reports must be unclassified where practicable, though classified annexes are allowed; DoD also must post periodic unclassified updates on a public website while safeguarding classified or export‑sensitive material.Finally, the bill authorizes funding to support the Initiative over a defined three‑year window. The statutory language creates a focused, DoD‑led mechanism intended to accelerate bilateral R&D and industrial collaboration, while embedding reporting and public reporting requirements to track how Israeli innovations move into U.S. capabilities.

The Five Things You Need to Know

1

The Secretary of Defense must establish the United States‑Israel Defense Technology Cooperation Initiative with the concurrence of Israel’s Minister of Defense.

2

The Initiative names ten priority domains, including counter‑UAS, anti‑tunneling, missile/air defense (explicitly 'Golden Dome for America'), AI/quantum/autonomy, directed energy, cyber/electronic warfare, and biotech/medical defense.

3

DoD must provide an interim briefing to congressional defense committees not later than 180 days after enactment detailing stand‑up steps, initial technology areas, and lead components.

4

DoD must submit annual reports (unclassified with a possible classified annex) that describe activities, technologies transitioned into U.S. acquisition programs, partnerships, and recommended authorities and resources.

5

The bill authorizes $150 million per year for fiscal years 2027 through 2029 to carry out the Initiative.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

Designates the bill as the 'United States‑Israel Framework for Upgraded Technologies, Unified Research, and Enhanced Security (FUTURES) Act of 2026.' Practically this is the capstone label that DoD and implementing offices will use in planning documents, solicitations, and public materials tied to the program.

Section 2

Sense of Congress

States congressional findings about the strategic importance of U.S.–Israel defense ties and recalls prior agreements such as the 2016 10‑year MOU on military assistance. While non‑binding, this section sets the political justification for accelerated cooperation and will shape how agencies prioritize the Initiative against other bilateral and multilateral efforts.

Section 3(a)–(c)

Establishment and scope of the Initiative

Requires DoD, with Israeli concurrence, to create a structured program that identifies Israeli‑origin or jointly developed technologies and accelerates their movement into U.S. systems and industrial partnerships. The provision specifies activities — joint R&D, protected information handling, transition into procurement, and industrial frameworks — and directs DoD to coordinate internally (naming several DoD components) and with State and Commerce externally to align with legal and export constraints. Practically this places responsibility with DoD acquisition and innovation offices to produce processes that link foreign tech evaluation, prototyping, and acquisition planning while maintaining national security safeguards.

3 more sections
Section 3(b)

Priority technology domains

Lists targeted domains (counter‑UAS; anti‑tunneling; missile/air defense; AI/quantum/autonomy; directed energy; cyber/electronic warfare; biotech/medical defense; network integration/data fusion; defense industrial base cooperation). By enumerating areas, the statute nudges program managers to prioritize those capabilities for resourcing and prototyping — which can shape solicitation language, partnership incentives, and what technologies receive rapid transition paths.

Section 4

Reporting, transparency, and congressional oversight

Imposes a 180‑day interim update to congressional defense committees on stand‑up actions and initial areas, and then annual reports describing activities, assessment of progress, technologies transitioned into acquisition programs, partnerships, and recommendations for authorities and resourcing. Reports must be unclassified to the maximum extent practicable and may contain classified annexes. The section also directs DoD to post periodic unclassified updates publicly while withholding classified or export‑sensitive material, creating parallel transparency obligations for both Congress and the public.

Section 5

Authorization of appropriations

Authorizes $150 million for each of FY2027–FY2029 to 'carry out this Act.' This is an authorization rather than an appropriation; implementing offices will need Congress to appropriate funds or reprogram existing resources to execute activities in the near term.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Defense across all five countries.

Explore Defense in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • U.S. military services and combatant commands — they gain a formal mechanism to identify and accelerate fielding of Israeli‑origin capabilities that can fill operational gaps faster than traditional acquisition pipelines.
  • Israeli defense firms — the Initiative offers structured routes into U.S. markets via licensing, joint ventures, and co‑production arrangements that can expand sales and U.S. manufacturing partnerships.
  • DoD innovation organizations (e.g., Defense Innovation Unit, DARPA) — they receive priority authority and a clearinghouse for bilateral projects and prototyping efforts that can move promising tech toward programs of record.
  • U.S. defense prime contractors and manufacturers who engage in co‑production — those that partner with Israeli firms can win new contracts and supply‑chain roles tied to jointly produced systems.

Who Bears the Cost

  • U.S. taxpayers and appropriations committees — the program carries an authorizing price tag of $150 million per year for three years and will pressure appropriators to fund priorities or reallocate existing budgets.
  • Department of Defense components and acquisition program offices — they must absorb planning, integration, oversight, and sustainment work to vet foreign‑origin technologies and adapt acquisition pathways.
  • Export‑control and regulatory agencies (State, Commerce) — these agencies will face increased workload to reconcile cooperative arrangements with ITAR, EAR, and other controls and to issue licenses or special authorities.
  • Small U.S. defense firms without established Israeli partnerships — such firms may face competitive pressure if co‑production and licensing arrangements favor Israeli incumbents or large primes that can integrate foreign tech.

Key Issues

The Core Tension

The central dilemma the bill creates is speed versus control: it forces DoD to deliver faster access to allied innovation and industrial partnerships while maintaining strict controls over classified capabilities, export‑controlled technologies, and long‑term sustainment — objectives that often pull in opposite directions and have no single technical fix.

The bill accelerates bilateral tech insertion while leaving several operational questions unresolved. Key implementation challenges include how DoD will reconcile accelerated transition pathways with existing acquisition law and sustainment obligations — for example, selecting a path that ensures long‑term logistics support and software sustainment for foreign‑origin systems.

Export controls are another practical choke point: collaborative R&D and co‑production will require careful licensing decisions and, in some cases, new or exception authorities to move controlled technologies across borders without undermining U.S. national security.

The funding language authorizes three years of resources but does not appropriate them; absent appropriations the Initiative must rely on reprogramming or competing budget priorities. Finally, the statute directs public updates while permitting classified annexes — balancing transparency and operational security will require disciplined redaction standards, or the program risks either over‑classifying useful information or leaking sensitive technology details that could compromise export control regimes or tactical advantages.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.