The Logic of Power

Power, not compute, is the binding constraint on infrastructure at scale, and how that constraint is answered over the life of an asset, not only at procurement, is what separates the systems that stay adaptable from the ones that lock themselves in. This work is written for data center developers facing fast-moving markets. It treats sustainability as a set of options to be kept open across the life of an asset rather than a property fixed at the point of procurement, so that meeting the speed-to-power challenge now does not foreclose the better path later. The Logic of Power is one diagnosis with five facets. Each answers a plain question about building power infrastructure under that constraint. They are not a sequence to be read in order. They are five angles on the same problem, and each stands on its own.

The five facets

Power, Not Compute: what is the real constraint? The visible race in AI infrastructure is for chips and compute. The binding constraint is the power to run them. Power, not compute has been on a trajectory to set the limit, visible since at least 2016, and that is now the defining condition of the buildout. Read more‍

Speed to Power: why is it urgent? The gap between when a site is needed and when the grid can serve it is the live problem. Speed to power, the time it takes to energize a site, has become the variable that decides where and whether projects happen. Read more‍ ‍

Structured Transition Model: how do systems change? Power systems do not switch states cleanly. The Structured Transition Model sets out how a site moves from its current configuration toward a cleaner, more resilient one in sequence, as requirements and capital allow, rather than in a single step. Read more‍ ‍

Temporal Trilemma: why system design leaves time out. The familiar energy trilemma, security, affordability, and sustainability, has no time axis. The Temporal Trilemma adds it. The rate at which the answer has to change is now the dominant variable, and AI demand is pushing operators to regress on sustainability inside a single procurement cycle. Read more‍ ‍

Control Follows Assets: how do you build for it? The control architecture of a system follows from its assets, not the other way around, and because assets evolve, control is specified to the trajectory rather than the snapshot. This is where the diagnosis becomes a way to build and deploy a site. Read more‍ ‍

Where this goes

These five are the working parts of one argument. Take the power constraint seriously, and design for how it changes across an asset's life rather than the moment it is procured. Each link above goes to the full treatment.

Five Nines and Fast Power

Making better decisions in the age of AI

Questions and Answers