The Integration Architecture : Post VIII — The Wiring

The Integration Architecture Post VIII of VIII  ·  Forensic System Architecture

The Wiring

Seven posts have traced seven separate mechanisms. Read together, they describe a single circuit — one that does not run in the direction the conventional framing of this relationship assumes

---

---

Randy Gipe 珞· Claude / Anthropic  ·  2026  ·  Trium Publishing House Limited  ·  Forensic System Architecture

Every gear in this diagram has now been opened up across seven posts. What remains is to look at the whole machine running at once — not as two separate systems, statutory and institutional, but as a single circuit with a single direction of current.

Layer I  ·  Source

---

This series began with a question Randy Gipe raised plainly: does the conventional framing — Israel as a forward operating base of the United States, a forward-deployed node executing American strategy in a region Washington cannot directly garrison — actually match what is happening in the legislative record of 2026? Seven posts of forensic examination later, the documentary answer is not ambiguous. The architecture examined in this series does not describe a base receiving direction from headquarters. It describes a senior structural partner writing its own permanence into the host nation's statutory machinery, using mechanisms that this series has now traced in granular, sourced, repeatedly cross-verified detail.

The clearest single piece of evidence for this is not analytical inference. It is the documentary record itself: on June 1, 2026, the head of a foreign government wrote a letter to a member of the United States Congress, thanking him for advancing legislation that would integrate that government's military and intelligence apparatus with America's own — and independent reporting characterized the effect of that legislation as transforming the foreign government from an aid recipient into a full member of the U.S. defense and intelligence apparatus. A forward operating base does not receive a thank-you letter from its garrison commander for the privilege of being more deeply wired into headquarters. It is wired in because headquarters decided to wire it in. What this series has documented is the reverse current.

The Complete Circuit — Seven Mechanisms, One Direction of Current

Each node below is a post in this series. Read individually, each documents one mechanism. Read in sequence, they form a closed loop: a mandate that cannot be quietly reversed, enforced by an office with no sunset, riding a vehicle built for exactly this purpose, proceeding regardless of the government's own threat assessment, unconditioned by the one law built to condition it, carrying documented historical risk of further redirection, and structured unlike every comparable relationship Congress has built in the same period.

1

The Mandate

Section 622 converts a discretionary intelligence relationship into a standing legal obligation, with reduction permitted only after a disclosed, congressionally-reviewed justification. The flow of secrets is locked.

2

The Office

Section 224 creates a permanent Pentagon Executive Agent — now renumbered Section 219 in the House, Section 1217 in the Senate — whose sole function is synchronizing defense industrial integration, timed to outlast the FY2028 MOU renegotiation. The supply chain is locked.

3

The Vehicle

Both provisions ride inside must-pass authorization bills too large and too politically costly to fail, insulating them from the kind of standalone scrutiny their structural permanence would otherwise invite. The scale itself is the shield.

4

The Designation

The DIA's own internal assessment raised Israel's counterintelligence threat designation to "critical" in the same weeks Congress mandated deeper sharing — two channels of the same government reaching opposite conclusions, with no statutory mechanism connecting them. The warning has nowhere to plug in.

5

The Omission

The Leahy Law's vetting forum for Israel has identified zero ineligible units in over four years, against eleven for Ukraine, nine for Jordan, three for Egypt — a documented procedural asymmetry, not a textual exemption. The conditioning mechanism does not condition.

6

The Leverage

A documented historical record of onward technology and intelligence transfer — Pollard, China, apartheid South Africa — establishes the actual risk Section 622 forecloses the president's ability to manage, at the same moment the Israeli prime minister's own letter describes the goal as full apparatus membership. The tool for managing risk is removed precisely as the risk is named.

7

The Precedent

Congress wrote a five-year sunset and war-resolution certification into Ukraine's comparable cooperation framework in the same legislative period. It wrote no equivalent limit into Section 622. The permanence is a choice, demonstrably available to be made otherwise.

Seven mechanisms, examined separately, could each be argued away as routine. Read as one circuit, they describe something routine legislative practice does not produce by accident: a closed loop with no exit, built in the specific window before the one moment — the 2028 MOU expiration — that would have forced an open one.

The Integration Architecture  ·  Series Analysis

Layer II  ·  Conduit

---

One mechanism this series has not yet isolated on its own deserves naming directly in this closing post, because it is the cleanest single illustration of the circuit's asymmetric design: reciprocity itself. Military.com's reporting on Section 622 notes a detail with sharp implications — neither Section 622 nor Section 224 requires Israel to provide reciprocal access to technology, software, or source code as a condition of the expanded cooperation they mandate. This omission is not abstract. It has a documented history: Israel negotiated unique accommodations within the F-35 program unavailable to other foreign operators of the aircraft, and separately, after the US Army purchased Iron Dome batteries for its own air defense architecture, Army officials repeatedly requested the system's source code in order to integrate the batteries into broader US systems — requests the reporting characterizes as a recurring point of friction, not a settled matter.

The Reciprocity Gap — What the Mandate Does Not Require

US obligation

Statutorily mandated to expand: intelligence across nearly the full range of Middle East subjects, defense technology cooperation across AI, quantum, autonomous systems, and directed energy, and industrial co-production access. Codified, permanent, enforceable.

Israeli obligation

No statutory requirement for reciprocal access to Israeli source code, proprietary technology, or intelligence product as a condition of receiving the expanded American access. Voluntary, at Israel's discretion, with a documented history — the Iron Dome source code dispute — of that discretion being exercised to withhold.

