AI Buildout PermitsAdd to Claude

Methodology

One row per data-center project, one dated event each time a public record moves it. Every field carries its source.

First seen

Each source is read daily by a scheduled job. A field that changes closes its old value and opens a new one dated that day; nothing is overwritten or deleted. A project that drops off a list gets a "delisted" event. Events already in a source on the day we first read it carry their record date and are marked backfilled, so the history never claims we saw something earlier than we did. First crawl dates: EPA air-permit registry: 2026-11-20; Virginia DEQ air permit: 2026-11-20; Air-permit document: 2026-11-20; Minnesota DEED list: 2026-11-20; City / county agenda: 2026-11-20; EIA-860M generators: 2026-11-20; Texas Comptroller certification: 2026-11-20.

Tickers

Each named party is matched to an ultimate parent by a dated rule: alias when the parent's own brand is in the name, curated when a public fact ties them (the note says which), ex21 when the exact name appears in the parent's 10-K Exhibit 21. Each link carries its method and confidence. Private parents are marked private. A link says a name belongs to a parent; it is not an ownership share.

Numbers

Every number comes from the source text: a cell, a field, or a line quoted next to it. No model supplies or estimates a number. Counts and sums are arithmetic on stated values. A missing value is shown as "not in record".

People

Rows are about projects and companies. A person appears only in a business role from a government record. No home addresses. Staff names in agency feeds are dropped.

What isn't used

CivicPlus and BoardDocs agendas (their terms bar this use), interconnection queues outside ERCOT and CAISO, procurement portals, deed owner names, and any site whose robots.txt or bot checks say no. Virginia's issued-permit page blocks scripts, so its issue dates are not included; DEQ's own published map feed is.