What changed.
What remains open.

October 4, 2026 · Prosper hearing status

Issue: Our calendar, tracker and newsroom described the September 8 hearing as upcoming or pending after that date had passed. The city directory still presented the proposal without a follow-up status.

Evidence: The Town’s hearing notice and September 8 agenda establish the scheduled hearing. CBS reports withdrawal on September 8. We have not retrieved a direct town outcome announcement or approved minutes; a hearing notice alone cannot establish an outcome.

Action: Archived the date and updated the affected calendar, tracker, historical newsroom item and directory to point to this record. We do not describe the P&Z recommendation as a final council denial.

Status: Outdated future wording corrected; primary outcome confirmation remains open. Next manual check target: October 11, 2026.

Town September 8 meeting and agenda route ↗ · Town September 8 agenda ↗ · CBS · September 8 report ↗

October 4, 2026 · Prosper outcome gap resolved

Evidence: We retrieved the Town of Prosper’s notice graphic from its original social-media asset, located through an indexed @Town_of_Prosper post. The Town’s website identifies that account as official. The notice identifies the September 8, 2026 session and says the applicant withdrew both Tomahawk items, closing the current proposal. It specifies a new application, notices and P&Z hearing for a revised plan.

Action: Updated the tracker, calendar, directory and historical newsroom follow-up to “Withdrawn · Town notice.” The earlier unresolved assessment above is retained as history. The old hearing-notice URL returned 404 in this check; working town meeting/agenda routes replace it.

Qualification: The notice numbers the items 20 and 21; the retrieved September 8 agenda numbers the rezoning and plan amendment 19 and 20. The notice explicitly names Tomahawk and case ZONE-26-0007, so we preserve that numbering discrepancy without inferring a council denial. Approved meeting minutes and the exact social-post permalink were not retrieved. This resolves the notice-based withdrawal question, not any future application status.

Status: Current proposal withdrawal verified from the Town notice. Check for any new application separately; next manual review target October 11, 2026.

Town outcome notice · original media file ↗ · Town official-account directory ↗ · Town meeting and posted agenda ↗ · Town planning records and contact ↗

October 4, 2026 · Abilene schedule and training intake

Issue: A mid-2026 Phase 2 target appeared without a completion qualification. The training section described TSTC’s course without identifying its historical March intake.

Evidence: DPR’s project page and Crusoe’s March 27 announcement give different targets. TSTC’s February 11 announcement describes a March 2026 start.

Action: Replaced the isolated schedule headline, added a dated project evidence ledger separating the original campus and additional development, and labeled the TSTC intake historical.

Status: Wording corrected. Actual later building completion and next training intake remain unverified; next manual check target October 11.

Project sources and conflicts → · TSTC · February 11 announcement ↗

October 4, 2026 · Haskell County status and project separation

Issue: The previous town record stopped at an announcement-stage summary. It did not reflect Google’s June construction report or distinguish the separate Crusoe-linked County agreement.

Action: Added a dedicated local guide, dated original sources and separate project evidence. Adjacent energy capacity is not counted as data-center IT load.

Status: Coverage updated. Intersect’s narrative and status field conflict on Quantum operations; later compute completion, vendor-workshop availability and recipient confirmation remain open. Next check target October 11.

Original sources, discrepancy and review limits →

October 4, 2026 · San Angelo scope and projected scale

Issue: The city directory described a six-building campus without the City’s application qualification. The local overview needed a clear boundary between adopted rules, developer projections and a filed project.

Action: Replaced the directory scale claim with the City’s within-city-limits application status, dated the source review, added participation/training pathways and kept June incentive information historical.

Status: Wording corrected. A later executed agreement, project-specific vacancies and measured benefits remain unverified. The strategic concept sections were preserved and not re-audited. Next check target October 11.

City evidence and limits →

October 4, 2026 · Opportunity follow-up qualifications

Evidence: TSTC’s June report records a historical 15-week cohort; its current general program page describes 12 weeks. Howard College’s linked interest form includes a 2025 BuildSafe course and other dates without a year. An older Google Haskell technician URL returned “Job not found.”

Action: Added a dated register with separate enquiry, visible listing, qualification and interest-form labels. Excluded the unavailable technician role from actionable listings. Connected town, jobs, training and vendor pathways to these records.

Status: New intake seats, date details and future vacancy availability remain unverified. Forms were read, not submitted. Next manual check target October 11, 2026.

Inspect original sources and qualifications →

October 7, 2026 · ERCOT voluntary RFI request deadline

Issue: The newsroom listed October 4 as the voluntary participation-request deadline for newly substantiated 25–75 MW data-center loads.

Evidence: ERCOT’s September 24 market notice sets the request deadline at October 5, 2026 and the completed-response deadline at 5 p.m. Central on October 12, 2026.

Action: Corrected the request date, refreshed the verification date and replaced the generic resource link with the exact ERCOT notice.

Status: Corrected from the official record. The October 12 response deadline remains upcoming.

ERCOT · September 24 market notice ↗