A filing, statute, agency record, map, or dataset published by the responsible public body.
Methods & corrections
A public position can still use disciplined evidence.
The Observatory is not neutral about Pacifico Cedar Creek at this location. It is rigorous about what the record proves, what remains an assertion, and what evidence could change a conclusion.
Two dimensions
Source type is not claim status
An applicant statement can appear inside an official government filing. The source is official; the underlying assertion is still the applicant’s.
A statement about what an official record contains. This does not independently prove every underlying applicant assertion.
A fact, forecast, description, or claim made by the applicant and represented accurately here without automatic adoption as fact.
A modeled outcome based on assumptions. It is not a guarantee of future jobs, taxes, earnings, or spending.
A calculation or comparison performed by the Observatory from cited source data.
A technically supported conclusion that remains subject to project-specific evidence and can be revised.
A question worth investigating, not a proven condition. It is paired with the evidence needed to test it.
Claim lifecycle
How a conclusion enters the public site
- 01
Acquire the source
Record publisher, date, version, URL, and project linkage.
- 02
Index exact support
Create page-level findings before turning a long filing into a public claim.
- 03
Classify the claim
Separate applicant assertion, record content, cross-check, inference, and hypothesis.
- 04
Name the next evidence
A conclusion is stronger when the public can see what would confirm, narrow, or overturn it.
- 05
Publish corrections visibly
Material changes are dated and explained rather than silently overwritten.
Corrections log
The record changed here
These entries reconcile the earlier public prototype, repository v4, Supplement 1, and the live primary record.
Gas-turbine siting record expanded
The Cedar Creek dossier now explains the air-pollution, low-frequency noise, fire and fuel-system, waste-heat, and operating-duration questions created by a 710 MW simple-cycle gas-turbine facility beside homes and schools. These are documented technology characteristics and required studies—not claims that unmodeled project-specific impacts have already been quantified. REQ-001, seeking the complete TCEQ air record, was submitted by email on July 26.
Location case and resident action center expanded
The site now states the evidence-based site-suitability conclusion directly, adds statewide air-permit precedent without attributing unproven conduct to Pacifico, reviews the July 27 county tax-abatement draft, summarizes the proposed Bastrop Bill of Rights, and publishes verified meeting, contact, records-request, TCEQ, legislative, and JETI action routes.
Amazon and EdgeConneX tract extents corrected
The GIS map replaced the earlier undersized ownership snapshots with CAD-derived site boundaries supplied from Bastrop CAD ParcelARI data fetched July 23, 2026. Amazon is now shown as an approximately 1,300-acre union of 24 former CTX/Creekside parcels. EdgeConneX-related mapping now separates AUS01, AUS02, the 179-acre Campus 2 tract, and the full 704-acre Campus 3 host parcel; Campus 3 is dashed because its approximately 400-acre project footprint has not been filed.
Drought and fixed fire-service facilities added
The GIS map added the live weekly U.S. Drought Monitor layer and seven Bastrop County ESD No. 1 station sites from Texas FireConnect. The project area is classified D2 Severe Drought on the map valid July 21, 2026. FireConnect lists seven sites across a 395-square-mile response area but does not verify staffing, apparatus, response time, water supply, or industrial-fire capability at each station; the map now makes that distinction explicit.
Community proximity layers added
The GIS map now shows 5,701 anonymized residential address points within three miles of Pacifico’s filed perimeter, schools and childcare, farms and agricultural sites, and public community places. All household names, street addresses, ownership fields, and resident-submitted locations were removed. Public-school campuses are cross-checked against Bastrop ISD; other public-facing facilities remain labeled as reference locations pending record-by-record verification.
Corridor parcels and fire controls corrected
The GIS map added current county parcels for EdgeConneX/DFW and Amazon Data Services, changed distance lines from center-point circles to offsets from Pacifico’s filed perimeter, and replaced fragile browser requests for the 2011 and 2015 fire layers with county-published geometry stored in the site.
Pacifico tract geometry corrected
The map now treats the eight property IDs listed on J0049 page 7 as the filed Pacifico project area and reconciles them to county GIS polygons. Supplement 1, Figures 2–3, depicts the same proposed-project boundary. The tract descriptions total 2,810.0553 acres, while the applicant narrative says approximately 2,842 acres.
Legal correction recorded
The Observatory corrected the earlier suggestion that dispatchable generation may be exempt from the JETI compelling-factor requirement. SB 2322 did not become law.
Supplement 1 indexed
Twelve page-level findings were added, including the project-scope change, Ohio alternative, and revised economic projections.
Owner records corrected
EDCAUS11 and EDCAUS12 now identify Burr Computer Environment Inc. as the TDLR owner of record; any other relationship remains a separate research question.
FM 535 cluster expanded
AUS02, EDCAUS11, and EDCAUS12 are tracked separately and analyzed cumulatively.
Most consequential correction
SB 2322 proposed the dispatchable-generation exemption; it did not enact it.
Current §403.609(b)(3) and the Comptroller’s current FAQ still state the compelling-factor requirement.
Privacy
Residences are context; residents are not identifiers
An anonymous public address-point pattern can show community proximity without publishing a household’s name, street address, ownership, contact information, or private submission.
Public: official parcels, filed project locations, agency records, public infrastructure, named public facilities, aggregate counts, and residential points stripped to coordinates only.
Protected: resident names, street addresses, ownership, contact details, private submissions, and any tooltip or export that could identify a household.
Anonymous site analytics: the Observatory counts page views, browser-level visitors, sessions, referrer hostnames, active-page time, device category, and approximate city, region, and country. Raw IP addresses, exact coordinates, search queries, form contents, and private submissions are not stored in traffic analytics. Browser Do Not Track and Global Privacy Control signals are honored.