What this means structurally

A genuine bilateral integration architecture would condition US access on equivalent Israeli access, closing the loop in both directions. The actual statutory language closes the loop in one direction only — which is the single clearest piece of evidence, independent of any of this series' other findings, that the relationship being built is not the symmetrical "full member of the apparatus" partnership its proponents describe, but something with a documented directional bias built into its own text.

Layer III  ·  Conversion

---

What this entire series converts, at the level of political function, is the comfortable ambiguity surrounding "the US-Israel relationship" into seven specific, documented, independently verifiable mechanisms — each traceable to bill text, government audit, official statement, or named source. This is the conversion FSA methodology exists to perform: replacing a debate conducted in the register of loyalty, alliance, and accusation with a debate conducted in the register of statutory structure, procedural mechanism, and documentary comparison. None of this series' seven posts required speculation about motive. Each rested on what the bills actually say, what the GAO actually found, what officials actually stated on the record, and what Congress actually chose to write differently for comparable relationships in the same period.

$750M

AIPAC's own published figure for total US-Israel cooperative program funding in the FY2027 NDAA — a $65 million increase over the prior year, publicly framed by the organization as a core achievement

AIPAC's own published memo on the FY2027 NDAA states the bill includes $750 million for U.S.-Israel cooperative programs, itemized as $500 million for missile defense cooperation, $100 million for counter-unmanned systems, $100 million for subterranean operations cooperation, and $50 million for emerging technologies cooperation — alongside the Section 224/219 Defense Technology Cooperation Initiative examined throughout this series. This is presented here not as evidence of wrongdoing but as the clearest available admission, from the institution most directly engaged in advancing this legislation, of the architecture's scale and the value its proponents place on having achieved it.

Layer IV  ·  Insulation

---

The architecture's overall insulation is the sum of every insulation mechanism this series has documented individually, and naming that sum is this closing post's final task. The vehicle insulates the provisions from standalone scrutiny. The voice vote insulates the floor fight from an attributable record. The closed-session markup insulates the committee process from public observation. The fifteen-day disclosure clause insulates the mandate from quiet reversal while appearing to permit it. The Leahy vetting forum's unique procedural architecture insulates the human-rights conditioning mechanism from ever actually triggering. The rhetorical framing around loyalty and security insulates the leverage argument from being raised without cost. And the absence of any other single body of expertise that tracks both the Israel-specific and the Ukraine-specific legislative ecosystems insulates the precedent comparison from ever being made by anyone with institutional standing to make it loudly.

Institutional Layer — What Happens Next

As of this writing, both provisions remain in motion: Section 622 advancing through the Senate Intelligence Committee process, Section 224 (now Section 219 in the House, Section 1217 in the Senate text) having survived a House Armed Services Committee floor amendment by voice vote and continuing toward full House passage, conference reconciliation with the Senate, and final enactment. This series does not predict the outcome. The Arab Center's own analysis notes a genuine point of political uncertainty this series has not previously emphasized: Republicans could lose at least one chamber of Congress in the November 2026 midterms, and if that happens, passing legislation of this kind could become considerably harder — which is precisely why, per that same analysis, the bill's most committed proponents are working to seize the current window before it closes. Readers tracking this story should consult congress.gov directly for the bills' current status, as the specific section numbers, language, and disposition described across this series will likely continue to shift through conference.

Series Closing Statement

The question this series set out to answer was whether Israel functions as a forward operating base of the United States, or something structurally different. The documentary record assembled across these eight posts answers it without requiring this series to take a side in the underlying political debate over the merits of the relationship itself.

A forward operating base does not write its own permanence into the host nation's statute. It does not receive a thank-you letter from the host's own legislators for the privilege of deeper integration. It does not negotiate one-directional access while the host's reciprocal requests go unmet for years. It does not survive a documented "critical" threat designation from the host's own intelligence services without the relationship's legislative momentum so much as pausing.

What the record shows instead is a senior structural partner locking permanent leverage into the host nation's own machinery — not through conquest, not through treaty, but through the most American of mechanisms: a provision, a markup, a vehicle, a vote. Sub Verbis, Vera. Beneath the words, the truth. The words, in this case, were public the entire time.

FSA Wall — Post VIII

This closing post synthesizes findings documented across Posts I through VII of this series, with full sourcing for each individual claim available in the corresponding post's FSA Wall. The reciprocity gap analysis — the absence of a requirement for reciprocal Israeli access to source code or proprietary technology, and the specific F-35 accommodation and Iron Dome source code dispute examples — is drawn from Military.com's "Section 622 Amendment Makes Israel Intelligence Sharing Harder to Reduce." The $750 million NDAA funding figure and its itemization is drawn directly from AIPAC's own published memo, "America & Israel: Defense & the NDAA," available at aipac.org. The current section renumbering (Section 224 to Section 219 in the House text, Section 1217 in the Senate text) is documented in the Quincy Institute's "Cooperation without Oversight" analysis and the Wikipedia entry for the United States-Israel FUTURES Act, both of which note this renumbering is a product of ongoing House and Senate editing and may continue to change. The Arab Center's analysis of the November 2026 midterm timing pressure is drawn from "Section 224: US-Israel Defense Integration Beyond Military Aid," cited previously in Post II. This series, in its entirety, constitutes analysis of pending, actively moving legislation as of June 2026; section numbers, specific language, and the ultimate fate of both provisions may change substantially through conference and final passage. Readers are strongly encouraged to consult congress.gov directly for current, authoritative bill text and status before treating any specific provision described across these eight posts as settled law.

