R2026-111 · Resolution · 2026 · City of Aurora

Data Center Moratorium 2026 (subject to affirmative council action on item 17.a)

R2026-111 A RESOLUTION OF THE CITY COUNCIL OF THE CITY OF AURORA, COLORADO, AUTHORIZING A MORATORIUM ON THE ACCEPTANCE OR PROCESSING OF DEVELOPMENT APPLICATIONS WHERE A DATA CENTER IS INCLUDED AS A PROPOSED PRIMARY USE

Prime sponsors

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

The official page for this measure does not publish a summary. Its full text is linked below.

Status timeline

Every recorded action on R2026-111, oldest first
DateLocationAction
10/26/2026City CouncilListed on the City Council agenda — General Business

Full text

Official record

City of Aurora — City Council meeting agendas and voting results (auroragov.org)

Source: City of Aurora — City Council meeting agendas and voting results (auroragov.org) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

2bde1ca2942123b33481f92597bbdc04d0f2b48f7f08839257b108240a17ce7f

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-10-28 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: City of Aurora — City Council meeting agendas and voting results (auroragov.org) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.