When armored trucks and camo uniforms roll down city streets, it’s hard not to feel a twinge of unease, even for those of us who appreciate law and order. Over the past few months, National Guard convoys have appeared in a few urban battlegrounds, all under orders from Washington. Governors are suing, federal lawyers are countersuing, and the rest of us are left wondering: Whose Guard is it, anyway?

Apparently, the word “National” is now doing a lot more work than the word “Guard.”

The latest showdown pits President Trump’s administration against governors from California, Oregon, and Illinois. The White House says it’s simply enforcing federal law and protecting federal property. The states say it’s federal overreach, plain and simple. Judges are now deciding who actually commands these troops when Washington and the states disagree.

Beneath the lawsuits and press conferences lies a much older argument, one the Founding Fathers settled, or at least thought they did, more than two centuries ago.

A Brief History Lesson They Forgot in Civics Class

In the early days of the Republic, the state militias were considered essential, local citizens defending their own communities. The Constitution allows the federal government to “call forth the Militia to execute the Laws of the Union, suppress Insurrections and repel Invasions,” but otherwise, those forces belonged to the states.

James Madison wrote in Federalist No. 45, “The powers delegated by the proposed Constitution to the federal government are few and defined.” He wasn’t kidding. The states, Madison said, were to retain nearly everything else, including control of their militias.

But history, as usual, had other plans. Over time, Congress and the courts redefined “militia” into “National Guard,” and federal authority expanded right along with the name. From the Militia Act of 1903 to the post-9/11 defense laws, Washington gained more and more say over who trains, equips, and deploys the Guard.

Now, when a president wants to federalize state Guard units, governors seem to have little say.

The Modern Power Grab

Let’s be honest: this didn’t start with President Trump. The steady expansion of federal control over the National Guard has been a bipartisan project, a slow but consistent erosion of state authority that’s unfolded under every administration this century. Each president inherits a little more power than the last, promises to use it wisely, and then stretches it just far enough to make that “temporary” precedent permanent.

After the September 11th attacks, President George W. Bush relied heavily on the Guard to defend the homeland. Guard units patrolled airports, secured borders, and stood ready for counterterror operations. The Guard became an essential arm of national defense, and a convenient one, since these forces could be mobilized quickly and at relatively low political cost. When Hurricane Katrina devastated the Gulf Coast, Washington again leaned on the Guard, directing massive deployments that blurred the old line between state control and federal command. What began as an emergency response gradually evolved into a model for national intervention, and few in Congress raised an eyebrow.

President Obama followed with his own version of federal activism. In 2010, his administration deployed roughly 1,200 National Guard troops to the U.S.–Mexico border, later extended under “Operation Phalanx.” Officials stressed that these troops were not enforcing immigration law directly; they were providing surveillance, logistics, and intelligence support to border agents. But in practice, it deepened the idea that the Guard could be federalized or redirected for domestic operations that had once been the sole domain of the states. Even limited, temporary deployments shifted expectations about who really commands these forces.

President Trump, during his first term and now again, has used the Guard for urban security and protection of federal facilities, first during the 2020 riots and more recently attempting to send Guard forces to Portland and Chicago, where federal authority and local leadership have clashed. Supporters call it decisive action; critics call it overreach. But the broader truth is this: every president since 9/11, Republican and Democrat alike, has grown more comfortable treating the Guard as a standing federal instrument, a ready reserve for domestic crises and political standoffs alike.

Each move creates a new “normal,” and every “normal” becomes the next administration’s baseline. The problem isn’t any single president; it’s the steady migration of power from the statehouses to the federal bureaucracy. The Founders envisioned the Guard — the old state militias — as a shield of local authority. But over time, that shield has been repurposed into a tool of national convenience. What began as an exceptional measure has become standard procedure, and Washington seems in no hurry to give it back.

The Governors’ Revolt (Sort Of)

In the latest twist of federal-versus-state drama, governors like California’s Gavin Newsom and Oregon’s Tina Kotek have suddenly discovered a deep love for the Tenth Amendment. Both states have sued the Trump administration, arguing that Washington’s attempt to deploy National Guard troops within their borders violates the Constitution and encroaches on state authority. Their lawsuits paint the picture of brave defenders of local control, standing firm against the heavy hand of Washington.

The irony, of course, is almost too rich. These are the same governors who, in nearly every other policy fight, demand more federal action: on health care, climate change, gun laws, education, you name it. They’ve cheered for Washington’s intervention when it meant billions in subsidies or new regulations aligned with their priorities. But when the federal presence arrives wearing camouflage instead of a grant program, their enthusiasm for centralized power vanishes overnight.

