Back to Green Data Centers
I stopped writing about green data centers for a while because the conversation started feeling stale.
The same ideas kept showing up with new logos attached: renewable energy claims, PUE numbers, sustainability reports, renderings, commitments, and announcements. Some of the work is real. Some of it is excellent. But the public conversation has become predictable.
So I decided to come back a different way.
Instead of writing about another announced facility, I am going to write about my own fictional green data center — one that lets me test what "green" actually means when the claims have to hold.
The project starts with a simple physical frame:
100,000 square meters of floor area, 10 meters tall, for a total of 1,000,000 cubic meters of space.
That number — 1,000,000 cubic meters — is not arbitrary. It is a forcing function.
At that scale, the comfortable hand-waving that fills most green data center writing stops working. You cannot just say "we use renewable energy" and leave it there. You cannot cite a PUE number without explaining how you measured it. You cannot claim cooling efficiency without accounting for what happens when the ambient temperature spikes, the grid gets stressed, or the AI workload doubles overnight.
At 1,000,000 m³, every claim becomes a structural argument.
And structural arguments either hold or they do not.
What I Got Bored Of
The green data center space has a formula. You have seen it.
A press release announces that a new hyperscale facility will be powered by 100% renewable energy. There is a rendering. There are sustainability commitments. There is a PUE number that sounds impressive. The facility opens. The sustainability report comes out twelve months later. Much of it reads like marketing.
I am not saying the work is not real. Some of it is. But the industry conversation has become a loop.
The hard questions are usually avoided.
What does it actually mean to be green in a way that can be verified by someone other than the company making the claim?
What happens to green commitments during a prolonged drought, when cooling towers become a liability?
What happens when the local grid is stressed and diesel generators run for four hours?
What happens when the AI workload doubles overnight and the thermal profile of the building changes?
Those questions are more interesting to me than another announcement.
The Fictional Project as a Tool
So I built a fictional one.
No specific location. No owner. No PR constraints. Just a volume of space and the question:
What would it take to make this genuinely, structurally green?
Fictional does not mean unserious. It means unconstrained. It lets me test the claims without being trapped inside a vendor story, a corporate sustainability report, or a single site's limitations.
I use the word structurally deliberately.
I have been developing a way of thinking called StructuralTruth: the idea that any serious claim about a system should be expressible as:
invariants — what must remain true
violations — what must never occur
boundaries — where the claim holds
transformations — what is allowed to change
If you cannot express your "green" claim in those terms, you probably do not have a claim yet.
You have an aspiration.
The fictional data center is the test bed for applying that thinking to physical infrastructure.
The fictional project has a name: GreenM3DC.
M3 stands for the cubic meter — the fundamental unit of the space.
Everything I write in this series will be grounded in one question:
Does the claim hold?
Not does it sound right. Not does it appear in a sustainability report. Not does it support a nice rendering.
Does it actually hold, under measurement, over time, in real operating conditions?
That is the standard I am interested in. It is harder than it sounds.
Let's go.
Next: What does "green" actually mean? A structural definition that survives contact with reality.