The Rebellion That Keeps Us Alive#

I’m going to say something that’ll rub a lot of people the wrong way: one of the healthiest things in American governance is when a state looks at the federal government and says, “Go to hell.”

Not anarchy. Not secession. I’m talking about a governor or a state legislature staring down a federal mandate and going, “Nah. Not here. Not like that.” That stubborn, friction-filled, sometimes infuriating refusal to comply.

People in Washington hate it. They call it inefficient. Messy. An obstacle to clean, uniform policy. And yeah—they’re right about all of that. But here’s what they don’t get: the mess is the point. The inefficiency is the feature. That friction everyone complains about? It’s the last line of defense between us and a catastrophic centralized screw-up that takes down the whole country at once.

I’ll tell you how I know. It starts with the Secret Service.

Redundancy: The Ugly Principle That Saves Lives#

When I was in the Service, we lived and died by redundancy. Multiple security layers. Overlapping responsibilities. Backup plans stacked on backup plans. Efficient? Hell no. You could absolutely design something leaner, sleeker, more streamlined on paper.

But here’s what lean gets you: when it fails, it fails all the way. No safety net. No second bite. The round reaches the principal because there was exactly one thing between the threat and the target, and that one thing didn’t hold.

Redundancy is expensive. It’s slow. People trip over each other. But when Layer One goes down—and believe me, Layer One always goes down eventually—Layer Two is right there. Layer Two fails? Layer Three. The system doesn’t survive because every piece is flawless. It survives because no single piece breaking is enough to kill it.

The American federal system runs on the exact same logic. States are redundant nodes in a distributed network. When the central node—Washington—pushes out a bad instruction, the state nodes don’t have to salute and execute. They can drag their feet. They can push back. They can flat-out refuse. And that refusal, annoying as it is to whoever sent the order, does the same thing a backup layer does on a protection detail: it catches the mistake before it turns into a body on the ground.

Single Processor vs. Distributed Network#

Think about it this way.

A fully centralized government is a single-processor machine. One brain, one instruction set, one pipeline. Fast. Clean. Every command fires immediately, uniformly, everywhere. But when that processor has a bug—when the central algorithm gets it wrong—the error rips through every corner of the system instantly. No circuit breaker. No failsafe. The whole machine goes down at once.

A federal system with real state sovereignty? That’s a distributed network. Multiple processors running semi-independently. Slower, sure. More overhead. The processors argue with each other sometimes. But when one processor sends garbage, the others aren’t forced to swallow it. They reject it, tweak it, run their own alternative. The error gets contained. The system bends. It doesn’t shatter.

The founders got this. Maybe they didn’t think in computer science terms, but they’d just finished fighting a war against a system where one brain made every call and every node obeyed without question. They built America specifically to prevent that kind of efficient, uniform, catastrophically brittle governance.

And here’s the piece that critics of “states’ rights” consistently miss: the value of state resistance isn’t that states are always right. They’re not. States have been dead wrong about plenty of things. Spectacularly, historically wrong. The value is that their resistance creates three functions no centralized system can replicate.

Function One: The Signal#

When a state shoves back against federal policy, it’s broadcasting information. Raw, unfiltered information. It’s saying: “This doesn’t work here. People are getting hurt. They’re angry.”

In a centralized system, that kind of feedback rarely makes it to the decision-makers. And when it does, it arrives sanitized—smoothed out by layers of bureaucracy until all the sharp edges are gone. State resistance is the opposite. It’s loud. It’s political. It’s impossible to pretend it isn’t happening.

That signal matters more than anything, because the single most dangerous thing for any leader is to be insulated from the consequences of their own decisions.

Think about it like your body’s pain response. You touch a hot stove, the cells in your hand scream at your brain. Pain isn’t pleasant, but it’s the only thing that stops you from holding your hand there until the bone shows. State resistance is the pain signal of the federal system. It makes Washington flinch—and that flinch carries information they desperately need.

Function Two: The Firewall#

When a state refuses to implement a bad policy, it contains the blast radius. Instead of the damage hitting all fifty states at once, maybe it hits forty-seven. Three states hold out. They become the control group.

