Four things are happening simultaneously in the United States right now. Each of them is, individually, underreported. Together, they constitute something that has no precedent in the modern American political era: the assembly, piece by piece, of a permanent entanglement between American military power, Israeli defense infrastructure, a domestic AI surveillance apparatus, and an ocean of money flowing through channels most Americans cannot see and were never asked to approve. This is the first installment of The Illuminated Record. We will put it all on the table.
The Bill: What Section 224 Actually Builds
On May 27, 2026, buried on page 847 of a $1.15 trillion defense authorization bill, the House Armed Services Committee quietly released Section 224 — titled the “United States-Israel Defense Technology Cooperation Initiative.” Its language is bureaucratic. Its implications are not. C1
Section 224 directs the Secretary of Defense to designate a single executive agent responsible for synchronizing U.S.-Israeli military cooperation across every domain of modern warfare: artificial intelligence, quantum computing, autonomous weapons systems, directed energy, cyber and electronic warfare, biotechnology, and what the text calls “network integration” and “data fusion.” That last phrase deserves to be read slowly. Data fusion between U.S. and Israeli military systems means, in operational terms, that classified American intelligence infrastructure — signals, surveillance architectures, targeting algorithms — would be accessible to a foreign government’s military apparatus. C1
This is not an aid package. It is not a weapons sale. It is architectural. Section 224 would embed Israel into the American defense supply chain at a level of integration the United States has not extended to any other nation on earth — not the United Kingdom, not Canada, not any NATO ally. Importantly, the oversight mechanism is deliberately constrained: the Pentagon must file annual reports through 2030, but those reports “may include a classified annex.” The provision was co-authored by HASC Chairman Mike Rogers (R-AL) and Ranking Member Adam Smith (D-WA) — the committee’s top Republican and top Democrat — and has not faced a single public hearing. C1
Section 224 is not merely a policy preference. Once enacted, it embeds Israeli defense technology into U.S. military programs of record — the formal acquisition pipeline. Programs of record are extraordinarily difficult to reverse: they involve contracts, supply chains, congressional district jobs, and classified dependencies. The Quincy Institute’s Steven Simon has documented that this shift moves the relationship from visible annual aid votes into the “opaque machinery of defense acquisition, where oversight is limited and political accountability is minimal.” In practice: once this integration is operational, the question of whether to continue it becomes a logistical impossibility rather than a political choice.
Section 224 also includes a provision requiring the Pentagon to post public updates “to the maximum extent practicable.” That phrase — standard national security boilerplate — means the public may get patriotic summaries while the operational architecture disappears behind classified annexes. C1
The bill’s legal ancestry matters. Section 224 is derived from two prior bills: H.R.7540 and S.3855, both known as the U.S.-Israel FUTURES Act, introduced by Rep. Van Taylor (R-TX) and Sen. Ted Budd (R-NC). Neither bill advanced on its own merits through regular order. Instead, their provisions were folded into the must-pass NDAA — which has passed every year since 1961 — specifically to avoid the kind of standalone floor debate that might attract public attention. This is not a conspiracy. It is standard legislative strategy for provisions that authors correctly anticipate would face public opposition if debated openly. C1
Section 224 is not legislation. It is a lock. It is the mechanism by which a foreign policy no longer supported by most Americans becomes structurally impossible to reverse — before the politics fully catch up.
The financial architecture driving Section 224 is not new. The Syndicate documented in detail how defense contractor lobbying spending, AIPAC electoral funding, and congressional stock trading in defense equities form an interlocking system in which the same officials who vote on military spending hold financial stakes in its outcome. Section 224 expands that architecture: every co-production facility it authorizes in a U.S. congressional district becomes a job creation argument, a lobbying lever, and a political lock. The machinery documented in Chapter VI built the environment in which Section 224 was possible. The NDAA is where it graduates to permanent infrastructure.
The Cloud: Project Nimbus and the Digital Backbone of Occupation
Section 224 does not exist in a vacuum. The data integration it proposes between U.S. and Israeli military systems already has a corporate antecedent — and that antecedent has been operating, largely without public notice, since 2021. It is called Project Nimbus. C1
In April 2021, the Israeli Finance Ministry announced a $1.2 billion contract split between Google Cloud Platform and Amazon Web Services to provide Israeli government agencies, security services, and military units with comprehensive cloud computing infrastructure, artificial intelligence, and machine learning capabilities. The contract was initially framed as a benign government modernization project — health records, transit systems. Leaked Israeli Finance Ministry documents, obtained by a joint investigation between +972 Magazine, Local Call, and The Guardian and published in February 2026, revealed the contract’s actual architecture: Israel required both companies to build physical data centers entirely within Israeli borders, creating a “Sovereign Cloud” governed exclusively by Israeli domestic law. C1
The contract contained two provisions of particular significance. First, it prohibits Google and Amazon from restricting how Israel uses their products — even if that use breaches the companies’ own terms of service. Second, it requires both companies to tip off the Israeli government if a foreign court demands its data — meaning that legal accountability mechanisms in other jurisdictions are contractually neutralized. A confidential internal Google report, obtained by The Intercept in May 2025, made explicit what Google’s own executives understood: the company could not control what the Israeli government or military did with its technology, and the contract could obligate Google to obstruct criminal investigations by other nations. C1
Project Nimbus is a $1.2 billion contract between the Israeli government and Google/Amazon, signed 2021, running for an initial seven years with extension options. Physical data centers were built inside Israeli borders to create a Sovereign Cloud governed by Israeli law. Leaked contract terms prohibit the companies from restricting Israeli use of the technology even if that use violates the companies’ own terms of service. A second provision requires companies to alert Israel if foreign courts demand its data, effectively shielding Israeli military operations from international legal accountability.
The contract explicitly covers the Israeli Defense Ministry. A Google document obtained by TIME Magazine showed the company billing the Israeli Ministry of Defense over $1 million for consulting under the Nimbus framework, with a 15% discount applied “as a result of the Nimbus framework.” Google told its own employees that Project Nimbus “is not directed at highly sensitive, classified or military workloads.” The Israeli contract document states the government “may make any use of any service included in the supplier’s catalog of services.” Both statements cannot be simultaneously true.
In September 2025, Microsoft announced the cessation of some of its Israeli government deal. Israeli data moved to Amazon. Google retains its multi-billion dollar commitment. As of May 2026, more than 1,000 workers at Google’s DeepMind lab in the UK have demanded formal union recognition, with Project Nimbus as a primary stated cause. Over 90 Google workers and 300 Amazon workers have signed internal protest letters.
The connection between Project Nimbus and Section 224 is structural, not speculative. Section 224’s “data fusion” provision would extend the same model — U.S. technology embedded in Israeli military systems, governed by Israeli law, shielded from American congressional oversight — from the commercial sector into the official defense acquisition pipeline. Project Nimbus is the proof of concept. Section 224 is the formalization. LI
By May 2026, reporting from multiple sources documents that the IDF has moved from monitoring past actions to algorithmic prediction of “future threats” — flagging civilians for detention or interrogation based on probabilistic AI outputs before any act has occurred. The cloud infrastructure running this system is Project Nimbus. The AI models generating its outputs were built, at least in part, using Google’s machine learning capabilities. Google promised its employees the system is not used for “weapons or intelligence services.” Its own contract says otherwise. Section 224, if enacted, would move this model into the official U.S. defense acquisition chain. C2
The Show Must Go On documented financial conflicts of interest at the intersection of U.S. defense contracting and Israeli military operations — specifically the undisclosed advisory relationships between U.S. defense officials and Israeli defense firms. Project Nimbus adds a new layer: the same tech infrastructure companies with $80M+ in annual Washington lobbying spend (Google, Amazon, Microsoft) are simultaneously providing the cloud backbone for Israeli military AI operations while pursuing U.S. federal contracts worth tens of billions. The revolving door between DoD procurement, Big Tech government contracting, and Israeli defense adjacency has never been more directly documented.
The Infrastructure: $77 Billion, 76 Projects, and the Physical Backbone
While the legislative and contractual architecture has been assembling quietly in Washington and corporate boardrooms, the physical infrastructure of this system is being built across America in plain sight — on farmland, adjacent to nuclear power plants, on former industrial sites — at a scale that has no historical precedent. C1
Total U.S. data center construction spending in 2025 reached an estimated $77.7 billion — a 190% year-over-year increase from 2024, according to a February 2026 ConstructConnect report. Average monthly spending on data center construction jumped from roughly $500 million in mid-2021 to $6.5 billion in December 2025 alone. ConstructConnect is tracking 76 data center projects set to start in 2026. Virginia received the most data center funding of any state in 2025 at $15.3 billion; Louisiana received $15 billion; Mississippi received $13.9 billion; Texas $13.4 billion. C1
The geographic pattern of this buildout is not random. The largest concentrations are in states with the lowest regulatory barriers, the cheapest land, and the most favorable tax treatment — and in states that are also home to significant congressional defense committee membership. Mississippi, where Israeli defense company Rafael already operates a co-production facility manufacturing anti-tank missiles in Tupelo, received $13.9 billion in data center construction starts in 2025. Arkansas, where Rafael’s R2S subsidiary opened a manufacturing facility in Camden, is the site of the largest single data center investment in the state’s history. C1 LI
This is the co-production geography that Section 224 would formalize and scale. The data centers are not Israeli. The co-production facilities are. What Section 224 does is create the legal architecture to connect them — to make the data infrastructure and the weapons manufacturing infrastructure part of a single, officially sanctioned, classified U.S.-Israeli industrial system, anchored in congressional districts whose representatives now have a constituent jobs reason to support it regardless of their other policy views. LI
The Trump executive order of July 2025, which directed streamlined permitting, regulatory rollbacks, and access to federal land for large-scale AI data center construction above 100 megawatts, removed the primary friction points that had slowed the buildout. The administration has explicitly framed this as an economic competitiveness initiative. It is also, structurally, the ground preparation for the physical layer of what Section 224 intends to wire together. C1
The Quanfinity Project’s prior Data Centers investigation documented in detail the Palantir layer of this infrastructure: DHS’s $1 billion blanket purchase agreement with Palantir Technologies in February 2026; the ICE ELITE platform and ImmigrationOS built on Palantir infrastructure; the Army’s swearing-in of Palantir executives as Army Reserve lieutenant colonels; and Alex Karp’s documented statements about “elites restoring control” through AI tools. The data centers now being built at $77.7 billion annually are the physical housing for that surveillance architecture. Section 224 would embed Israeli AI and autonomous systems development into the same supply chain that feeds Palantir’s U.S. government contracts.
The Money Map: A Comprehensive View of What Flows Where
Formal military aid is the most visible channel of American financial support for Israel, and it is massive. But it is not the only channel — not by a long distance. A complete picture of U.S.-to-Israel financial flows requires looking at six distinct streams, operating under different legal frameworks, with different disclosure requirements, and with varying degrees of public visibility. The picture that emerges is of a financial relationship whose true aggregate scale is substantially larger than any single figure in public reporting. C1
Three aspects of this money map deserve particular emphasis because they are almost entirely absent from mainstream coverage. First, the tax-deductibility of private donations: under Article 15A of the 1975 U.S.-Israel Income Tax Treaty, American donors can deduct contributions to Israeli charities from their U.S. federal taxes, provided the organizations would qualify for tax-exempt status under U.S. standards. This effectively means the U.S. Treasury subsidizes private American philanthropic support for Israel — including, as reporting from the Associated Press and Shomrim revealed in 2024, organizations that have actively worked to block humanitarian aid from entering Gaza. C1
Second, the Israel bonds mechanism: American state and local governments — most significantly Florida under Governor Ron DeSantis — purchased approximately $300 million in Israel bonds in the period following October 7, 2023. These are sovereign debt instruments. When a state pension fund or municipal government buys Israel bonds, it is lending money to the Israeli government at interest rates that, by multiple accounts, are modest compared to comparable instruments. State government officials described these purchases explicitly as acts of solidarity — using public funds, without a vote of affected citizens, to extend credit to a foreign government. C1
Third, and most significant for understanding Section 224: the AIPAC electoral spending figures. The $126.9 million spent in the 2023–24 cycle is the documented number. The 2026 figure is higher: the United Democracy Project entered the midterm cycle with $91.6 million in cash on hand. In the 2026 Illinois congressional primaries, AIPAC-affiliated donors funneled at least $25 million through entities with names like “Elect Chicago Women,” “Affordable Chicago Now!,” and “Chicago Progressive Partnership” — PACs that bore no visible connection to Israel policy. Voters had no way of knowing that the most expensive outside spending in their primary was driven by a foreign policy agenda. C1
The full financial architecture is not AIPAC. It is not aid. It is not bonds. It is all of them at once, operating simultaneously through different legal channels, each individually defensible, collectively constituting the most comprehensive foreign policy financial operation in American history.
The Allegiances: Who Benefits, Who Voted, Who Holds What
Understanding why Section 224 was written the way it was — and why it was dropped into a must-pass bill without a public hearing — requires understanding the financial allegiances of the people who built it. This is not a claim of corruption. It is a documentation of disclosed conflicts of interest and documented financial relationships, all of which are in the public record. C1
HASC Chairman Mike Rogers (R-AL), who co-authored Section 224, has received documented AIPAC-aligned contributions in prior election cycles. His ranking partner Adam Smith (D-WA) represents a district that includes Boeing — the largest U.S. defense contractor by revenue — and has received campaign contributions from defense industry PACs in every election cycle since 2004. The bipartisan authorship of Section 224 is not incidental: it reflects what the Quincy Institute and others have documented as a structural alignment of both parties’ institutional leadership on Israel, driven by the fact that AIPAC spent to defeat progressive critics and that the defense industrial lobby funds members on both sides of the aisle. C1 LI
Miriam Adelson — widow of casino magnate Sheldon Adelson, single largest individual donor to Trump’s 2024 presidential campaign, recipient of Israel’s Medal of Valor. The Adelson family’s combined political spending since Citizens United exceeds any other family in American history. She purchased a controlling stake in the Las Vegas Review-Journal in 2015. Her money flows directly to the elected officials voting on Section 224.
Peter Thiel — PayPal co-founder, Palantir co-founder, major Republican Party donor. Palantir holds $1 billion+ in active U.S. government contracts including DHS, ICE, and DoD. Thiel backed J.D. Vance’s Senate campaign. Section 224’s “data fusion” and AI integration provisions directly expand the market for Palantir-type products within the U.S.-Israeli defense framework.
Larry Ellison — Oracle chairman, co-founder of the Stargate Project ($500B AI data center buildout), documented Republican donor. Oracle holds significant Israeli government contracts. Trump announced Stargate from the White House flanked by Ellison. The geography of Stargate construction tracks closely with the congressional districts of HASC members drafting and voting on Section 224.
The connection between these individuals and Section 224 is not a conspiracy. It is structural alignment — what political scientists call “structural corruption,” as distinct from transactional bribery. Each element is documented separately. Each is legal. The aggregate effect is a legislative environment in which the officials who write defense bills have financial relationships with the companies and political networks that benefit from those bills, and in which the electoral survival of those officials depends on the continued support of those same networks. LI
There is one additional allegiance that requires naming directly, because it is almost entirely absent from mainstream coverage: the evangelical theological engine. The largest pro-Israel lobbying organization in the United States is not AIPAC. It is Christians United for Israel — CUFI — with over 7 million members, composed almost entirely of American Evangelical Christians whose theology holds that Jewish return to the Biblical land of Israel is a prerequisite for the Second Coming of Christ. CUFI’s political influence on Republican members of Congress — particularly in Southern and Midwestern districts — is documented by political scientists and is a significant factor in the structural bipartisan consensus on unconditional Israel support that enabled Section 224 to be written without a public hearing. This is not speculation. It is documented. C1
The Holy Lobbies series documented the intersection of evangelical political organizing, AIPAC electoral targeting, and the theological basis for Evangelical support of Israeli policy. The Grand Architecture documented the financial allegiances of the billionaire donor class — Adelson, Thiel, Ellison — and their relationships to the current administration’s defense posture. Section 224 is the point at which all of these threads converge into a single legislative vehicle: theology, billionaire money, electoral capture, and defense industry profit, assembled into 12 pages of NDAA text that most Americans will never read.
The System: How It All Connects
What has been documented across the first five chapters of this installment is not five separate stories. It is one system, described from five angles. The mechanism is worth stating plainly. LI
Project Nimbus established that American technology companies would build military-grade AI infrastructure for Israel, governed by Israeli law, shielded from international legal accountability, and contracted in ways that overrode the companies’ own stated ethical commitments. Section 224 takes that model and moves it into the U.S. defense acquisition pipeline, fusing the two nations’ militaries at a level of integration that no other U.S. ally has been offered. The $77.7 billion domestic data center buildout provides the physical infrastructure in which this fused system will operate — with co-production facilities in congressional districts that now have constituent jobs reasons to defend the relationship regardless of its policy implications. The comprehensive money map — $3.8 billion in annual aid, $26 billion in emergency supplementals, $1.2 billion in cloud contracts, $1.4 billion in private donations, $1.7 billion in bonds, $126.9 million in electoral spending — ensures that the financial relationships flowing through this system are so deeply embedded that no single official can unravel them without triggering a coordinated response from donors, lobbies, voters, and contractors simultaneously. And the allegiance layer — Adelson, Thiel, Ellison, AIPAC, CUFI, the bipartisan HASC leadership — ensures that the political will to unravel any of it will face the most sophisticated and well-funded opposition in the history of American single-issue politics.
This is what structural corruption looks like. It does not require a bribe. It does not require a conspiracy. It requires only that every incentive in the system points in the same direction — and that the people positioned to redirect it face prohibitive costs for trying. LI
The system does not need anyone to be evil. It only needs everyone to be self-interested. And it was built, piece by piece, to make self-interest and the continuation of this relationship indistinguishable from each other.
What You Can Do
- Call your representatives on the NDAA. Section 224 must pass the full House Armed Services Committee, then the full House, then the Senate before becoming law. The window is open. Find your member at house.gov and call — not email. Congressional offices track call volume. Tell them to oppose Section 224 of the FY2027 NDAA or to demand a public hearing before any vote.
- Name it accurately when you share it. This is not an “aid bill.” It is a military merger provision buried in a defense authorization act. Precise language matters because imprecise language is how provisions like this survive without opposition.
- Follow the money publicly. OpenSecrets.org and FEC.gov are public. Look up your representative. Look up their AIPAC-related contributions. Make that public record visible in your networks.
- Ask your state and local governments about Israel bonds. If your state or municipality has purchased Israel bonds using public funds, that is a matter of public record. Ask for it. Demand a public vote before any future purchases.
- Support journalists covering this. Responsible Statecraft, The Intercept, +972 Magazine, and The Guardian have published the primary-source reporting this analysis draws from. They are operating under significant financial pressure. Readers are their survival mechanism.
- Demand FARA compliance. AIPAC has never registered as a foreign agent under the Foreign Agents Registration Act. Contact the DOJ’s FARA Unit and your congressional representatives to ask why the most powerful single-issue foreign-policy lobby in American history does not register as one.
This is the inaugural installment of The Illuminated Record, a new series from The Quanfinity Project dedicated to underreported civic stories with serious implications for American life. Evidence tier designations follow QP’s six-tier confidence system: C1 Documented · C2 Corroborated · LI Logical Inference · OA Open Architecture · C3 Unverified Claim · UNVERIFIED Pending. All financial figures are from public record including FEC filings, Congressional Research Service reports, the Israeli Ministry of Diaspora Affairs, ConstructConnect, and corporate earnings disclosures. Project Nimbus documentation sourced from +972 Magazine, Local Call, The Guardian, and The Intercept investigations, 2025–2026. Cross-references to prior QP series are noted throughout and available in full from The Quanfinity Project archive. This piece does not constitute legal advice. Pre-publication legal review recommended before commercial distribution.