The Integration Architecture  ·  Series Navigation

Post IThe Mandate

Post IIThe Office

Post IIIThe Vehicle

Post IVThe Designation

Post VThe Omission

Post VIThe Leverage

Post VIIThe Precedent

Post VIIIThe Wiring

The Integration Architecture : Post VII — The Precedent

The Integration Architecture Post VII of VIII  ·  Forensic System Architecture

The Precedent

Congress writes notification and sunset clauses into security legislation constantly. The question this post answers is not whether Section 622's structure is unusual in form — it is whether its specific combination of permanence, scope, and absence of an exit ramp has any equal among the other relationships it superficially resembles

---

---

Randy Gipe · Claude / Anthropic  ·  2026  ·  Trium Publishing House Limited  ·  Forensic System Architecture

Every gear in this diagram has an equivalent in some other US security relationship — a notification requirement here, a co-production agreement there. This post is the only one that places those equivalents directly beside Section 622's language to see whether the gears actually match.

Layer I  ·  Source

---

Congress was, in the same general legislative period as Sections 622 and 224, actively writing comparable-sounding provisions for other security partners — which makes this the right moment to ask the comparative question directly rather than take on faith that Israel's arrangement is unique. The clearest test case is Ukraine. S.2592, the Supporting Ukraine Act of 2025, contains its own trilateral cooperation initiative — Section 301, covering unmanned air, marine, and underwater defense systems with Ukraine and Taiwan — built with the same general drafting toolkit Congress uses across these bills: a notification requirement to a named set of committees, a defined scope of cooperation, and language governing what happens if support is paused.

The architecture looks similar on its face. It is, on direct textual comparison, structured almost as a mirror image.

Same Drafting Toolkit, Opposite Default — Section 622 vs. S.2592 Section 301

Both clauses govern notification before a change in support to a security partner. Read them side by side and the structural difference is not subtle: one assumes permanence and treats reduction as the event requiring justification. The other assumes finitude and builds its own end into the statute.

Sec. 622 — Israel (IAA FY2027)

"...shall expand and enhance intelligence sharing with the Government of Israel...

No suspension, reduction, or limitation of sharing under this section shall occur except on the basis of a specific and identifiable national security concern...

[no sunset provision]
[no certification-based termination mechanism]"

Default posture: permanent expansion. Reduction is the exception requiring a triggering justification. The statute contains no built-in mechanism for its own conclusion.

Sec. 301 — Ukraine/Taiwan (S.2592)

"...Trilateral cooperation initiative with Ukraine and Taiwan...

Not later than 10 days before any pause in providing the support... the Secretary of Defense shall notify [named committees]... including a justification for such pause.

(d) SUNSET.—This section shall cease to have effect [5 years after enactment], or upon certification that hostilities have ceased and [conditions met]."

Default posture: time-limited, condition-bound. The cooperation has a built-in expiration tied either to a fixed clock or to the resolution of the conflict that justified it in the first place.

Both clauses require the executive to notify Congress before changing course. Only one of them tells Congress, in the same breath, exactly when the arrangement is supposed to end.

The Integration Architecture  ·  Series Analysis

Layer II  ·  Conduit

---

The comparison is a conduit for a broader point about how Congress treats finite versus open-ended security relationships, and it cuts in a direction worth sitting with rather than smoothing over: Ukraine is a nation at active war, fighting for its survival against an ongoing invasion, and Congress still built a five-year sunset and a war-ending certification trigger into its cooperation framework. Taiwan, folded into the same Ukraine bill's trilateral provision, exists under the much older and more deliberately ambiguous Taiwan Relations Act of 1979 — a framework explicitly designed, as Just Security's analysis notes, to provide defense support without a formal treaty commitment, precisely because Congress in 1979 wanted strategic flexibility rather than a permanent guarantee.

Section 622, by contrast, governs a relationship with a state not engaged in an existential war for its own territory in the way Ukraine is, and does so with language that contains no comparable temporal limit. The drafting choice is the data point. Congress had, in active concurrent use during the same legislative season, the tools to write a sunset clause, a certification-based termination trigger, and a defined conflict-resolution endpoint into a security cooperation statute. It used those tools for Ukraine. It did not use them for Israel.

Three Comparable Relationships, Three Different Architectures

Ukraine (S.2592)

Time-bound and condition-bound: a five-year statutory sunset, or earlier termination upon presidential certification that hostilities have ended. The cooperation is explicitly tied to an emergency — the active Russian invasion — and is designed to expire when the emergency does, regardless of which administration is in office when that happens.

Taiwan (TRA 1979)

Deliberately ambiguous by design, not absent: the Taiwan Relations Act was constructed specifically to avoid the kind of formal treaty commitment that would constrain executive flexibility, precisely because Congress in 1979 wanted to preserve the option to recalibrate the relationship as cross-strait dynamics changed. Ambiguity, in this case, was the chosen mechanism for preserving future discretion — the opposite design goal from Section 622's mandate language.

Israel (Sec. 622 / 224)

No sunset, no certification-based termination, no tie to an active, resolvable conflict whose end would naturally close the statute. The mandate's only exit is the fifteen-day disclosure requirement examined in Post I — a procedural hurdle, not a structural endpoint. Among the three relationships compared here, it is the only one built without any future moment at which the law itself contemplates its own conclusion.

