I want to step away from the usual format of this blog for one post. No records request, no lawsuit filing, no city council agenda item. Just something I’ve been chewing on for a while now, and a conversation tonight that finally put it into words I could write down.

The pattern under the pattern

If you’ve read this blog for any length of time, you’ve seen the shape by now. Flock cameras. Zencity scraping social media sentiment. Cell-site simulators bought with forfeiture money. Kyle Bass and a private equity firm trying to pull billions of gallons out of an aquifer an entire region depends on. Data centers justified as a national necessity while they draw down water and power with almost no local say in the matter.

I keep writing about these as separate stories because they arrive as separate stories, different vendors, different agencies, different counties. But they’re not separate. They’re the same mechanism wearing different clothes, and I think it’s worth naming the mechanism directly instead of dancing around it story by story.

Here’s the mechanism: someone builds a capability because they can. The capability gets sold using a fear or a promise big enough that nobody wants to be the one arguing against it, public safety, missing children, beating China, keeping the lights on. The purchase or the buildout gets funded through a channel that skips a real public vote, grant money, forfeiture funds, a line-item contract, a national security exemption. And by the time residents find out what was actually built and what it’s actually capable of, it’s already running. The audit trail exists. The oversight policy exists. It just all showed up after the fact, not before.

That’s not a conspiracy. Nobody sits in a room plotting to build a surveillance state. What I’ve come to believe, after tracing this pattern across a dozen different posts on this blog, is something a little harder to sit with: this is what fear does when you hand it a budget and a supply chain.

Every arms race starts with someone who meant well

Alfred Nobel spent his life building dynamite to make mining and construction safer than the nitroglycerin it replaced. He held over 350 patents and thought of himself as an industrialist solving an engineering problem. By the end of his life, dynamite was being used to kill people faster than anything that came before it, and the newspapers said so plainly. He didn’t set out to build a weapon. He built a capability, and the capability went where capabilities go.

The Manhattan Project is the starker version of the same story. Physicists who were horrified by the idea of a nuclear weapon built one anyway, because the alternative, a fascist regime getting there first, felt worse than the thing itself. That’s not a story about evil men. Oppenheimer spent the rest of his life wrestling with what he’d built. The logic that got him there wasn’t malice. It was fear, wearing the mask of responsibility: if it’s coming either way, better that someone with a conscience gets there first.

That exact argument is being made out loud right now, by AI labs, by data center developers, by the people funding the current infrastructure buildout. We can’t let China get there first. The technology is coming regardless of what any one company does, so better to be at the frontier and shape the norms than cede the ground to whoever has fewer scruples. It’s a coherent argument. It’s also the same argument every physicist on the Manhattan Project made to themselves, and it comes with the same question nobody’s answered: does being first with better intentions actually produce a better outcome, or does it just guarantee the powerful thing exists sooner, and drags everyone else into the same race behind you?

I don’t have a clean answer to that. I don’t think anyone building frontier AI right now does either.

Fear turns questions into loyalty tests

Watch what “we can’t let China get there first” actually does in a conversation. It doesn’t answer whether a data center’s water use is reasonable. It doesn’t answer whether the power draw should come from gas peaker plants. It converts a cost-benefit question into a loyalty question, and loyalty questions don’t get debated, they get complied with. Ask a hard question about the pace of the buildout and you’re not raising a valid concern anymore, you’re the person who’d rather lose the race.

I hear a version of this every time someone on social media tells me they don’t mind being tracked because they’ve got nothing to hide. Or that questioning a camera network means I must want kids to get hurt. Neither of those is actually an argument. They’re conversation-enders. They work by turning a policy question into a character question, so that defending yourself becomes the whole conversation instead of the tool itself ever having to justify what it does.

Nobody who says “nothing to hide” would actually hand over their own location history and search logs with no warrant and no oversight, no audit trail after the fact, just full access. If they wouldn’t accept that standard for themselves, it’s not a principle. It’s a script they’re repeating because it makes them feel like the reasonable one in the room.