Not ideal—ideally the bad policy wouldn’t exist. But it’s a hell of a lot better than uniform catastrophe across the board.

This matters especially because federal policy is inherently one-size-fits-all. But America is not one size. What works on the streets of Manhattan is meaningless in rural Montana. What makes sense for eight million people stacked on top of each other might be devastating for a community of eight hundred spread across a county. State resistance allows the system to adapt locally—like an immune response that tailors itself to the specific threat in the specific organ, instead of carpet-bombing the whole body with the same drug.

Function Three: The Laboratory#

When states refuse to follow the federal playbook, they open up space for experimentation. Maybe Washington got it wrong. Maybe there’s a better way. You’ll never know unless someone tries something different—and states that chart their own path become natural testing grounds for policy innovation.

Some of the best policies in American history started exactly this way. A state tried something nobody in Washington had the guts to try. It worked. Other states picked it up. Eventually the feds adopted it. The innovation didn’t come from the center. It came from the edges. And the edges can only innovate if they have the room to say no.

The Honest Limits#

I want to be straight about where this argument hits a wall, because I’m not some states’-rights absolutist waving a flag from a bunker.

Not all state resistance is healthy. Some of it is pure obstruction—resistance for the sake of resistance, with zero substantive alternative on the table. Some of it is political theater: a governor grandstanding for cameras while offering nothing real. And let’s not pretend the history is clean. “States’ rights” has been the banner for some of the ugliest chapters this country has lived through—slavery, segregation, voter suppression. The principle itself is morally neutral. It can serve justice or serve as a weapon against it, depending entirely on who’s holding it and why.

The line that matters is between resistance as a corrective signal and resistance as a power grab. Healthy resistance says: “This policy is hurting people, and here’s the data.” Unhealthy resistance says: “Nobody tells us what to do. Period.” The first is an immune response. The second is an autoimmune disorder—the body attacking itself.

The real challenge is keeping the infrastructure that enables healthy pushback while strangling the pathological kind. That takes something Washington is running dangerously low on: nuance. The ability to say, “State sovereignty matters—and also, some exercises of state sovereignty are indefensible.” Holding two truths at once. Most people in politics can barely hold one.

The Flatline#

Here’s what I keep circling back to after all my years in the Service and everything I’ve seen in politics: the most dangerous system on earth is the one with no internal conflict.

When every node in the network snaps to attention and executes the central command without hesitation, it looks incredible. Decisions land fast. Implementation is seamless. No messy disagreements, no governors on cable news torching the president’s agenda. It looks like strength.

It’s actually the most fragile thing you can build.

Because when central command screws up—and it will, because every institution run by humans eventually does—there’s nothing to catch the fall. The error cascades through every level, every state, every town, all at once. By the time anyone figures out the policy is toxic, it’s already everywhere. No control group. No firewall. No signal. Everyone was too busy saluting to notice the building was on fire.

The Soviet Union was efficient. Commands flowed from Moscow to every republic like water through a pipe. No friction. No pushback. And when those commands were wrong—when the agricultural directives starved entire regions, when the economic plans ground the country to a halt—there was no corrective mechanism anywhere in the system. The error spread uniformly. Millions paid for it with their lives.

America’s loud, argumentative, friction-filled mess is the opposite of that. It’s harder to manage. It’s slower. It’s uglier. But it’s alive in a way centralized systems never are—because it can catch its own mistakes before they become the kind of thing historians write about with a body count.

The fight over state sovereignty was never really states versus Washington. It’s about whether we keep the distributed architecture that makes this whole thing resilient. Whether peripheral nodes retain the right to push back when the center sends bad code. Whether the rebellion stays alive—not because rebels are always right, but because a system that can’t rebel is a system that can’t fix itself.

And a system that can’t fix itself doesn’t last.

That friction between Washington and the states? It’s not weakness. It’s a pulse. The day every governor falls in line without a word—the day the states go quiet—is the day America’s immune system flatlines.

That’s not unity. That’s death.