How we source
GridFreeze reads the primary public record — the places where data-center development is actually decided — and publishes only what that record supports. Every signal links to the public document it came from. This page explains what we follow, what a published signal requires, and what we never do.
What GridFreeze follows
- County boards of supervisors and planning commissions.
- Zoning, rezoning, and special-exception records.
- Public meeting packets and proceedings.
- Verified grid-planning and transmission records relevant to data-center load.
What every published signal requires
- An identifiable jurisdiction.
- A traceable public source, with its URL attached to the signal.
- A verified description of what changed.
- A publication or detection date.
- Ambiguous fields are omitted or flagged for review — never guessed.
What GridFreeze does not do
- Present rumors as projects.
- Infer a data center from an unrelated generation-queue entry — grid-generation items are always labelled as context, never as data-center load.
- Call transmission-planning records an official “data-center queue.” They are transmission projects driven by data-center load, and we say so.
- Invent missing fields.
- Publish realistic-looking mock rows as live data.
Freshness
Sources are scanned on a recurring schedule, most on a daily cycle, and the weekly brief is compiled from what those scans verified. Signals are published when they are detected and verified, not in real time. The most recent completed source scan finished Aug 21, 2026.
How fast
We alert the day we detect a matter. Over the last 60 days detection ran a median of 2worst case of 14. Speed varies by source, and every alert prints its own measured lag so you can check it. Next business day is the engineering target.
Every alert email states two dates, when the source published and when we detected it, so each one reports its own lag rather than asking you to trust a claim. There is a design limit worth knowing: a county agenda feed lists a meeting only on the day it happens, so roughly one day is the fastest this approach can be. Anything quicker would mean reading each county's own website directly, which we have not built.
Corrections
If a signal misstates what the record shows, or a source link is wrong, email gridfreeze@shaachi.com with the signal and the correct record. Corrections are reviewed against the primary source and fixed in the live data.