My name is Kenn Dowell — Cleveland-born and Glenville-raised, and never afraid to say what needs to be said.
Before we get into it — thank you for reading Strategic Moves. If you’re new here, welcome. If you haven’t already, subscribe for free — it costs you nothing and makes sure you never miss a breakdown. And if this work is worth more to you than the free tier, a paid subscription helps keep this operation running and keeps the analysis coming every week, no matter who’s uncomfortable with it. Either way — glad you’re here. Let’s get into it.
Cleveland City Council just voted on two things that got reported everywhere as wins. Neither one closes the door it needed to close.
Here’s the part nobody’s saying out loud.
Council renewed its contract with Flock Safety, the company running the license plate readers watching this city, 9 to 6. In the same amendment, they cut off the Northeast Ohio Regional Fusion Center — a Homeland Security-linked local-federal data-sharing hub — from access to that camera network. They shortened the deal to six months instead of a year. They cut Flock’s fee in half. They added a transparency portal and quarterly reporting. On paper, that reads like accountability is working exactly as it should.
Watch what that accountability actually protects against.
It protects against this specific vendor, under this specific contract, for the next six months. It does nothing about the next fusion center, the next data-sharing partner, the next vendor with a new name and the same appetite for access. The amendment closed one door. It didn’t ask why the city keeps building doors that need closing after the fact instead of getting the terms right before signing.
Same meeting, same instinct, bigger blind spot.
The city rejected a permit for a $1.6 billion, 150-megawatt data center proposed for a 35-acre site in Slavic Village. This working-class neighborhood found out about the project the same way most residents find out about deals that affect them: after it was already moving.
The mayor’s office cited “serious concerns about hyperscale, standalone data centers being placed in residential neighborhoods.” No further explanation. No public criteria. No standard anyone can point to and say, “Here’s exactly why this one failed and what the next one has to do differently.”
“That’s not a win. That’s a black box that happened to open in the community’s favor this one time.”
Here’s the detail that should be the actual headline.
Council followed the rejection with a three-month moratorium — but read what it actually covers. The freeze applies only to standalone data center buildings. Server farms built inside multi-tenant or mixed-use developments are explicitly exempt.
Nobody covering this story flagged what that means in practice: the same computing capacity Slavic Village just fought off can come back next month, wrapped inside a “mixed-use” development, and the moratorium will never touch it. The loophole isn’t closed. It’s been renamed, and the rename is sitting in the ordinance text right now, waiting for the first developer smart enough to read it.
This is the pattern underneath both stories, and it’s the same pattern every time.
The city doesn’t get ahead of the terms. It reacts, after the fact, to whichever version of the problem showed up first and made enough noise to force a response. A camera network gets a data-sharing hookup nobody approved, and the fix is a six-month patch on one vendor’s contract.
A data center gets proposed on land nobody consulted, and the fix is a three-month pause with a hole in it big enough to drive the same project through under a different label. Neither fix asks the actual question: what’s the standing rule, applied before the crisis, that prevents this category of problem regardless of which company or which neighborhood shows up next?
That’s the difference between winning a fight and building a floor. Slavic Village won a fight. Cleveland still doesn’t have a floor.
This isn’t unique to Cleveland, and that’s exactly why it matters here first. Every city adding data center capacity right now is running this same reactive playbook — approve first, regulate after the backlash, patch the specific loophole that got caught, and leave the adjacent one wide open.
The neighborhoods absorbing that pattern are disproportionately those without the political capital to force a public fight before the deal is signed. Slavic Village got its fight because people noticed in time. The next neighborhood, in the next city, might not get that chance — because the rule protecting them still doesn’t exist anywhere it hasn’t already been forced into being.
Full breakdown — the fusion center language, the exact moratorium carve-out, and what a real standing policy would need to look like — on the newsletter this week.
What’s the version of this “temporary fix, permanent loophole” move happening in your city right now? Drop it in the comments — I’m building the file on this pattern, and I want your entries in it.