Layer III  ·  Conversion

---

What this comparison converts, at the level of political function, is the claim that Section 622's structure is simply standard congressional practice for security partners into a claim that requires actual evidence — and the evidence, on direct comparison, does not support it. Congress retained sunset and certification language even for a wartime ally facing an active existential invasion. It declined to use equivalent language for a security partner not in that position. The absence of a sunset clause in Section 622 is not an oversight or a drafting default. Given that Congress demonstrably had the relevant clause language in active use in the same legislative period, its absence here is itself a decision — one this series' earlier posts on the vehicle and the institutional capture layer have already supplied a mechanism for explaining.

5 years vs. indefinite

The sunset Congress wrote for Ukraine's trilateral cooperation initiative, compared to the absence of any sunset in Section 622

This is not a claim that Ukraine's security relationship with the United States is more or less important, more or less deserving, or more or less at risk than Israel's. It is a narrower and more precise claim: when Congress wrote security cooperation language for Ukraine in the same general period, it built in a finite horizon tied to the resolution of an active war. When it wrote security cooperation language for Israel, it did not build in an equivalent horizon, despite Israel also being, at the time of this writing, an active belligerent in a regional conflict. The asymmetry in drafting choice — not the underlying merits of either relationship — is the forensic finding this post documents.

Layer IV  ·  Insulation

---

The precedent argument's insulation is the same vehicle and rhetorical insulation traced in Posts III and VI, applied here to a specific comparative claim: it is difficult to raise the Ukraine-Israel drafting asymmetry on the floor of Congress without the comparison itself being read as a relative ranking of the two countries' worthiness for US support, rather than what it actually is — a narrow observation about statutory drafting technique. The insulation works by making the comparison itself appear improper to raise, regardless of how carefully it is framed, because any direct juxtaposition of how Congress treats different countries' security relationships risks being received as a statement about which ally matters more.

Institutional Layer — Why This Comparison Rarely Surfaces in Debate

None of the reporting and analysis this series has drawn on across its first six posts — Responsible Statecraft, the Quincy Institute, the Arab Center, Military.com — makes this specific Ukraine/Israel clause-language comparison directly. That absence is itself informative. The comparison requires placing two bills that move through entirely separate committees, advocacy ecosystems, and media narratives — Ukraine aid and Israel aid occupy almost entirely distinct political conversations in Washington, despite both ultimately running through the same basic congressional drafting toolkit. The institutional infrastructure that tracks and contests Section 622 specifically is not the same infrastructure that tracks Ukraine assistance, and the absence of cross-referencing between those two advocacy and oversight ecosystems is part of what allows the drafting asymmetry documented in this post to pass without the comparative scrutiny it would receive if a single body of expertise were responsible for reviewing both.

FSA Wall — Post VII

The text of Section 301 of S.2592, the Supporting Ukraine Act of 2025, including its ten-day pause-notification requirement and its five-year sunset and certification-based termination provisions, is drawn directly from the bill text published at congress.gov (119th Congress, S.2592). The Taiwan Relations Act of 1979's design as a deliberate alternative to a formal defense treaty, intended to preserve executive and congressional flexibility regarding US-Taiwan security cooperation, is documented in "A Security Guarantee for Ukraine? Look to the Taiwan Relations Act," published by Just Security. The Section 622 statute insert referenced in this post's comparison is the same forensic reconstruction presented in Post I of this series, sourced to bill summaries and committee reporting on S.4615; readers should consult congress.gov directly for authoritative current bill text for both S.2592 and S.4615. This post's central comparative claim — that Congress used sunset and certification language for Ukraine's cooperation framework in the same general period it declined to use equivalent language for Israel's — is an original analytical observation of this series, constructed by direct comparison of the two bills' published text rather than drawn from any single cited secondary source; readers are encouraged to verify the comparison independently against the primary bill texts. This post does not take a position on the relative merits of US support for Ukraine or Israel; its claim is limited to the documented asymmetry in statutory drafting technique between the two cases.

The Integration Architecture  ·  Series Navigation

Post IThe Mandate

Post IIThe Office

Post IIIThe Vehicle

Post IVThe Designation

Post VThe Omission

Post VIThe Leverage

Post VIIThe Precedent

Post VIIIThe Wiring

The Integration Architecture : Post VI — The Leverage

The Integration Architecture Post VI of VIII  ·  Forensic System Architecture

The Leverage

Once intelligence is shared, the sharing government loses control over where it travels next. This is not a hypothetical risk attached to Section 622. It is a documented pattern with a forty-year paper trail — and a sitting US prime minister's own letter now describes the goal in writing

---

---

Randy Gipe · Claude / Anthropic  ·  2026  ·  Trium Publishing House Limited  ·  Forensic System Architecture

The "Intelligence Sharing Protocols" gear in the blueprint half assumes a closed loop: information flows from the US intelligence apparatus to Israel and stays inside that relationship. This post traces what happens when the loop is not closed — where the documented record shows it has not been, historically, and what a permanent statutory mandate does to the leverage the US previously held over that fact.

Layer I  ·  Source

---

