public-hearing-concerning-a-resolution-approving-the · Resolution · 2026 · City of Thornton

A public hearing concerning a resolution approving the Service Plan for the Thornton Commons Metropolitan District and an Intergovernmental Agreement between the City and the Thornton Commons Metropolitan District regarding the Service Plan for the District.

Official status: Passed

Prime sponsors

Sponsor information is on the official bill page (linked below).

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 public-hearing-concerning-a-resolution-approving-the, oldest first
DateLocationAction
03/31/2026City CouncilQuasi-Judicial Public Hearings — Passed

Recorded votes

Full text

Official record

City of Thornton — Council Record of Votes (thorntonco.gov)

Source: City of Thornton — Council Record of Votes (thorntonco.gov) · 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

ed451e7e54516f3e37a0f7e2a5d81560aaac394e7d0a5149f629d28c9666284a

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 Thornton — Council Record of Votes (thorntonco.gov) · 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.