Our Ally, Our Spy, Our Military?
The Israel NDAA Provision You Didn’t Vote On
While you were trying to live your life and maybe not doomscroll 24/7, Washington pulled one of those moves that makes you question whether “consent of the governed” is still anything more than a slogan on a civics worksheet.
In the span of a few days, two stories broke that should not exist in the same reality, let alone the same defense bill:
The Pentagon quietly raised its assessment of Israeli spying on the United States to the highest threat level.
A House committee quietly advanced a plan to more deeply integrate the U.S. and Israeli militaries, without a recorded vote and without a single citizen getting any say at all.
If that makes your head spin, good. It should.
The Ally We Call a Spy
Let’s start with the headline almost no one will see on the evening news.
In recent weeks, U.S. defense officials raised the counterintelligence threat level for Israeli espionage on U.S. soil to “critical,” the highest category in the system used by the Pentagon and intelligence agencies to track how aggressively other states are trying to spy on us. “Critical” is not for friendly misunderstandings. It’s the label you put on governments you believe are actively and aggressively trying to penetrate your most sensitive conversations.
Why the upgrade? Reporting says there are growing concerns that Israeli intelligence has ramped up efforts to spy on senior U.S. officials and to get inside internal U.S. deliberations, especially around the wars and crises roiling the Middle East right now. In plain English: while our government debates what to do, one of our closest allies is being treated by our own security apparatus as a serious spy threat trying to listen in.
Publicly, of course, it’s all smiles and statements about “unbreakable bonds.” Israeli and U.S. officials are denying the allegations or brushing them off as overblown. Privately, the people tasked with keeping our secrets safe are telling each other something very different.
This is the backdrop. Now look at what Congress just did.
The Provision You Never Got to Vote On
Every year, Congress passes a colossal bill called the National Defense Authorization Act (NDAA). It’s hundreds or thousands of pages, sets defense policy, and authorizes an eye‑watering amount of money. It’s also treated in Washington as basically “too big to fail”, which makes it the perfect place to hide things you don’t want the public to notice.
This year’s House version of the NDAA includes a little section with a very boring name:
Section 224 – United States–Israel Defense Technology Cooperation Initiative.
Sounds harmless, right? “Cooperation,” “technology,” “initiative.” Bureaucratic chamomile tea.
But read what it actually does.
Section 224 orders the Secretary of Defense to designate a single “executive agent” to oversee U.S.–Israel defense cooperation. That person’s job is to knit together the two militaries by coordinating:
Joint research and development
Co‑production of weapons systems and components
Industrial collaboration across the defense sector
“Network integration” and “data fusion” between U.S. and Israeli systems, especially in areas like AI, drones, missile defense, cyber, quantum, and advanced surveillance technologies
Strip away the jargon, and it’s this: Section 224 builds the plumbing to wire our military’s tech stack, weapons supply chains, and data streams more deeply into Israel’s, at exactly the moment our own Pentagon is treating Israel as a top‑level spying threat.
If you were designing a system to make sure another government could get close to your most sensitive capabilities and communications, this is one way you’d do it.
How They Did It Without You
Now comes my favorite part (and by “favorite,” I mean the part that makes my blood pressure spike): how this moved.
You did not get a vote on Section 224. You didn’t even get to see your representative’s vote.
Here’s why:
Section 224 wasn’t a stand‑alone bill. It was dropped into the chairman’s mark—the base text of the NDAA drafted by House Armed Services Committee leadership before the public ever gets a look.
During the committee’s markup, Congressman Ro Khanna offered an amendment to strike Section 224 because of exactly what we’re talking about: the deep, structural integration with Israel’s military at a moment of massive public concern and opposition.
That amendment did not get a recorded roll‑call vote. Instead, the committee handled it with a voice vote: members say “aye” or “no,” the chair decides which side sounds louder, bang goes the gavel. No list of who voted which way. No paper trail. No accountability.
So when Section 224 survived, it survived without producing a single line that says, “Here is how your representative voted on fusing U.S. and Israeli defense technology.” You can’t hold them accountable for a vote you’re not allowed to see.
This is not an accident. It’s a feature. This is how you move controversial, far‑reaching decisions in a town that still wants to pretend it believes in democracy while doing as much as possible in the shadows.
“Cooperation” in the Age of Critical Threat
Let’s pause and appreciate the absurdity here.
On one side of the house, the security state is quietly saying:
Treat this government as a critical spying threat. Protect our internal deliberations. Be careful what you say and where you say it.
On the other side, the legislature is quietly saying:
Let’s create an office whose job is to integrate our weapons, our industrial base, and our data networks with that same government, and let’s do it without public debate or a recorded vote.
Imagine your bank sending you an alert that your neighbor is a “critical burglary threat” and then, the same week, announcing a program to give that neighbor a spare key to your house and access to your security system because “we’re working together more closely now.” That’s the basic logic of what’s happening here.
And remember: this is on top of everything else about U.S.–Israel relations, the blank‑check rhetoric, the weapons transfers, the diplomatic cover, happening while public support for unconditional backing of Israel’s current government is eroding. When people are in the streets, the instinct in Washington hasn’t been to listen. It’s been to lock the policy in deeper.
The Process Is the Point
You’ve heard me say this before on Politically POMP: democracies rarely die with one dramatic coup. They die by a thousand “procedural” cuts.
Section 224 is one of those cuts.
It hides a big, values‑loaded decision, how deeply to fuse our military with another state’s, inside a giant, must‑pass bill.
It shields members from having to go on the record by using a voice vote instead of a roll‑call.
It assumes you won’t have the time or energy to dig through section numbers and acronyms to figure out what just happened.
Same story with that Pentagon move on religious affiliation codes: shaving the list from over 200 down to 31 in a way that heavily favors Christian denominations and erases a huge number of minority and non‑theistic identities into “Other” or “No Religion,” all under the soothing label of “streamlining.”
In each case, we are told this is just about efficiency, modernization, cooperation. In each case, the effect is to narrow who counts and deepen the power of institutions that answer to each other more than they answer to us.
The pattern is the story.
“But We’re Allies”
Some people will read this and shrug: “We already share intel. We already coordinate. What’s the big deal?”
Here’s the big deal:
Integration is not the same thing as cooperation. You can cooperate with another military and still maintain meaningful lines, controls, and safeguards. Full “network integration” and “data fusion” are something else entirely; they’re about building systems in which disentangling later becomes nearly impossible without massive disruption.
Threat assessment matters. If your own counterintelligence professionals are saying this country is behaving like a top‑tier spy risk, the minimum standard for democratic sanity is that any plan to wire your systems together with theirs gets a loud, public, fully recorded debate. Instead, we got a voice vote in committee.
Public consent is not optional in a democracy. You cannot keep telling citizens “we’re a government of, by, and for the people” while moving decisions of this scale in a way that deliberately avoids letting those people see who chose what.
If our leaders truly believe that Section 224 is the right thing to do, they should have no problem arguing for it openly and putting their names next to their votes. The fact that they didn’t tells you everything you need to know.
What We Can Still Do
Here’s the good news: this story isn’t over yet. The NDAA still has to go through the full House, the Senate, and then a reconciliation process before a final version lands on the president’s desk. Section 224 is in play now, which means this is the moment to raise hell, not six months from now when it’s baked into law and everyone shrugs and says, “Well, that’s already done.”
If you’re reading this and feeling the same mix of anger and exhaustion I am, here are some concrete things you can do:
Call and email your House member and both Senators. Ask one specific question:
“Will you commit to opposing Section 224 of the NDAA and supporting efforts to strip it from the final bill?”
If they don’t know what it is, send them this piece. Make them learn.
Demand a recorded vote. Tell their offices that voice votes on something this consequential are unacceptable. You have a right to know where your representative stands.
Talk about it publicly. Share this, write your own post, bring it up at local meetings, call into radio shows. The only reason this kind of thing works is because most people never hear about it.
Support watchdogs and organizers. There are groups tracking U.S.–Israel policy, civil liberties, and militarization who are already sounding the alarm about Section 224. Follow them, amplify them, help them do the nerdy, unglamorous work of reading every line of these bills.
Washington banks on our fatigue. It banks on us seeing “Section 224 of the NDAA” and hearing white noise. It banks on us believing the story is too complicated, too foreign‑policy‑ish, too far away from our daily lives to bother with.
But here’s the truth: when your government can quietly deepen military integration with a state it is simultaneously labeling a critical spy threat, without your consent, without your knowledge, and without even recording who voted yes, that’s not a foreign policy footnote. That’s a stress test of whether we still live in a functioning democracy.
We didn’t get a vote on any of this.
So the least we can do is refuse to be quiet about it.