Extension narrative · #233 · the workloads it will run
What the facility is for
The customer question is settled — the developer is Google
([verified]). This works one layer downstream: not who builds it,
but what it is for, and who can use it. The industry told an Ohio committee,
in its own words, that “data center” names four very different businesses — and they
answer the public's two plain questions, who benefits and who can use it,
in completely different ways.
Pick a type — read who can use it
The full table — every type, in plain text
The four businesses called “data center,” and what the Lima record establishes about each.
The developer is Google ([verified]); which model the campus is stays
[open].
Type
Who owns the compute
Who can use it
Evidence
Lima
Bitcoin mininga mine is its own customer
the operator — it mines on its own account
no one else — “we don’t have customers in Bitcoin”
[verified]MARA Holdings volunteered the distinction itself (closing session, 2026-06-04)
ruled out
Hyperscalethe owner runs the compute
the operator runs its own workloads (Google, Meta, AWS, Microsoft)
the owner’s own services and its global cloud customers
the tenants — the operator builds and powers the hall, others run the racks
the operator’s tenants, who need not be named on any public record
[verified]Vantage: “I do not know … passed through … or taken advantage by the tenants themselves”
[open]
Federal enclaveauthorized users only
a wholly dedicated, U.S.-citizen-staffed environment
only authorized federal users — FedRAMP, then DoD impact levels IL4–IL6
[verified]AWS named the Department of War and the CIA before the committee; the DoD CC SRG; Google’s air-gapped appliance holds IL5
[open]
Where this lands
Confirming the customer did not resolve the use. The record establishes the taxonomy and
the federal-enclave structure above it — but not which one the Lima campus is,
and not who can use it. Two of its silences are pointed: Google's own
legislative testimony omits Lima, and the records request for County ⇄ DoD / GDLS
communications returned “no records.” An absence is not a finding — it is the continued
absence of an answer.
This is the short, interactive version. The full report walks every claim to its
source —
the hyperscale-vs-colocation split, the “cannot say” abatement opacity, the FedRAMP /
DoD impact-level ladder, and why the answer changes the public-benefit math
.