Paul R. Pillar, a former senior CIA analyst now a non-resident fellow at Georgetown's Center for Security Studies and the Quincy Institute, made the structural point as directly as it can be made in his analysis of Section 622: any sensitive information shared with Israel carries a documented risk of onward transfer to other states, including US adversaries — a risk Pillar describes as resting on a long record, not a speculative one. He names two specific historical instances: Israel's transfer of US-origin military technology to China, and the Pollard case, in which Israel is widely understood to have passed at least some of the classified material Jonathan Pollard stole from US Navy intelligence onward to the Soviet Union — reportedly as part of an exchange tied to Soviet Jewish emigration.

Pillar's analysis extends the pattern further back, to a relationship few defenders of the current legislation would want surfaced in the same sentence: Israel's military and technical cooperation with apartheid-era South Africa, a partnership that extended, by Pillar's account, into joint nuclear weapons development. The pattern Pillar identifies is not that Israel is uniquely untrustworthy among US partners. It is that Israel's diplomatic strategy has long depended on building relationships with as many states as possible, including ones the United States treats as adversaries or pariahs — and that US intelligence, once shared, becomes a valuable and available form of currency for exactly that strategy.

The Documented Record — Four Instances of Onward Transfer or Third-Party Risk

This is not a list of allegations constructed for this post. Each entry below is drawn from the historical record as characterized in Paul Pillar's published analysis for the Quincy Institute and Responsible Statecraft, supplemented by independently reported current events. The purpose is to establish a base rate — what has actually happened before — against which Section 622's "shall expand and enhance" mandate can be assessed.

1970s–80s

South Africa. Israeli military and technical cooperation with the apartheid government extended, by Pillar's account, into joint development work on nuclear weapons capability — cooperation with a state under international arms embargo and global pariah status, undertaken despite that status rather than because of any alignment with US interests. The case establishes that Israeli strategic cooperation has historically not been bounded by US foreign policy preferences when Israel's own perceived interests pointed elsewhere.

1985

The Pollard case. Jonathan Pollard, a US Navy intelligence analyst, was convicted of spying for Israel after passing large volumes of classified material. Pillar's analysis states it as established that Israel probably passed some of the secrets Pollard purloined to the USSR, reportedly in exchange for Moscow easing restrictions on Soviet Jewish emigration. This is the most direct documented instance of US intelligence, obtained by Israel, being redirected to a Cold War adversary for Israel's own diplomatic purposes — purposes unrelated to, and arguably contrary to, US strategic interests at the time.

1990s–2000s

China technology transfer. Pillar's analysis identifies Israel's sharing of US-origin military technology with China as a documented and recurring issue, distinct from any single incident — a pattern significant enough that it has shaped US export control posture toward joint US-Israeli defense programs for decades. China is named explicitly, by Pillar, as one of the present-day "partners or potential partners" to whom shared US intelligence would be attractive as trading material under the new mandate.

2026

The cybersecurity exclusion. In January 2026, Beijing ordered Chinese firms to stop using cybersecurity software from a list of American and Israeli companies — including Check Point, CyberArk, Orca Security, and Cato Networks — citing concern that the software could function as a backdoor for foreign intelligence services. China's own stated rationale for excluding Israeli firms is structurally identical to the concern this post raises about Section 622: that deep technical integration with an allied intelligence-adjacent ecosystem creates a channel that does not stay contained within the relationship it was built for.

The mandated intelligence sharing ties the president's hands and prevents any administration from using management of the liaison relationship as leverage to deter destructive conduct — at precisely the historical moment the documented record shows that leverage has been most necessary.

The Integration Architecture  ·  Series Analysis

Layer II  ·  Conduit

---

The leverage problem operates as a conduit in a specific direction this series has not yet fully named: it is not merely that intelligence might leak. It is that the management of the sharing relationship — the ability to slow, condition, or threaten to reduce sharing — has historically functioned as the primary tool available to a US administration for influencing Israeli conduct in cases where direct diplomatic pressure has failed. Section 622's reduction-limitation clause, examined in Post I, does not merely create a disclosure cost for using that tool. Pillar's analysis describes it more starkly: it removes the tool's deterrent function almost entirely, because using it now requires triggering a public, congressionally-reviewed process that the Israel lobby would, in his words, quickly depict as a question of being for or against the security of Israel rather than a judgment about a specific Israeli action.

What the Mandate Removes From the President's Toolkit

Quiet calibration

Historically, a president could slow the pace or narrow the scope of intelligence sharing without a public announcement, using the adjustment itself as a private signal of displeasure. Section 622's fifteen-day disclosure requirement converts every calibration into a public political event, removing the option to send that signal quietly.

Conduct-based conditioning

The leverage Pillar describes losing is specifically conduct-based: the ability to make continued or expanded sharing contingent on Israeli behavior the US considers destructive to regional security or its own interests. A mandate to "expand and enhance" sharing, with reduction permitted only for a "specific and identifiable national security concern," does not contemplate Israeli conduct as a valid basis for adjustment — the clause is written around threats to the United States, not around how Israel uses what it receives.

Third-party deterrence

If Israel understands that continued or expanded sharing is now a statutory entitlement rather than a relationship the US actively manages and can withdraw, the historical deterrent against onward transfer — the risk that the US might notice and respond by curtailing the relationship — weakens correspondingly. The documented cases in the ledger above occurred under a discretionary relationship that still, in theory, carried that risk. A mandated relationship carries it less.

Layer III  ·  Conversion

---

