In 2021, a newspaper asked a small Oregon city a small question: how much water does Google use? The city's answer was to sue the newspaper. Not Google — the city. The Dalles took The Oregonian to court to keep its largest water user's consumption a secret, and Google quietly funded the fight with more than a hundred thousand dollars. Thirteen months later the city surrendered, and the number came out: the data center campus was drinking more than a quarter of the entire city's water — in a county that has known extreme drought — and by last year the share had climbed toward forty percent, while the campus sat on hundreds of millions in tax breaks.
Hold that story to the light, because every gear of the machine is visible in it. A public resource, privately consumed. A local government defending the corporation against its own citizens. Secrecy as the factory setting. And a town that only learned the truth because one reporter refused to accept a form letter dropped into a void.
The newest complex
My last essay, The Machinery No God of Love Would Build, traced the shape of this machine in its older forms — the military-industrial complex, the psychiatric-industrial complex, the family-court complex: constructs no God of love would build, and none of them requiring a villain to run. Nobody conspires. Everybody just does what their position rewards.
Now watch the newest one assemble itself in real time. Call it the compute-industrial complex. There is no room where anyone decided your power bill should climb to finance a machine you will rent your own thinking back from. There is a utility planner rewarded for load growth, a county assessor rewarded for ribbon cuttings, a site consultant rewarded for the nondisclosure agreement, a council that signs before the town knows there was anything to sign. Each of them doing the ordinary, rational thing. And the sum of all that ordinary self-interest is the largest private construction project in American history — gigawatt campuses announced by the month — with the bill arriving where bills always arrive: at the household meter.
The mechanics are simple and damning. Under most state regulation, the cost of new power plants and transmission lines is socialized — spread across every ratepayer — unless an explicit rule says otherwise, and for most of the country no such rule exists. So when a campus lands that draws as much electricity as a small city, the substations and gas turbines and capacity payments fold quietly into everyone's bill. By one recent accounting, data-center-driven grid costs have already added roughly $23 billion to the public's electricity bills. Residential rates are up about forty percent since 2021. Utilities asked regulators for $31 billion in increases last year and another $9.4 billion in just the first three months of this one. A retiree in Manassas, Virginia opens a January bill triple his usual and cannot point to one thing in his house that changed. Nothing in his house did.
And here is the same tell I named in psychiatry — the Treatment Prevention Paradox, now wearing a hard hat. The spend goes up and the promised relief never arrives. Hundreds of billions poured into the machinery of intelligence, and what does the household receive? A higher bill, a deeper dependence, and a subscription. In any other industry, spending and suffering rising together would read as failure. Read it as design and it resolves: a complex that made you self-sufficient would lose you. Misalignment is the product here too — only now it is measured in kilowatts and monthly renewals, and the crop being farmed is the household itself. In the economy we are walking into, whoever administers your attention administers you; this buildout is the physical consolidation of that administration, poured in concrete at a thousand acres a pour.
A household that can think and power itself is a terrible customer. That is why no one is subsidizing yours.
An honest word before the blueprint
Let me concede what honesty requires, so none of this can be dismissed as smashing looms. Training a frontier AI genuinely needs scale; a purpose-built hall computes more efficiently than a million scattered closets, and the open models a household runs were born in exactly such halls. You own the mill, not the seed stock — and that division of labor is fine. Nor are data centers the sole culprit of your rising bill; aging grids and equipment costs carry their share of it.
So the demand is not demolish the cathedral. The demand is narrower and therefore stronger: no more cathedrals raised on our subsidies, our water tables, our rate base, and our silence — while the household is priced and permitted out of standing on its own.
Call the strategy by its honest name: fight big tech with big tech — or more precisely, with big tech's own artifacts, carried home. The open model was born in their hall; the panels rolled off their supply chains; the shelf-sized computer is cheap because their volumes made it so. We are not refusing the technology. We are refusing the tenancy. Same silicon, opposite geometry: theirs concentrates, ours distributes; theirs meters, ours belongs. And fight big government the same way — with its own procedure: the docket, the deadline, the response compelled onto the record, every instrument the machine perfected turned back on the machine.
But the measure I set last time still governs: the honest measure of a good tool is whether it helps you need it less. The cathedral fails that test by design — it is built to be needed more tomorrow than today. Which means protest alone is not the answer. The answer is to build the tool that passes the test, in copper and glass, on your own property. People imagine that requires a server farm and an engineering degree. It requires neither. Here is the whole thing, in plain terms.
The sovereign property, in plain terms
Picture two half-closets. One thinks. One powers. Together they are the entire counter-machine.
The whole loop, on one page:
lights, heat, the dryer
No warehouse. No subscription. No one on the other end. A property that generates its own power, keeps its own records, and does its own thinking — which is to say, a household restored to the condition the complexes exist to prevent. And it passes the good-tool test: everything in that loop is built to do its work and get out of the way. Nothing in it is designed to keep you staring at it.
The how This essay is the why. The full engineering build — hardware tiers, model serving, the records vault with retrieval, a bounded agent loop, and the power math to keep it running — lives in a companion field guide I wrote for DevForge Academy: The Half-Closet Server. Read this one for the stakes; read that one to spec, build, and govern the node on your own shelf.
What it costs, honestly. The thinking half is used-car money — four to ten thousand dollars for the shelf and the cabinet, and it is the right place to start. The power half is the expensive half: a full roof and wall runs into the tens of thousands, less wherever state rebates survive. And mark what just happened to that price. Last December 31, the federal thirty-percent credit for household solar and batteries was allowed to die — terminated seven years ahead of schedule by last summer's budget law — while the cathedral's abatements rolled on untouched. The hyperscaler gets the ledger; the household gets the sticker. That is not a market outcome. It is a policy choice — and policy choices are exactly what petitions exist to reverse.
The clerk needs a constitution
An honest reader will spot the gap in the blueprint. A raw AI model on a shelf is a mind, not an institution. Left ungoverned it is a very fast intern — eager, tireless, and unaccountable, with no procedure and no memory of what was decided last week. And the complexes do not beat citizens with intelligence; they beat them with procedure — the docket, the deadline, the form filed in triplicate, the record they keep and you don't. So the counter-machine needs procedure of its own. That is the software half of sovereignty: the part that keeps the record straight, drafts to a standard, checks the work before it counts, and leaves a trail a clerk or a council must respect.
That is what SQUEIL is being built to be: a sovereign Property OS — an operating system for running your affairs on your own property, under your own record. In plain terms, it is a bench of specialized clerks with a constitution over them. A Canon holds the record: what is true, what was decided, by whom, and when. A Forge drafts — the petition, the demand letter, the document, the code. An Arbiter inspects every draft against the rules before it is allowed to count. A Worker executes only what survived inspection. And a Coronel conducts the bench, so the work moves in order instead of in chaos. Over the whole of it sits the SPEED Methodology: the standing discipline that nothing changes — not a document, not a decision — without being proposed, examined, and ratified on the record.
Notice what that is. It is this article's own petition standard turned inward: one matter, one examination, one response on the record. SQUEIL governs itself by the daylight this essay demands of government — every decision ratified, every change traceable, secrecy structurally impossible rather than merely discouraged. I will not ask the state to live under a discipline my own machine does not.
And it is not a pitch deck. The founding tenant is my own exterior-cleaning company here in Salem — real ledgers, real weather, real customers with real roofs. The software earns its sovereignty claims on invoices before it asks anyone else to trust it with theirs. From there the same bench scales in both directions: down to the shelf in your hallway, where the clerk runs under a constitution instead of a subscription — and up to the civic layer this essay has been arguing for, the dashboards and routed petitions and records no functionary can quietly lose. The design intent is the good-tool test made structural: tools you own, data on your side of the doorkeeper, and a success metric that points out the door. The tenant who needs the platform less every quarter is the platform working.
The petition, clause by clause
What follows is written to be lifted verbatim — into a public comment, a council testimony, a letter to a legislator. Six clauses. Take the one that fits your venue.
Where to file it
A petition that doesn't route is a prayer addressed to no one. So here is the routing table, in ascending order of difficulty.
And whatever the venue, write it the way power respects: one office, one clause, one deadline, and a demand for a response on the record. Not a signature drive into the void — a filing a named official must answer or be seen refusing to. This is the Year 2 milestone from the reconstruction map made literal: the clerk on your own shelf can draft the filing in minutes. Use the machine's medicine on the machine.
The signature they can't ignore
File the petitions. Then cast the one vote no clerk can misplace: build the loop. Every roof that harvests, every wall that remembers, every question answered inside your own four walls is a signature renewed hourly on the meter — one household subtracted from the crop. Voice and exit together: the petition asks the complex to stop; the property makes its answer matter less either way.
And notice this is the reconstruction map from my last essay, made physical. Illuminate — drag the water numbers and the subsidy ledgers into daylight, the way one reporter did in The Dalles. Equip — put the shelf, the cabinet, the roof, and the wall inside the home. Engage — the docket, the council chamber, the response on the record. The power doesn't vanish. It migrates — from the cathedral to the kitchen, year by year, clause by clause, roof by roof.
Then go stand in the sun
Because no god of love would build a machine that drinks a town's water to sell the town its own thoughts back. But love's blueprint was never in the machine — it is the whole world outside it, and that world comes provisioned: a reactor already hung in the sky, a roof already fitted to catch it, faces already in the room. So let the clerk carry the paperwork the complexes pile on you. Let the roof carry the load the cathedral wanted metered. File the paper, seal the loop — and then set the device down and walk out into the light you now own twice: once as kilowatts, once as liberty.
Sources & Further Reading
- Oregon Public Utility Commission, approval of Schedule 96 under HB 3546 (the POWER Act) — creating a separate rate class so data-center loads don't raise household bills. oregon.gov/puc
- Oregon Capital Chronicle, coverage of the POWER Act's passage (June 2025) — the >20 MW rate class and what it exempts. oregoncapitalchronicle.com
- Reporters Committee for Freedom of the Press, on The Dalles' reverse public-records lawsuit against The Oregonian and its settlement. rcfp.org
- Latitude Media, on Google's disclosed water use in The Dalles — roughly 550 million gallons, nearing 40% of the city's consumption (June 2026). latitudemedia.com
- Fortune, on the estimated $23 billion in data-center-driven costs already added to public electricity bills (July 2026). fortune.com
- Consumer Reports, on household impacts, the 300+ state bills introduced in 2026, and the nonbinding White House ratepayer pledge. consumerreports.org
- Congressional Research Service, on the repeal of the Section 25D Residential Clean Energy Credit for expenditures after December 31, 2025, under the FY2025 reconciliation law. congress.gov
- Office of Rep. Mike Levin, introduction of the SHIELD Act — a federal large-load cost-allocation standard (January 2026). levin.house.gov
