Extension narrative · #233 · the defense thread

What the corridor shows, and what it can't

There is a defense installation near the campus, the developer has the credentials to do defense work, and an industry witness told a state committee that hosting the government is a normal line of business. Each of those is true. None of them — alone or together — shows that the Lima campus does defense work. The map below holds both at once: the facts are real, and the gap between them is 5.5 measured miles of city, drawn but never crossed.

Three facts, one map — pick one and read what it does and doesn't reach

The three facts in plain text — and the measured gap

Each row is `[verified]`. None of them, and not their sum, is a connection — that stays `[open]`.
What's confirmed	What it actually is
The geography is real geo/jsmc.geojson · 5 parcels, owner UNITED STATES	The Joint Systems Manufacturing Center — the Lima Army Tank Plant, operated by General Dynamics Land Systems — sits 5.5 miles south of the campus, 5 contiguous parcels totaling ~384 acres, every one owned in the auditor's field by "UNITED STATES." It is on the parcel map. And it is only on the parcel map: a fact of geography, not a fact about the campus.
The capability is real relator testimony 2026-06-04 · DoD CC SRG · EO 14265	The developer is Google, which has achieved IL-6 — the DoD impact level for data classified up to SECRET — and runs an air-gapped Distributed Cloud at IL-5. Before the same Ohio committee, AWS named the Department of War and the CIA among its government customers, and the relator tied the timing to Executive Order 14265. Every word of that is a capability Google holds everywhere it operates. None of it is a fact about Lima.
Nothing in the record draws the line response-index.yaml item 2 — "No records"	Set the footprints down together and the temptation is to let 5.5 miles of city collapse into a connection. The method forbids it, and so does the record: there is no contract, no filing, no dated communication naming both. The public-records request for any County ⇄ DoD / GDLS communications came back "No records." Google's own legislative testimony did not name Lima at all. The gap on this map is the finding — measured, and empty.
The measured gap computed from geo/campus + geo/jsmc	Nearest parcels ~5.5 mi apart; centers ~6.6 mi. The JSMC footprint is ~384 acres across 5 US-owned parcels. The campus and the plant share a city and a corridor study area — not adjoining land.

Where this stops

A defense nexus is not a finding of this record. It is a question the record raises by what it contains — a federal plant down the corridor, a developer cleared to SECRET, a procurement order, an industry that hosts the CIA — and cannot answer by what it withholds. The honest end is the open one: one disclosable fact would close it, and it is the one the record doesn't carry.

[open] · the facility’s authorization posture What would actually connect this campus — or clear it?

the lock

No FedRAMP / DoD authorization record for the Lima facility appears in the corpus, and the public-records request for any County ⇄ DoD / GDLS communication returned “no records.” The IL-6 capability belongs to Google everywhere it operates; the posture of this facility is undocumented.

One disclosable fact would close it: the Lima facility’s FedRAMP / DoD impact-level posture, or a dated County ⇄ DoD / GDLS communication. Neither is in the record. Proximity is not connection — the gap stays measured, and empty.

response-index.yaml item 2 — “No records” · docs/defense-nexus.md

This is the short, interactive version. The full report walks every claim to its source — the IL-6 credential, the AWS testimony naming the Department of War and the CIA, Executive Order 14265, the relator's own framing of the thread as “likely speculative,” and why the “no records” response forecloses one avenue without proving the connection absent or present .

Read the full report →