What this post's evidence converts, at the level of political function, is a documented historical risk into an admitted current goal — and the conversion did not require this series to make an inferential leap. On June 1, 2026, Prime Minister Benjamin Netanyahu wrote a letter to Representative Marlin Stutzman, thanking him for endorsing what Netanyahu's own letter described as a "new framework of joint defense cooperation, codevelopment, coproduction and mutual investment" spanning missile defense, artificial intelligence, unmanned systems, cybersecurity, and next-generation military platforms. Responsible Statecraft characterized the letter as an explicit endorsement of Section 224, writing that the provision "essentially transforms Israel from a top U.S. aid recipient to a full member of the U.S. defense and intelligence apparatus."

A full member of the apparatus is not the same legal or strategic category as an ally receiving aid under conditions the donor sets and can revoke. Membership implies standing, access, and a presumption of shared purpose that the historical record in this post's ledger does not uniformly support. CAIR's statement following the House Armed Services Committee's passage of Section 224 used almost identical language independently: the provision represents "a dangerous attempt to permanently fuse elements of the American and Israeli military intelligence and technology in ways that could outlast any single administration, Congress, or political moment." Eli Clifton and Ian Lustick, writing in The Guardian the same week, called it bluntly "a trap being set by Israel and its lobby to bind our country to a state that, for all its past promise, has gone rogue."

"A Full Member"

Responsible Statecraft's characterization of what Section 224 makes Israel within the US defense and intelligence apparatus — drawn directly from Netanyahu's own letter endorsing the provision

This is not this series' framing of the provision's effect. It is the framing offered by the head of the Israeli government himself, in a letter thanking a member of Congress for supporting it, as characterized by independent reporting. The series' inversion thesis — that the relationship functions less like a forward operating base of the United States and more like a senior structural partner embedding leverage into the host nation's own statutory architecture — finds its most direct documentary support not in inference, but in the stated position of the official whose government stands to benefit most directly from the architecture this series has traced.

Layer IV  ·  Insulation

---

The leverage argument's insulation is rhetorical rather than procedural, and Pillar names the mechanism precisely: any attempt to raise the third-party transfer risk in the legislative debate gets quickly depicted as a question of loyalty to Israel's security rather than a sober assessment of documented historical risk. This framing does not need to win the substantive argument. It only needs to make raising the argument costly enough, in domestic political terms, that fewer members of Congress are willing to do it — which is functionally identical to the insulation mechanisms this series has traced in the legislative vehicle and the institutional capture layers, now operating at the level of permissible public debate rather than committee procedure.

Institutional Layer — The Live Floor Fight

On June 4, 2026, Representative Ro Khanna introduced the floor amendment to strip Section 224, co-sponsored by Representative Sara Jacobs. Khanna's stated argument was explicitly about leverage and sovereignty, not partisan position: "Everyone in America... says that we need to tell Netanyahu that America calls the shots, not the prime minister of any other country." The amendment was opposed inside his own party by Representative Adam Smith, who argued the war context — stating that "Mr. Netanyahu insisted on this war with Iran that has strengthened Iran and weakened our position" — cut against, not for, further integration. The amendment failed by voice vote. The fight over Section 224 is not, on this evidence, a clean partisan divide — it is a fight over whether conduct-based leverage should exist at all, with both parties internally split, and the institutional and procedural advantages this series has documented determining the outcome regardless of where individual members actually stood.

FSA Wall — Post VI

The third-party transfer risk analysis in this post is drawn primarily from Paul R. Pillar's "Senate Wants to Force US to Share Sensitive Intel with Israel," published by Responsible Statecraft (June 10, 2026); Pillar is a former senior CIA analyst, non-resident senior fellow at Georgetown University's Center for Security Studies, and non-resident fellow at the Quincy Institute for Responsible Statecraft, and his characterizations of the Pollard case, the South Africa relationship, and the China technology transfer pattern are presented in this post as his published analytical assessment, not as independently adjudicated historical fact, though the Pollard case's broad outline is a matter of public record from his federal espionage conviction. The January 2026 Chinese directive against US and Israeli cybersecurity software is documented in reporting from Fox Business, Tom's Hardware, China Global South, and The Cradle, all citing Reuters' original sourcing. Netanyahu's June 1, 2026 letter to Rep. Marlin Stutzman, the Responsible Statecraft characterization of Section 224 as making Israel "a full member of the U.S. defense and intelligence apparatus," CAIR's June 5 statement, the ADC's statement, Eli Clifton and Ian Lustick's June 5 Guardian opinion piece, Ro Khanna's June 4 floor amendment and quoted statement, Sara Jacobs's co-sponsorship, and Adam Smith's opposing statement are all documented in the Wikipedia entry for the "United States-Israel FUTURES Act," which compiles primary reporting and statements from these sources; readers seeking primary documents should consult the original statements and reporting cited therein. This post presents Pillar's risk assessment as one informed analyst's published view, grounded in a documented historical record, not as a settled prediction of what will occur under Section 622 specifically. The legislative developments described are current as of mid-June 2026 and may have changed by the time of reading; consult congress.gov for the bill's current status.

The Integration Architecture  ·  Series Navigation

Post IThe Mandate

Post IIThe Office

Post IIIThe Vehicle

Post IVThe Designation

Post VThe Omission

Post VIThe Leverage

Post VIIThe Precedent

Post VIIIThe Wiring

The Integration Architecture : Post V — The Omission

The Integration Architecture Post V of VIII  ·  Forensic System Architecture

The Omission

The law that conditions American security assistance on human rights compliance applies, on paper, to every recipient. In practice, it has identified eleven ineligible units in Ukraine, nine in Jordan, three in Egypt — and, after more than four years of a dedicated process built solely for this purpose, zero in Israel

