Only the field-level records marked rights-cleared in rights-manifest.json receive the published CC BY 4.0 grant. Linked source documents and reference-only records retain their own rights. No record is currently in the licensed-core subset.
The national directory snapshot is adapted from Compute Atlas by Edward Kubiak under its own CC BY 4.0 license. Its rows are not DataCenterData findings, never enter reviewed counts, and are identified by their own layer and provenance fields. The deployed immutable-ID ledger and source manifest travel with the same atomic release.
Core indexes
- registry.json — Stable IDs, aliases, record units and canonical page links (218 rows)
- licensed-directory/snapshot.json — Third-party licensed discovery rows, kept outside reviewed records and counts (1,593 rows)
- us-coverage.json — Fifty-state coverage labels and non-additive record counts
- claims.json — Canonical claim wording, verdicts, evidence and checked dates (50 rows)
- corrections.json — Visible field and verdict corrections (65 rows)
- lifecycle-events.json — Dated approvals, starts, openings, withdrawals and other changes (9 rows)
- state-data-standard.json — Common state field and counting rules
- rights-manifest.json — Per-record reuse classification and approved-field lineage (212 rows)
Published collections
Collection files contain reviewed, attributed or unresolved rows exactly as labeled. Counts from different files may overlap and are not automatically additive. The Indiana facility file is a reviewed sample, not a statewide census.
| File | Scope | Contents |
|---|---|---|
| discovery.json | Multiple topics | 0 records |
| indiana-census.json | Indiana | 21 records |
| indiana-projects.json | Indiana | 15 records |
| national-projects.json | Multiple states | 78 records |
| new-albany-building-leads.json | Ohio | 43 records |
| ohio-facilities.json | Ohio | 29 records |
| ohio-projects.json | Ohio | 20 records |
| projects.json | Multiple topics | 6 records |
Machine access today
Every link above is a stable HTTPS JSON response and can be read without JavaScript. Matching CSV files are available for the registry, claims, corrections and lifecycle events. Changes are also published as JSON and an Atom feed. There is no query API, uptime guarantee or completeness promise yet.
What may become paid later
The underlying findings should remain free. A later paid product may add convenience: filtered queries, saved alerts, historical comparisons, bulk delivery and service guarantees. Those features will use the same reviewed records and cannot bypass the evidence gate.