Watermark.
All sites
Switch site 38 sites · 11 basins 8 open

Each site is one Watermark investigation. The page color says what opens; the campus line is the build on the ground — two different clocks.

MAU Maumee Basin 9 sites
2MI The Two Miamis 9 sites
SE Southeastern Basins 12 sites
NE Northeast Basins 8 sites
The page — what opens on Watermark Open · Draftfull record Queued · Watchingpreview page Restrictedrequest access
The campus — the build on the ground Investigating Confirmed Under construction Operational
All 38 sites — the network index →
Watermark · directory · the three hypotheses

One network, three open questions

The platform-level index now holds 38 sites · 11 basins. Each hypothesis asks one question about why the build-out is happening where it is, and carries a candidate answer that is under test — never a finding. The watershed thesis, where compute meets water and power, is the live reference build (Lima / BOSC); defense & federal-enclave and consumer surveillance are opening alongside it. For what a build-out does to a place rather than why it is there, the five lenses read the same network descriptively — and reach no verdict at all.

Not mutually exclusive — a single site can sit in all three. Lima (BOSC) is the worked example under each.

H1 · Water & Coercion Reference build
Is a town's acceptance compelled by its own Clean Water Act exposure?
Candidate answer under test Where discharge becomes leverage.

The original thesis: hyperscale compute lands where it can pull power and water, and a data center's intake, discharge, and downstream effects are basin facts. Sites nest by drainage — two divides, nine basins. Lima is the live, fully-assembled reference. A coercion sub-thesis (#903): in municipalities with declining populations, the receiving WWTP may be running lean on influent — below the biological-treatment minimum that keeps it in NPDES compliance. A datacenter's high-volume, consistent discharge provides the flow buffer the plant needs, structurally compelling municipal acceptance. The Clean Water Act is the backstop that makes the need non-negotiable.

Open the basin view — every site against the drainage › Read H1 as a wiki node — definition, related concepts, open questions ›
Two divides · eleven basins
Lake Erie drainage
Maumee 8 Portage 1 Sandusky 4 Cuyahoga 2
Ohio River drainage
Great Miami 7 Little Miami 2 Scioto 4 Muskingum 4 Mahoning 2 Hocking 3 Ohio Brush Creek 1
Cross-site scorecard

Every point, by drainage

Build phase, readiness tier, and facility status are three clocks — our progress on the site, the record it has assembled, and the plant in the ground — kept distinct.
SiteWatershed pointBuild phaseTierDocumentsRecordsFacility status
Tier and counts are read from each site's own exported bundle at build time. A dash means no bundle is committed yet — nothing measured; a zero means the export ran and the site carries none.
H2 · Defense & Federal Enclave Emerging hypothesis
Does the federal footprint — land, clearance, payroll, prime awards — determine where the compute lands?
Candidate answer under test Where the build-out meets federal land and the defense base.

A second reading: the same map tracks arsenals, air bases, federal research and the CHIPS build — enclaves where federal jurisdiction, clearance, and defense supply chains concentrate. Newly opened; most sites are not yet assessed, and a federal nexus is a signal, not a verdict. A capture sub-thesis (#1663): the enclave is not only geography, it is an economic structure — federal payroll and prime-award obligations concentrated in one county, land held by the United States and therefore off the local tax rolls, and the abatement / PILOT / public-benefit instruments layered on the ground around it. The reading it tests is whether the defense base *distorts* the local economy the datacenter then lands in, or merely sits beside it.

Read H2 as a wiki node — definition, related concepts, open questions ›
Assessment so far
Arsenals 3 Federal semiconductor 2 Defense supply corridors 1 Economic capture 0 Not yet assessed 32
H3 · Consumer Surveillance Emerging hypothesis
What is the compute for, and is the public subsidizing surveillance of itself?
Candidate answer under test What the compute is for, who it watches, and who's paying.

A third reading: the operators behind shell LLCs, the public-subsidy stack that pulls them in, and the capital and data flows the facilities sit on. The consumer-surveillance thesis — opening now, mostly under investigation, with Lima's abatement on record. An end-use sub-thesis (#904): these facilities are infrastructure nodes in a consumer surveillance apparatus — behavioral tracking, financial-transaction processing, or similar mass-scale surveillance of individual consumer activity, financed in part by the public subsidies the same communities provide.

Read H3 as a wiki node — definition, related concepts, open questions ›
Assessment so far
Operator 3 Public-subsidy signal only 2 Not yet assessed 33