# Research and verification method

## Source order

Use trackers, news, advocacy, and industry materials for discovery. Verify legal propositions against enacted legislation, current codes, official regulations, commission orders, approved tariff sheets, signed agreements, issued permits, and court records. Official explanatory pages help orient readers but do not replace controlling text when that text is available.

Record the exact supporting section/page and a brief excerpt or faithful paraphrase. Distinguish official text, official summary, secondary reporting, and researcher inference. Cite original publishers. Follow applicable quotation limits. Do not bypass access restrictions. If controlling text is unavailable, retain a research lead and mark it unverified rather than treating it as law.

## Verification workflow

1. Identify the instrument, issuing authority, official identifier, and geographic reach.
2. Retrieve controlling text and official history/status. Confirm that the version matches the claimed rule.
3. Verify adoption, effective dates, repeal/sunset, amendments, and transition rules separately. Do not infer effectiveness from passage or a press release.
4. Extract individual provisions, coverage thresholds, exceptions, enforcement, and deadlines.
5. Check relevant official litigation/proceeding information; distinguish a challenge from a stay. Record unresolved validity questions without deciding them.
6. Write a resident-facing explanation and researcher note. Link claims to evidence.
7. Record verification date and coverage log, then flag review needs.

## Status vocabulary

Instrument status: proposed; adopted-not-effective; effective; expired; repealed; superseded; withdrawn; failed; unknown.

Litigation status is separate: none-identified-in-scope; challenged; stayed-in-part; stayed-in-full; resolved; unknown. A search that finds no litigation does not establish there is none.

Review status: lead; extracted; source-verified; reviewer-approved; needs-review. Model self-checking is not independent review.

Binding force: binding; nonbinding; conditional-contractual; unclear. A plan, pledge, or incentive application is not automatically enforceable. Record relevant conditions and parties for agreements.

## Coverage vocabulary

- Not researched.
- Research in progress.
- Reviewed within stated scope: relevant measures identified.
- Reviewed within stated scope: no data-center-specific measure identified.
- Source unavailable or unresolved.

Every coverage claim requires a jurisdiction, topic, source set, search date, and limitations. Generally applicable rules can still apply where no specific measure was found.

## Comparison safeguards

- Noise: retain dBA/dBC, time window, receptor/location, averaging, tonal treatment, and exemptions. Never rank raw limits without those conditions.
- Water: distinguish withdrawals, consumption, discharge, annual averages, peak demand, direct use, and upstream estimates.
- Electricity: distinguish MW capacity from MWh energy; minimum billed demand from actual consumption; approved tariffs from proposed tariffs; service area from state boundaries.
- Emissions: distinguish permitted potential emissions from measured emissions and emergency backup from routine generation.
- Finance: distinguish promised, authorized, paid, and realized amounts; do not mix construction jobs with permanent jobs.
- Applicability: record facility/campus aggregation, thresholds, expansions, grandfathering, exemptions, and geographic limits.
- Outcomes: presence of a rule does not prove compliance, enforcement, or effectiveness. Mark empirical evidence separately.

## Updates

Never overwrite history silently. Preserve prior versions, add verification events, and link amendments/replacements. Review the official source before marking an entry unchanged. Record unavailable sources and unresolved changes. Maintain a queue with priority, next source/action, and reason. Do not fabricate freshness dates or claim exhaustive coverage from a finite search.


Initial release: 2026-10-28. Calibration update: ten source-verified legal instruments with eleven extracted provisions and four official agency/utility summaries checked. The sample is not a national survey and has not yet received independent review. The map distinguishes verified instruments from official leads; neither shading nor a missing record states what law applies throughout a state.

The Virginia and Fairfax records are distinct: the Virginia statute sets a threshold and assessment process for specified land-use applications, while Fairfax County's local zoning amendment has separate use tables, setbacks, noise-study requirements, and transition rules. Federal engine records are limited to selected emergency stationary RICE and stationary compression-ignition-engine provisions. Their 50-hour terms are conditional and do not represent a general operating allowance. Minnesota's large-load tariff statute sets a future classification process and does not itself establish the final class or utility tariff.

The Ohio Power tariff and Loudoun County noise provisions remain official-source leads pending retrieval and review of controlling text and, for Ohio, proceeding status. Do not treat their summaries as verified legal requirements.