And “safety” framing works precisely because nobody wants to be the person who argued against protecting children. That’s exactly why it’s such a convenient frame for anyone selling something that wouldn’t survive being examined closely. The urgency is the point. It’s designed to make you skip the part where you ask if the tool actually works, who else gets access to the data, and what happens when someone with legitimate credentials decides to use it for something it wasn’t sold for.

The compliance chain, and why “just doing my job” doesn’t clear anyone

Here’s the part I had to correct myself on tonight, and it’s worth writing down honestly. I’d started explaining why individual engineers and city officials end up building and approving things they’d never personally choose to unleash on their neighbors: budget pressure, genuine belief in the sales pitch, a technical knowledge gap, institutional inertia once a program exists. All of that is true as description. None of it is an excuse, and I let it function like one for longer than it should have.

There’s a name for this in ethics. Hannah Arendt covered Adolf Eichmann’s trial and coined the phrase “the banality of evil” to describe how ordinary and undramatic he came across, a bureaucrat filling a role, not a monster. That phrase gets misused constantly to mean “see, it’s just ordinary people, don’t judge them too hard.” That is not what she was arguing. Her point was closer to the opposite: the fact that harm gets carried out by people who never think of themselves as doing anything wrong doesn’t make the harm smaller. It makes the mechanism more dangerous, because it means the harm doesn’t require anyone evil to keep running. It just requires enough ordinary people declining to ask the question.

Every engineer who writes the matching algorithm, every product manager who ships the feature, every executive who approves the funding round, every official who signs the contract, makes an actual choice at some point to keep going instead of stopping. The system makes that choice easy not to examine. It doesn’t relocate the choice. Diffused responsibility doesn’t mean nobody’s responsible. It means the responsibility got spread across more hands, not zeroed out. Ten people each contributing a share of the harm doesn’t add up to a tenth of a crime each. It’s the same crime with more names on it.

I don’t think it takes a uniquely dark psyche to end up building a mass surveillance tool. I think it takes an ordinary psyche, a paycheck, a technically interesting problem, and enough distance from the people it gets used against that the harm stays abstract. That’s a much bigger population of people than “those who’d consciously choose to exploit the unwilling masses.” It’s also the scarier version of the same problem. A functioning, well-compensated industry of otherwise decent people keeps this running without most of them ever having to frame it to themselves the way I just framed it here.

Where I land, for now

I don’t think the honest answer is that we’re racing toward our own destruction with no say in the outcome. Every one of these histories, Nobel, the bomb, the current AI buildout, has a counter-thread running alongside the destructive one. Nobel’s fortune built the prize that now rewards the kind of work that pushes back against exactly what he made possible. The nuclear race that could have ended the world instead produced decades of deterrence and inspection regimes, built by people who looked at the same trajectory and refused to treat it as fixed.

That’s the part worth holding onto. The moratorium in East Texas didn’t happen because a company had a change of heart. It happened because residents and a lawmaker pushed back while the fight was still open. The audits that caught officers abusing plate reader access didn’t happen because the system polices itself well. They happened because someone was watching and asking questions before the harm became permanent.

I write this blog because I think most people building and approving this stuff never sit with it in plain language. Nobody wakes up asking what surveillance tool they can inflict on their neighbors today. They wake up solving a budget problem, a sales quota, a safety pitch that tested well. The gap between what gets built and what anyone actually asked for is enormous, and it stays that way precisely because naming it plainly is uncomfortable.

So that’s what this post is. The uncomfortable version, written down, without the softening I usually put around it when I’m citing a specific vendor or a specific lawsuit. The pattern isn’t limited to Flock, or Zencity, or Kyle Bass, or any one data center. It’s what happens whenever fear gets handed a budget and a supply chain, and enough ordinary people along the way decide it isn’t their place to ask if it should be built at all.

I don’t have a tidy ending for this one. I don’t think there is one yet. But the outcome isn’t decided, and that’s exactly why it’s worth staying loud about it.