---

---

Randy Gipe · Claude / Anthropic  ·  2026  ·  Trium Publishing House Limited  ·  Forensic System Architecture

The statutory layer of this diagram assumes uniform application — a law is a law, applied the same way to every recipient the appropriations process touches. This post examines the gap between that assumption and the documented operating procedure of the single conditioning mechanism Congress actually built: the Leahy Law, and the unique forum constructed to apply it to one country.

Layer I  ·  Source

---

The Leahy Laws, enacted in 1997 and made permanent in 2008, are the primary statutory mechanism by which the United States is supposed to condition security assistance on human rights compliance. The standard is deliberately set low: the Department of State and Department of Defense must withhold assistance from any foreign security force unit where there is credible information — not proof beyond a reasonable doubt, not even clear and convincing evidence — that the unit has committed a gross violation of human rights, defined to include torture, extrajudicial killing, enforced disappearance, and rape under color of law. The law applies, in principle, to every recipient of US-appropriated security assistance. It is the closest thing American law has to a universal conditioning mechanism on the kind of integration this series has been tracing.

In practice, the law's implementation is not universal. Since 2021, the State Department has built dedicated, ongoing Leahy vetting forum processes for exactly four countries: Israel, Ukraine, Egypt, and Jordan. A Government Accountability Office report, the first to provide public transparency on how these four processes actually operate, found that as of February 2025 the Ukraine forum had identified eleven ineligible units, the Jordan forum nine, and the Egypt forum three. The Israel forum — called the ILVF, the Israel Leahy Vetting Forum — had identified zero, in a process that had then been operating for more than four years.

One Law, Two Procedures — Leahy Vetting as Documented by GAO

The Israel Leahy Vetting Forum and the equivalent forums for Ukraine, Jordan, and Egypt operate under the same underlying statute. They do not operate under the same procedure. The differences, documented by the GAO and reported by Just Security based on direct former-official testimony, are structural — built into the standard operating procedures themselves, not incidental variation in enforcement.

Procedure Element

Israel (ILVF)

Ukraine / Jordan / Egypt

Decision authority

Rests with the Deputy Secretary of State — the SOPs require this specifically and exclusively for Israel. No other country in the world has its ineligibility determinations elevated to this level by standard procedure.

Made at the working level by career experts versed in the Leahy law and the specific country's security forces — the same level at which approximately 200,000 cases are vetted annually worldwide for every other recipient.

Foreign government input

ILVF SOPs require formal requests to the Government of Israel for information about allegations before any determination — again, true for no other country. The subject of the investigation is formally consulted before the investigation concludes.

No equivalent formal foreign-government consultation requirement built into the SOPs for the other three forums' working-level processes.

Process speed

Described by a former office director with direct ILVF experience as unique, complex, and time-consuming — requiring periodic in-person meetings at senior levels rather than the virtual expert-level review used elsewhere, slowing every stage.

Informal, conducted virtually at the expert and working level — and, in the former official's direct assessment, they work: they have produced agreed-upon lists of ineligible units.

Documented outcome

Zero ineligible units identified in over four years of operation, per the GAO's February 2025 findings — the only one of the four dedicated forums to produce this result.

Eleven units barred in Ukraine, nine in Jordan, three in Egypt — small numbers relative to the thousands of units former officials say are considered ineligible worldwide, but non-zero in every other case examined.

Political considerations are not supposed to be relevant to a Leahy law eligibility decision. A former senior State Department official with direct experience inside the process states plainly that, in actual practice, concern about criticism from the government of Israel functions as a factor anyway.

The Integration Architecture  ·  Series Analysis

Layer II  ·  Conduit

---

The omission operates as a conduit by removing the one mechanism that would otherwise create friction inside the architecture this series has traced — Section 622's mandate, Section 224's industrial integration, and the DIA's own threat designation all proceed through a system where the conditioning statute that exists to slow or stop assistance to abusive units has been built, by its own design documents, to almost never reach that conclusion for this particular recipient. The five-day, three-step Leahy review most countries' units receive runs through the Israel process as a months-long, multi-level escalation requiring the subject government's input before any unfavorable finding can be reached. The conduit is not the absence of a law. It is a law with two separate operating systems, one of which is engineered for a different outcome.

The 2024 case the GAO and Just Security both document illustrates exactly how the conduit functions in a live instance. Public reporting pressured the State Department, after several months of delay, to act on recommendations that five specific Israeli military units be subject to a Leahy ban. The eventual determination found that all five had been sufficiently held accountable for the underlying conduct, rendering them eligible — and the GAO's broader finding confirms this was not an isolated outcome but the pattern: in the entire history of the ILVF process, not a single Israeli unit has ever been formally identified as ineligible.

What the Comparison to Other Conditioned Relationships Shows

Ukraine, by contrast

Ukraine's security assistance, examined in Post I's framing of the original document under analysis, is conditioned on human rights compliance through a Leahy vetting forum that has produced eleven barred units — the highest count of the four dedicated forums. The same conditioning statute, applied to a country receiving assistance in the context of active war, produced findings of ineligibility. Israel's forum, also in the context of active and recent conflict, has produced none.

The national security exception

The Leahy Law allows the Secretary of State to determine that a government has taken "effective steps" to remediate a violation, rendering an otherwise-ineligible unit eligible again. This exception exists for every country and is not itself evidence of differential treatment — but the GAO's documentation that the exception's procedural gateway for Israel alone requires Deputy Secretary-level sign-off and prior consultation with the foreign government under investigation is the differential element, not the exception's mere existence.

