Resolution Approving a Site Development Plan for Residential Development Within the Bella Mesa Planned Development (Bella Mesa South) [9.3 acres of property located northwest of the intersection of Mikelson Boulevard and Mitchell Street]
Official status: Adopted
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 |
|---|---|---|
| 03/24/2026 | Town Council | Listed on the Town Council agenda — Quasi Judicial Hearings |
| 03/24/2026 | Town Council | Motion passed — "Approve Quasi-Judicial Resolution RES 2026-038 as presented" (Town Council minutes) |
Full text
Official record
Source: Town of Castle Rock — Town Council agendas and minutes, Granicus (castlerock-co.granicus.com); Public Notice of Ordinances (crgov.com) · 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
81e1b6398ef49687831dba830c80fc222c7c5cd15cbce015f03994049ae07bf6
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.