The city kept two books: what the cloud would say, and what the ground would pay. Only one was balanced.
Compute has a physical metabolism, and the metabolism has a municipal account. Governance of the model currently stops at the property line of the building the metabolism runs in, and the failure is classification and sequencing, both doing exactly what they were designed to do, with the effect that the questions that mattered were outside the form and past the decision by the time anyone thought to ask. Nobody lied. The record simply cannot hold the question, and a record that cannot hold the question is indistinguishable from a world without one.
Two readings refused
Both easy readings deserve better than the strawman each side keeps handy.
The first is the prohibition reading: stop the build-out until a framework exists. It has a bill number in the United States, where a proposed moratorium on new construction would lift only once Congress has legislated that these facilities will not raise electricity costs or worsen environmental outcomes, and will not proceed without community approval. Those conditions are close to the ones argued for here, which is worth saying before disagreeing with the instrument that carries them. The instrument is where it fails. The facilities are running, an industry is already here, and a construction ban imposed now would relocate the load rather than delete it, to jurisdictions with weaker instruments and weaker review and weaker publics, taking the tax base with it. Every condition in that bill can be attached at the point of consent without a national prohibition to carry it, and a sequencing problem is fixed by resequencing.
The second is the ratification reading: digital infrastructure as self-evident national interest, assessment as legacy friction that a serious country waives on its way to the future. This one fails more quietly. A sector that wants to be treated as strategic infrastructure, and the sector does argue exactly this, reasonably, should expect the assessment standard of strategic infrastructure. That standard exists, it is mature, it was paid for by every heavy-infrastructure class that came before, and none of them was destroyed by meeting it. Waiving assessment is how a country shows a sector it is not thinking about it.
There is a tell in how much effort is now going into leaving the property line altogether. Orbital compute is argued by its own advocates partly as a route around grid queues, permitting and local objection, and the launch cadence required to put even a single gigawatt up there is of a different order from anything the launch industry has achieved. Proposals like that get taken seriously only when the constraint on the ground is real, which is confirmation of this week's subject arriving from an unexpected direction.
The working position
The unit worth governing is neither the model nor the municipality. It is the point at which a computational claim becomes a physical draw on a shared system: the ground address. Three properties make it governable there, and each corresponds to a failure this week documented.
- Classified against what it is, rather than what it resembles. The plant, not the warehouse basket; the campus, not the slice. The scoping decision is the assessment, so the classification is where governance actually happens, whatever the org chart says.
- Disclosed before the decision it is material to. Resource parameters at the rights stage, not the design stage. Deferral is a component of the decision, and scheduling a fact after its decision is a way of deciding without it.
- An answerable party, named before deployment, holding community-facing duties, located where the duties sit. The standard figure every other infrastructure sector was eventually made to designate, arriving in the building where nobody is currently home.
The leave-behind
The social chapter for this class of plant, short enough to act on without a board paper:
- A baseline whose affected area is drawn by shared system rather than site boundary. Receptors by claim, not by noise contour.
- Cumulative municipal load across all facilities, assessed together, because the city's pipes experience the sum.
- Employment intensity stated as a ratio against allocated resource, tested like any other claim: what evidence settles it, who agreed, in advance.
- The grievance route with a name on it, in the affected party's language and timescale, held by someone who can alter the load.
- Monitoring auditable by someone other than the operator.
Five lines. Nothing exotic, nothing the framework cannot carry, nothing that has not been standard elsewhere for a generation.
The archive arc inherited the question of what civilisation passes down. The answer this week is a transmission line, literally, and the accounts at both ends of it.
Read what the file cannot hold before you sign it. Including this one.
Companions
- The week in order: The Erf Number · Assessed as a Shed · Confirmed After Approval · What Would Count as Benefit · The Same Account · Not Our Building.
- The prohibition reading in its strongest form, with sponsors and conditions: the Artificial Intelligence Data Center Moratorium Act.
- The hostile read, extended to physical plant: Sixteen Days.
- The operational form of the position: the Interim Protocol.
- Next week: the answerable-party problem, everywhere.
These notes come out of Sociable Systems, a practice that reads AI-shaped documents the way a hostile reviewer will, before a lender or a court finds the gap. The argument has an operational form: the Interim Protocol sets out four rules for AI use in environmental and social deliverables, covering disclosure at touch-point grain, evidence custody, the phrases no automated screening may settle, and a hostile read before anything ships. Free, and written to be cited or retired once institutional guidance arrives.