FMS and DCS exclusion

The Leahy Laws do not apply at all to Foreign Military Sales or Direct Commercial Sales — only to assistance funded through US appropriations. A substantial share of US-Israel defense transactions occur through exactly these excluded channels, meaning the omission documented in this post sits on top of a separate, broader category of transactions the conditioning statute was never designed to reach in the first place.

Layer III  ·  Conversion

---

What the omission converts, at the level of political function, is a universal legal standard into a country-specific outcome — without ever amending the statute that establishes the standard. This is the conversion's defining feature and the reason it belongs in this series rather than in a separate critique of human rights policy generally: Congress did not need to write Israel an exemption from the Leahy Law. No legislative text says Israeli units are held to a different evidentiary standard. The conversion happens entirely at the level of standard operating procedure — internal State Department documents, never published, that route Israel's cases through a structurally slower, more senior, more foreign-government-consultative process than every other country's units pass through. The law on the books is identical. The machine built to execute it is not.

0 / 11 / 9 / 3

Ineligible units identified — Israel / Ukraine / Jordan / Egypt — as documented by GAO, February 2025

The Government Accountability Office's report represents the first public transparency into how the four dedicated Leahy vetting forums actually operate and what they have produced. The comparison is stark by the numbers alone, but Human Rights First's analysis adds an important caveat that this series should carry forward honestly: even the non-zero counts for Ukraine, Jordan, and Egypt are described by former State Department officials as a "shockingly low" fraction of the thousands of units believed to be considered ineligible worldwide, suggesting Leahy implementation has documented weaknesses across the board, not only with respect to Israel. What distinguishes the Israel case, per the GAO's own findings and the former official's direct account in Just Security, is not merely a low count but a documented, procedurally distinct pathway — built specifically for this one country — that has never once, in over four years, produced the outcome the statute exists to allow.

Layer IV  ·  Insulation

---

The omission's insulation is procedural opacity layered on top of an already-low public visibility standard. The Leahy Law has required public disclosure of barred units "to the maximum extent practicable" since 2011 — and the State Department has, to date, publicly named 113 units globally as barred. But the ILVF's standard operating procedures themselves have never been published; what is known about how the Israel forum actually functions comes not from any government disclosure but from a former senior State Department official's direct, named account, published through Just Security, describing a process he observed and worked within. The insulation here is not classification in the formal sense. It is the simple fact that almost no public reporting exists on internal SOPs for any of these forums — which means the procedural disparity documented in this post became visible to the public only because one former insider chose to describe it, and because the GAO happened to audit the broader Leahy vetting system closely enough to surface the outcome numbers.

Institutional Layer — Why the SOP Looks the Way It Does

The former official's account is direct on this point: he attributes the ILVF's unique structure not to a documented national-security rationale but to political considerations — specifically, concern among State Department personnel about the diplomatic and domestic political cost of a finding against Israel, a concern he states explicitly should not be relevant to a Leahy eligibility decision under the law's own terms but which, in his account, has functioned as a real factor regardless. This is the same institutional-capture dynamic this series has traced in the legislative process in Posts II and III, now visible inside the executive branch's implementation of existing law rather than in the writing of new statute. The mechanism is consistent across both domains: the formal rule stays uniform on paper, while the apparatus charged with applying it absorbs the political cost of differential treatment into its own internal design.

FSA Wall — Post V

The Leahy Law's statutory text and history are documented in the Congressional Research Service's "Global Human Rights: Security Forces Vetting ('Leahy Laws')" (congress.gov, IF10575) and in the Israel Policy Forum's "The Security Assistance Process: Explained," which provides the law's 1997 origin and 2008 permanence. The GAO's February 2025 findings on the four dedicated Leahy vetting forums — including the specific counts of eleven units barred in Ukraine, nine in Jordan, three in Egypt, and zero in Israel — are documented in GAO-25-107077, "Human Rights: State Can Improve Response to Allegations of Civilians Harmed," and are further analyzed in Human Rights First's "Transparency in the Leahy Laws: Who is Banned?" The detailed account of the Israel Leahy Vetting Forum's unique standard operating procedures — including Deputy Secretary-level decision authority, mandatory prior consultation with the Government of Israel, and the assessment that political considerations have functioned as a factor in practice — is drawn from "Israel and the Leahy Law," published by Just Security, written by a former senior State Department official with direct firsthand experience administering Leahy vetting. The 2024 case involving five Israeli military units recommended for Leahy review is documented in the same Just Security analysis and in Human Rights First's reporting. The Council on Foreign Relations' "U.S. Aid to Israel in Four Charts" documents the broader allegation, made by legal scholars and other critics, that the Leahy Law has not been applied to Israel with the same rigor as to other Middle Eastern recipients, and is cited here as a secondary corroborating source rather than a primary one. This post presents documented institutional comparison rather than allegation; the GAO report is a primary government audit document, and the Just Security account, while a first-person former-official narrative rather than an official government finding, is the most detailed public account available of the ILVF's internal procedure as of this writing.

The Integration Architecture  ·  Series Navigation

Post IThe Mandate

Post IIThe Office

Post IIIThe Vehicle

Post IVThe Designation

Post VThe Omission

Post VIThe Leverage

Post VIIThe Precedent

Post VIIIThe Wiring