Open investigation · Urbana, Ohio

Open leads

Every gap we're chasing on this site, in the open. Each lead is unverified inference until a source corroborates it — and every one traces to the corpus-completeness audit or a working hypothesis. Pick one up, answer it, or bring the document that closes it.

Submit a lead

open leads

withheld / sealed

under review

closed recently

2 open leads · unverified

Signal Under review [inference] watermark-directory/the-watermark-directory#447

Source Highland55 Urbana connection via primary instruments (recorder, ODOD, CRA/PILOT)

## Context **Highland55** is the only Urbana-specific data-center signal in the corpus, but it exists solely as a one-line entry in `docs/COURSE.md` (line 117) tagged **`[open]`**: *"Thor Equities / Thor Van Wert / Highland55 (Urbana, Van Wert); CyrusOne; Platon Investments / Dynamo Ventures … corridor `[open]`; no in-corpus document yet."* A repo-wide search confirms Highland55 appears in exactly three corpus locations — `COURSE.md`, and the prior Van Wert research run's `findings.md` and `manifest.yaml` — never in a primary instrument or extraction. The site profile's `facility` field is `None` `[open]` (sites.py line 1674) and `facilityStatus("urbana") = "investigation"`. The `self-research` step that would have generated data-center seed proposals **errored** (`1 validation error for ProposalDrafts`), so the inferential entity layer is also empty. ## Acceptance Criteria - [ ] At least one primary instrument is ingested and extractable via `list_documents` for `urbana` or `champaign` — acceptable forms: Champaign County Recorder deed, ODOD/JobsOhio announcement, CRA/PILOT agreement, NPDES application, or zoning instrument tied to Highland55 or a Thor Equities entity. - [ ] **Or**, if no instrument is found after a documented search effort, Highland55 is formally retired from the Urbana register in `COURSE.md` and `sites.py` with a `[not found – retired YYYY-MM-DD]` tag. - [ ] The Highland55 register is kept **separate** from the Allen-County/Lima Bistrozzi land-assembly graph (no cross-reference unless a filed instrument bridges them). --- _Proposed by `bosc onboard urbana --research` (Phase 5; onboard-urbana-urbana-data-center-activity-recei-2026-06-21). Sub-issue of #441 / epic #440._

2026-06-28: Instruments read (10 docs, PR #803). Thor Equities (Urbana Owner I LLC) confirmed as developer; 47.6+ ac west of US-68; project includes electrical substation + build-to-suit for 'Vance Brands' (end use [open]). See data/extracted/urbana/highland55-findings.md. #447

Help confirm → GH-447

Open question Under review [inference] watermark-directory/the-watermark-directory#448

Pin Honda 'Champaign-area' data center to a parcel or filing, or downgrade to corridor context

## Context `data/entities/profiles/cloud-consumer-candidates.yaml` (lines 282–290) lists **Honda of America** as a tier-4 candidate with location **"Marysville / Clark / Champaign area"** and `confirmed_cloud_relationship: own Ohio data center (announced/investing)`. This is an **analytic candidate profile built for demand-fit screening** — not a deed, permit, or filing — and its location string spans three counties (Union/Clark/Champaign) without pinning to Urbana or Champaign County specifically. The findings classify it as **`[inference]/[open]`**: corridor context, not a documented Urbana project. The profile's manufacturing LQ of 4.14 and the Honda/Marysville corridor adjacency are consistent with the site's economic character, but treating an unanchored three-county candidate profile as a Urbana data-center instrument would be the inference-as-finding error the BOSC methodology explicitly prohibits. ## Acceptance Criteria - [ ] A primary instrument (announcement with a specific site address, county recorder filing, utility interconnection application, or OEPA/air permit) is identified that pins the Honda data-center investment to a specific parcel or jurisdiction. - [ ] If the instrument places it in Champaign County/Urbana: the candidate profile is upgraded to `[verified]` and a source document is ingested. - [ ] If the instrument places it outside Champaign County: the `cloud-consumer-candidates.yaml` entry is updated to reflect the correct jurisdiction and removed from Urbana's investigative register. - [ ] If no instrument is found after a documented search: the entry is downgraded to `corridor_context: true` in the YAML and excluded from Urbana promotion criteria. --- _Proposed by `bosc onboard urbana --research` (Phase 5; onboard-urbana-urbana-data-center-activity-recei-2026-06-21). Sub-issue of #441 / epic #440._

Downgraded 2026-06-28: no primary instrument found pinning Honda investment to Urbana/Champaign County. cloud-consumer-candidates.yaml updated with corridor_context: true. Excluded from Urbana promotion criteria. #448

Answer this → GH-448

Showing all 2 open leads. Closed leads move into the record →