Tapias LLC Annexation Ordinance
2026-14 FOR AN ORDINANCE ANNEXING A PARCEL OF LAND LOCATED IN THE SOUTHWEST QUARTER OF SECTION 25, TOWNSHIP 3 SOUTH, RANGE 66 WEST OF THE SIXTH PRINCIPAL MERIDIAN, COUNTY OF ADAMS, STATE OF COLORADO 2.496 ACRES
Official status: Pass
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
| Date | Location | Action |
|---|---|---|
| 04/06/2026 | City Council | Listed on the City Council agenda — Annexations |
| 04/20/2026 | City Council | Listed on the City Council agenda — Annexations |
Recorded votes
- 04/06/2026 — City Council: “Does the Council wish to approve this ordinance?” — the motion Pass on a vote of 9–0.
- 04/20/2026 — City Council: “Does the Council wish to approve this ordinance?” — the motion Pass on a vote of 10–0.
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
a6f7ffc0b181e59ea1f8dac70ca72bfa036a50e0d75ee45c4c02202a560cf0c7
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.
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.