Weekly Recap: The Buildout Meets Its Neighbors

Today on Concrete Compute: this was the week the AI buildout ran straight into the people who live next door to it. A landmark Virginia ruling that forces data centers to pay their own way on the grid. A five-hundred-megawatt Amazon campus in Maryland, pulled after voters ousted the commissioners who backed it. And — this one actually stopped me cold — a credible death threat against city council members in a small Michigan town, over nothing more than a one-year pause on new data center construction. Before we dig into all of that, we'll also cover PJM's new rulebook after data centers tripped off the grid in July, SpaceX's plan to run a sixteen-point-eight-billion-dollar chip campus entirely off the Texas grid, and where the neocloud money is actually landing this earnings season. Welcome back to Concrete Compute, your weekly recap of the AI infrastructure buildout. It's Saturday, August 15, 2026. This is the week that was — let's get into it.

Let's start with the biggest community win of the week, out of Virginia. Here's the number that matters: the average residential bill increase tied to new data center transmission costs was projected at two dollars and ninety cents a month. After this week's order from the State Corporation Commission, that number drops to ninety-four cents — a cut of about sixty-seven and a half percent. The mechanism behind that: the SCC ordered Dominion Energy to develop a tariff that directly assigns the cost of new transmission infrastructure — the substations, the dedicated lines built specifically to serve a hyperscale campus — to the data centers and large-load customers that actually trigger them, instead of spreading those costs across every ratepayer in the state. This didn't happen in a vacuum. Governor Spanberger's administration filed comments and testimony with the commission — through Chief Energy Officer Josephus Allmond — arguing that residential customers shouldn't be subsidizing infrastructure built solely for data centers, and the commission agreed. The order specifically flags the future seven-hundred-and-sixty-five kilovolt Valley Link line, running from Lynchburg to Culpeper, as the test case for how this actually gets applied going forward. Now, the caveat, and it's a real one: this is a directional order, not a finished rate structure. The exact tariff mechanics, and how costs get split among different large-load customers, are still getting worked out in a new docket. But directionally, this is the clearest signal yet that a major PJM state is willing to say 'data centers pay their own way' out loud, in a binding order. Other states weighing similar cost-allocation fights are going to be watching this docket closely.

Next, Maryland — and a story that shows what happens when that same fight goes the other direction. Up to five hundred megawatts is the capacity of the data center campus Amazon Web Services just walked away from — a two-point-four to two-point-five million square foot project proposed right next to the Calvert Cliffs Nuclear Power Plant. That project is now off the table in Calvert County. Underneath that number: months of organized opposition, a Change dot org petition that topped ten thousand signatures, the county's own Environmental Commission calling for a twelve-month pause over water, noise, and habitat concerns — and a primary election that ousted three county commissioners who'd resisted a moratorium. Amazon insists the withdrawal was a 'business decision,' unrelated to politics, and both Amazon and Constellation, which operates the nuclear plant, say they may come back with a revised or nearby proposal. So don't read this as a permanent defeat. But it's hard to ignore the pattern — Chesapeake Climate Action Network figures cited in this coverage put roughly three-quarters of Maryland residents in jurisdictions that already have some form of data center moratorium in place, and Calvert County commissioners are now moving toward making theirs formal. My own take: when the politics around a site turn this fast, a company calling it a 'business decision' and that same site having just lost an election aren't mutually exclusive explanations.

Then there's Marshall, Michigan — and this is the one that made me pause while writing today's script. Two weeks after the city council voted, unanimously, for a one-year moratorium on new data center development — aimed at a two-hundred-seventy acre project that Alterra Development had proposed at Brooks Industrial Park — council members received what officials called a credible death threat. Councilman James Hackworth put it plainly: threatening violence 'is not activism.' Marshall police did investigate the anonymous threat, and they've declined to file charges, citing insufficient evidence — the person accused of making the threat denies doing so — and they're now asking the community for what they're calling civil dialogue going forward. The fairness check here matters: this appears to be one anonymous poster, not a referendum on how the whole town feels about the data center fight. Marshall, like a lot of small communities weighing these proposals, has real trade-offs on the table — construction jobs and tax base against water use, noise, and industrial-scale power draw next door. Those are legitimate things to argue about, loudly, at a city council meeting. What happened in Marshall isn't that. It's the ugliest data point yet in a nationwide wave of local data center opposition that, up to now, mostly played out in petitions and moratorium votes — and it's a reminder that as these fights get more local and more personal, the temperature can rise faster than anyone's prepared for.

Now to the grid side of the story, and a number that explains why PJM spent this week rewriting its rulebook. Three thousand eight hundred megawatts — that's how much Northern Virginia data center load flipped onto backup generation during a grid disturbance on July twenty-second. That's the third time this kind of transfer has happened — after roughly one thousand five hundred megawatt events in twenty twenty-four and twenty twenty-five — and July's three thousand eight hundred megawatts is the largest in that stretch by a wide margin. PJM's Operating Committee chair didn't mince words about it, saying flatly that data centers 'should not disconnect from the grid' during a fault that would normally just clear itself. PJM itself says it has filed a proposal with federal regulators — a framework for connecting data centers that bring their own onsite power, consistent with what PJM calls its Ratepayer Protection Pledge, plus a new Interim Resource Adequacy Service for large loads that don't bring generation of their own. On X, S&P Global Platts senior editor @JAndersonEnergy summarized the filing as an attempt to ease the supply-demand gap PJM's identified, while energy analyst @ShanuMathew93 framed the bigger implication this way: 'Firm interconnection is becoming a differentiated asset.' That's the real story here: reliable, always-on grid connection has become a competitive advantage, and operators are starting to treat it that way. The catch: the actual ride-through obligations, which facilities they'll cover, and how existing projects get grandfathered in are all still moving through PJM's stakeholder process and a parallel FERC docket. Nothing's locked in yet.

