EDITORIAL SERIES
Community Ledger
Community-level tracking of data-center promises, obligations, and verified follow-through.
Residents, local officials, journalists, researchers, and builders evaluating a specific project.
Published work
- Data centers: public value, electricity, water, and noise
The existing Bright section supplies source-backed records and guides; a location-specific ledger remains a future reporting step.
What every edition contains
- place and facility
- promise or obligation
- baseline
- owner
- deadline
- reported result
- verification status
- source
- correction history
Source and fact-check standard
- Primary public record or attributable report
- exact geography and time window
- projection separated from realized outcome
- gross and net values kept distinct
- Verify jurisdiction and facility identity
- Check units and periods
- Identify who reported the result
- Name missing audit evidence
Author: Bright research editor. Reviewer: Human editor; local expert review when available and disclosed.
From draft to correction
- Record intake
- local source map
- baseline
- claim classification
- subject query where warranted
- review
- publish
- scheduled recheck
Append dated updates and corrections; retain prior promises so follow-through remains inspectable.
Newsletter, social, and support
Use only a verified change, with the locality and evidence status in the headline or first sentence.
Use a simple local ledger: promise, evidence, status, next checkpoint.
Sponsorship: No sponsor tied to a facility or decision under examination; unrelated page-level support requires conflict review.
Never sponsored: A project’s inclusion, status, public-benefit conclusion, or removal of an unmet commitment.