That said, even a broken clock can tell the right time twice a day. In this case, Newsom and Kotek are standing on solid constitutional ground. The National Guard, by design, belongs first to the states. It’s only meant to be federalized under narrow, clearly defined circumstances, such as an invasion or rebellion, not because Washington is frustrated with local policies or policing decisions. The Founders didn’t envision the president as a national superintendent, sending troops wherever he saw fit to keep the peace or make a political point.

The legal battles unfolding now aren’t just about Portland or Chicago; they’re about the future of state sovereignty in an era when Washington increasingly treats states as branch offices. The governors, to their credit, are forcing the courts to revisit where the constitutional line really lies and whether that line still means anything.

If they win, it could reaffirm a long-forgotten truth: that the federal government is not a parent correcting unruly children, but a limited partner in a union of equals. If they lose, it will mark yet another inch of authority quietly absorbed into the vast machinery of Washington, leaving state governments weaker and citizens with one fewer buffer between themselves and centralized power.

Either way, this “revolt” is more than a spat over troops; it’s a test of whether the spirit of federalism still lives in the modern republic, or whether it’s just another antique principle gathering dust in the National Archives.

Why Conservatives Should Care

It’s easy to preach about limited government when it’s the other side in power. It’s harder when the man sitting in the Oval Office is “on our side.” But if our commitment to the Constitution depends on who’s signing the executive orders, then it isn’t really a commitment; it’s just convenience dressed up as principle.

As conservatives, we often pride ourselves on defending federalism, local control, and checks on centralized authority. Yet, when chaos breaks out in left-leaning cities and the headlines show fires, looting, and lawlessness, it’s tempting to cheer for any show of order, even if it comes from Washington. But that’s a dangerous habit. Because once we justify stretching federal power to deal with “their” crises, we hand the same power to the next president, who may see us as the problem to be contained.

The Bible gives us a sober warning about unchecked authority. When Israel demanded a king “to judge us and go out before us,” the prophet Samuel warned that the ruler would take their sons, their fields, and their freedoms until they cried out for relief (1 Samuel 8:11-18). It was a lesson in human nature: even good leaders are tempted to rule beyond their bounds. Power once seized rarely returns quietly.

That’s why constitutional restraint isn’t a luxury; it’s a safeguard. The Founders designed the system to slow us down and make sure impulse never outruns wisdom. State sovereignty and separation of powers aren’t outdated relics; they’re guardrails built to protect liberty from good intentions gone too far.

So yes, President Trump’s desire to restore order in places like Portland or Chicago may come from a legitimate concern. But good ends don’t sanctify bad methods. Conservatives should be the first to say, “Hold on; is this Washington’s job, or the state’s?” Because if we only defend limited government when it’s politically convenient, then we don’t really believe in limited government at all.

The Constitution wasn’t written to restrain bad presidents; it was written to restrain all of them. And if we forget that, it won’t matter much who holds the office because the office itself will hold too much power.

The Way Forward: Restoring the Balance

If there’s one thing history teaches, it’s that once Washington gains a new lever of control, it’s treated not as an exception but as a precedent. And soon, it’s just “the way things are done.” Reversing that trend will take more than speeches about the Founders; it will require deliberate action by the states and vigilance by the citizens who keep them accountable.

Governors— of either party — who care about sovereignty need to stop waiting for permission to assert it. The Constitution already gives them the tools. States can form compacts reaffirming their shared authority over National Guard forces, passing laws that clarify limits on federalization, and challenging executive overreach in court whenever it appears. These fights might look small, but they add up. Federalism, after all, doesn’t die all at once; it fades in a thousand quiet concessions.

Congress, too, could stand to rediscover its spine. Instead of writing endless checks to the executive branch in the name of “emergency powers,” lawmakers could restore clear statutory guardrails for when and how the Guard can be called into federal service. It shouldn’t take a courtroom standoff every time a president tries to use state troops for domestic missions. A republic worthy of the name ought to know who’s in charge before the Humvees start rolling.

But the real responsibility lies with the people. As voters, we’ve grown accustomed to demanding that Washington solve every problem, and in doing so, we’ve made Washington far too powerful to resist. The Founders expected Americans to govern locally, to know their state leaders, and to understand that the federal government was meant to be the last resort, not the first. Recovering that mindset might be the most patriotic act of all.

Because in the end, the debate over the National Guard isn’t just about troops or court rulings; it’s about what kind of country we want to be. Do we still believe in self-government, or have we traded it for the illusion of safety under an all-powerful federal hand?

The Founders gave us a blueprint for liberty: divided power, local authority, and a government strong enough to protect us but restrained enough to leave us free. That balance is fragile, and if we don’t guard it, no one else will.

If the National Guard is to live up to its name, maybe it’s time we remember what it was meant to guard: not the government, but the people’s right to govern themselves.