A reviewed change log connects a dated document to the field it changes, the implication and the next record to check.
By Yaro Korets · Published · Source dates are stated below
This edition contains 8 interpreted entries, reviewed October 27, 2026 and ordered by event date. It includes retrospective milestones and filing metadata explicitly marked where document contents remain unread. Collection dates do not establish new physical events.
Socrates South files a Condition 12 notice and STY a Condition 15 notice, each labelled 2026 Q3. These are the only October 26 records in the exact 44-row intake; the other 42 were filed earlier.
Why it matters
The notices are follow-up leads. Their titles establish neither a change of operating status nor the outcome of complaint reporting.
What is still unknown
The PDFs remain unavailable for content review. Complaint counts, compliance findings and equipment changes are unestablished. Three other entries in the batch are explicitly confidential targets.
Next check
Read the public report files when access is available; retain the current source-backed project statuses meanwhile.
Crusoe reports construction underway after a June 2025 groundbreaking. Its release distinguishes operating Goodnight 1 from Goodnight 2 still under construction.
Why it matters
Track the campus, wind phases and shared grid connection separately. The wind ratings do not establish continuous supply or current computing load.
What is still unknown
Current delivered power and final disposition of the related PUCT rehearing remain unestablished here.
Next check
Check subsequent PUCT 59220 orders and wind-phase completion records.
The TensorWave announcement defines 222 MW of total facility power for the first phase, with phased delivery beginning in the second half of 2027. Expansion rights beyond 650 MW are separate options.
Why it matters
A customer phase is more specific than the 17 GW campus ambition. Keep the phase's power basis, delivery window and conditions together.
What is still unknown
The announcement does not establish fulfilment of financing and guaranty conditions, delivery or current operation.
Next check
Track subsequent disclosures against the 222 MW phase and the stated conditions.
The regulator’s September 17, 2026 table places case 25-0185-EL-BLN in its operational BTM category at 200 MW, with an August 3 operational date. This finding comes from a separately reviewed official status report, not the unread October filing.
Earlier evidence and the source-backed update
Field
Before
After
Documented project stage
Construction authorized June 9, 2025
Listed operational from August 3, 2026 in the September 17 table
Why it matters
An official operating listing supports a stronger project stage than the old construction authorization. The 200 MW gas-capacity figure excludes battery storage.
What is still unknown
Current metered output, delivered IT power and individual unit availability remain unknown.
Next check
Reconcile equipment and commissioning records; read the October Q3 report.
OPSB’s status table dates approval to June 25, 2026 and marks the project under construction as of September 17. Its June 26 announcement describes 250 MW gas generation, 116 MW battery storage and 36 conditions.
Earlier evidence and the source-backed update
Field
Before
After
Approval date basis
June 26 announcement date used in the older archive
June 25 approval date in the regulator table; announcement published June 26
Gas-capacity reporting basis
Older uncited BTW event: 296 MW turbines
Official OPSB table and announcement: 250 MW project gas capacity; technical-rating reconciliation pending
Why it matters
This corrects the stated source and capacity boundary. It does not establish a physical 46 MW reduction. Battery power and gas generation remain separate quantities.
What is still unknown
The 296 / 250 MW technical basis, current commissioning state and battery duration remain unestablished.
Next check
Read public narrative, staff report and amendments; seek in-service evidence.
O4721 adds a dated federal operating-permit milestone to the Longhorn / Abilene DC 1 record. Keep it distinct from the earlier NSR registration and modification.
Why it matters
Authorization progressed in the documentary record. Issuance does not measure the operating state of each unit or delivered IT power.
What is still unknown
Current output and the exact first day of BTM generation are not established by issuance.
Next check
Seek dated commissioning and operating evidence for each equipment cohort.
Blue Energy and Crusoe announce a proposed pairing after the port's option-agreement report. Initial gas-bridge power as early as 2028 and nuclear generation by 2031 are developer targets.
Why it matters
Track site control, gas generation and nuclear licensing as separate milestones. An option agreement is not a licensed power plant.
What is still unknown
Current option exercise, final site boundaries, permits and updated delivery dates remain unestablished in the reviewed sources.
Next check
Look for port decisions and project-specific air and NRC records before upgrading the development status.
The 177263 modification review describes fewer turbines and a longer LM2500 permitted-hours envelope. It was received January 11 and approved January 22, 2025; the original application dates to August 15, 2024.
Earlier evidence and the source-backed update
Field
Before
After
LM2500 count
6
5
Titan 350 count
6
5
LM2500 annual permitted hours per turbine
5,880
8,760
LM2500 site rating
Reduction described; earlier rating not reproduced
34.1 MW per turbine
Titan 350 site rating
Increase described; earlier rating not reproduced
38 MW per turbine
Why it matters
Use the amended five-plus-five configuration for this permitted cohort: 5 × 34.1 + 5 × 38 = 360.5 MW. Preserve six-plus-six as history rather than adding both versions as separate equipment.
What is still unknown
Permitted hours are not actual run hours, and site-rated MW are not metered delivery to computing.
Next check
Match subsequent filings to Abilene DC 1 / Longhorn and keep commissioning evidence separate from authorization.
These events have a source URL and an existing published facility dossier. They refresh with site exports. Review events describe a check; they do not necessarily establish a physical change. Unreviewed collector candidates never appear here.
Oct 27, 2026 · record reviewed
Checked Shelby County public notices and its October 6, 2026 notice; that notice contains no CTC/xAI update. The published 15-unit, 247.5 MW cohort remains a historical reported configuration; current installed count and delivered power were not established by this check.
Reviewed final MDEQ permit 0680-00119, issued March 11, 2026, and the current registry. The permit lists 41 turbines in three groups (17, 16 and 8). The separate 27-unit, 495 MW cohort comes from a historical court filing; it is not a current full-site operating total.
Reviewed TCEQ records: original registration 177263 application received August 15, 2024; amendment issued January 22, 2025; Federal Operating Permit O4721 issued January 16, 2026. The 360.5 MW equipment cohort is a permit-based figure, not verified current output. Exact first-power day remains unverified.
District court Doc 135 allows the United States to intervene but rejects unilateral dismissal of NAACP v. xAI/MZX Tech. The order addresses intervention and dismissal, not whether the defendants violated the Clean Air Act or how many turbines are operating.
Crusoe reported that the first Abilene phase was running on Oracle Cloud Infrastructure and that its first two buildings had been energized within a year. This establishes operation by the report date, not an exact first day of BTM generation.
TCEQ original technical review records August 15, 2024 as the project received date for registration 177263. This corrects the legacy August 1 date; January 11, 2025 relates to the later modification application.
Collect a public record and preserve its identity and date.
Review the project, phase, evidence basis and affected fields.
Publish the supported finding with source links, interpretation and unknowns.
The interpreted entries above are a manually reviewed edition. Filing metadata is distinguished from completed document-content review. The published-event section updates from the mirror; interpretation is not published automatically from every registry hit.