Sixteen point eight billion dollars is the initial investment SpaceX and Tesla are putting behind Terafab — the semiconductor and AI-compute campus going up in Grimes County, Texas. And the wrinkle that makes it worth a full segment: under SpaceX's tax-abatement agreement with the county, the plant is stated as 'not expected to use electricity from the grid' at all — running instead on onsite natural gas generation and large battery arrays. Here's the part that didn't make the headlines, though. The same county agreement carves out language allowing grid interconnection for startup power, emergency imports, or exports — so this may not be quite as fully off-grid as the framing suggests. In exchange for the tax break — a full county property tax abatement running through twenty thirty-six — SpaceX has separately committed to invest at least five billion dollars by twenty thirty and create at least eighteen hundred jobs by twenty thirty-five. SpaceX also retains a thirty-day right to exit the agreement. That's a real, specific community benefits package, with real numbers attached, which puts it ahead of a lot of the vaguer language we're used to seeing in these deals. So watch that jobs number in particular — eighteen hundred jobs by twenty thirty-five is the figure that would actually tell us whether this campus delivered on its promise, or whether the tax abatement outlasted the commitment behind it.

Sticking with the money side for a minute — the neocloud earnings that came out this week tell a pretty consistent story. CoreWeave, Nebius, and Cerebras all posted another quarter of rapid revenue growth, and all three also posted widening losses. That's not automatically alarming — infrastructure-heavy young companies are supposed to spend ahead of profitability while they're building out capacity — but it does raise a real question about how patient investors will stay while capex keeps outrunning revenue. This connects directly to a thread we're about to get into with Nvidia's five-hundred-billion-dollar financing push: there's reporting alongside these earnings that neoclouds are building cash hoards faster than their revenue is growing, which tells you these companies are raising capital aggressively even as the losses on paper get bigger. None of the three broke out exactly how much of that growth is contracted revenue versus recognized revenue this round, either — that's the detail I'd want before drawing hard conclusions about how sustainable the growth line actually is. So how long does that keep working? Nobody in this reporting has an answer, and neither do I — this quarter's numbers alone don't tell you where the ceiling is, only that nobody's hit it yet.

North of the border this week, Ontario tried something different: instead of a moratorium fight, the province rolled out a new data center framework upfront, pitched explicitly around 'meaningful benefits' for host communities. I'll be honest, 'meaningful benefits' is doing a lot of work in that sentence, and the initial reporting is thin on what it actually means in dollars, jobs, or rate protections — which is exactly the detail that determines whether this is a real answer to the host-community question, or just better marketing than Virginia, Maryland, and Michigan have managed so far. The question I keep coming back to is what the town actually gets once the construction crews leave — tax base that outlasts the build, jobs that aren't just temporary, protection from footing the power bill for someone else's campus. Virginia's SCC order this week is one kind of answer — a mandated cost shift, arrived at through a regulatory fight. Ontario is trying to get ahead of that fight entirely, offering the framework before the moratoria show up. Here's my honest opinion, and it's mine alone: any government or company promising 'meaningful benefits' owes the public actual numbers, on a specific timeline, not a press release with an adjective in it. We'll know a lot more once Ontario's framework has real figures attached.

Last story of the week ties the whole thing together with money. Five hundred billion dollars is the number attached to the AI infrastructure financing push reporting credits to Nvidia, structured to fund data center buildout across multiple operators. To translate that: it's financing architecture, not a single check being written — the kind of capital stack that lets multiple companies fund gigawatt-scale campuses without necessarily putting it all on their own balance sheets. What jumps out to me is where this lands relative to everything else in this episode. Massive committed capital is chasing a physical build — power, land, transmission — that is not moving anywhere near as fast as the money. That's exactly the tension behind the PJM ride-through fight, and it's exactly the tension behind Virginia forcing data centers to directly pay for their own transmission lines instead of socializing the cost. The honest caveat on a number this size: financing structures at this scale are genuinely complex, and the headline figure tells you less than the deployment timeline will. Committed financing and energized megawatts are two very different milestones, and this week's neocloud earnings are a decent reminder of how much space can open up between them. So the number worth tracking from here is how much of that five hundred billion actually turns into steel, substations, and interconnection agreements over the next few quarters.

That's the week: a regulator making data centers pay their own way, a five-hundred-megawatt project that didn't survive an election, and a small-town fight that turned genuinely dangerous. If any of that touches your town, your utility, or your portfolio, that's exactly why we do this every week. Follow Concrete Compute wherever you listen, so the next gigawatt headline lands with the context already built in — and if this week's episode was useful, send it to one person who works in power or permitting. This has been Concrete Compute, an AI-voiced podcast, created and built by a real human using today's cutting-edge technology. Nothing you heard on this show is financial advice. I'm Brian Lampert, and I'll catch you all tomorrow — take care!