Skip to main content
605Buzz
Today Search Corrections Following About Join waitlist

3 of 17 desks have not been read in over 48 hours, and 2 more have not finished a read in over 14 days. Their pages say when each was last read. Anything those desks show as upcoming or underway may have changed — check the source before relying on it.

605Buzz

Corrections record

Government / First published

The City of Spearfish's meeting portal lists "City Council Meeting" for April 20, 2026

Published automatically from public-record data. Whether a person reviewed any later version is recorded against that version below. This heading is the article's current headline.

Article identifier: meeting-spearfish-civicclerk-35

Read the live article →

Version history

Every published version of this article, newest first. Versions are append-only: a correction adds a row, it never rewrites history. Each version below states what changed against the version before it — which fields moved, and which body lines were added or removed.

The content hash is a SHA-256 fingerprint of that version's stored headline and body, computed when the version was written. Two versions with the same hash hold identical text; a changed hash proves the text moved. It is the tamper-evidence check — recompute it against an exported copy of a version and any silent edit shows up as a mismatch.

How we verify a hash — and how you can

Canonicalization: the hashed bytes are the version's stored headline, then the two characters ||, then the version's stored body markdown — UTF-8, SHA-256, lowercase hex. Nothing else is in the input: no normalization, re-wrapping or rendering is applied first, no trailing newline is added, and no other field (including the parent version's id) is mixed in.

Export a version's stored headline and body, join them with the two characters ||, and take the SHA-256 of the UTF-8 bytes. It must equal the hash printed beside that version. In a shell: 

printf '%s' "HEADLINE||BODY" | shasum -a 256

  1. Version 4

    Source update — the underlying public record changed

    This entry was filed before 605Buzz began recording its own wording changes separately. Its diff may also show wording changes 605Buzz made since the previous entry.

    Automated update from the source feed — no human edit

    The body text changed; the headline did not. (compared against version 3)

    Removed (2 lines )

    • The portal marks that time UTC, and it is not: the city's own records contradict the mark, because the plain-English posting time the portal prints for this meeting's agenda states the same clock reading as the machine-readable field that claims to be UTC. The time above is therefore the local wall clock the city published, reproduced without conversion. South Dakota keeps two time zones — Central east of the Missouri River, Mountain west of it — so 605Buzz prints the city's own wall clock rather than converting it for anyone.
    • This article was assembled from [the City of Spearfish's public agendas and minutes page](https://www.spearfish.gov/AgendaCenter). See the [corrections ledger](/corrections) if a field is wrong.

    Added (2 lines)

    • The portal marks that time UTC, and it is not: the city's own records contradict the mark, because the plain-English posting time the portal prints for this meeting's agenda states the same clock reading as the machine-readable field that claims to be UTC. The time above is therefore the local wall clock the city published, reproduced without conversion.
    • This article was assembled from [the City of Spearfish's public agendas and minutes page](https://www.spearfish.gov/AgendaCenter).

    Content hash: 091ce2f0d26604df733f591a7f9ced287ed6fe4520e42257c6745449235587f9

  2. Version 3

    Source update — the underlying public record changed

    This entry was filed before 605Buzz began recording its own wording changes separately. Its diff may also show wording changes 605Buzz made since the previous entry.

    Automated update from the source feed — no human edit

    The body text changed; the headline did not. (compared against version 2)

    Removed (3 lines )

    • - Agenda · City Council Regular Session Agenda 4/20/2026 · posted 2026-04-17
    • - Agenda Packet · Updated City Council Regular Session Packet 4/20/2026 · posted 2026-04-20
    • - Minutes · City Council Regular Session Minutes 04/20/2026 · posted 2026-04-27

    Added (3 lines)

    • - Agenda · City Council Regular Session Agenda 4/20/2026 · posted April 17, 2026
    • - Agenda Packet · Updated City Council Regular Session Packet 4/20/2026 · posted April 20, 2026
    • - Minutes · City Council Regular Session Minutes 04/20/2026 · posted April 27, 2026

    Content hash: e4f1275375d55ace834a5a7a3ffde736ccb0dce16b46b24b7a354128c0fe3b2a

  3. Version 2

    Revision (no reason recorded)

    605Buzz began publishing the numbered item lines from the agenda file this article already linked to

    The body text changed; the headline did not. (compared against version 1)

    Removed (1 line )

    • 605Buzz does not fetch, parse or summarise those documents. Minutes are produced after a meeting rather than before one; what they say is not reproduced here. Follow the link above to read them at the city's own page.

    Added (46 lines)

    • 605Buzz does not summarise those documents. Minutes are produced after a meeting rather than before one; what they say is not reproduced here. Follow the link above to read them at the city's own page.
    • The city's agenda for this meeting lists 61 numbered items. 605Buzz reproduces 40 of them below, exactly as the city wrote them; the other 21 name a party or a location and are not reproduced here.
    • - 1. Call to Order
    • - 2. Roll Call
    • - 3. Invocation \(participation welcomed, but not mandatory\)
    • - A. Countryside Church
    • - 4. Pledge of Allegiance
    • - 5. Approve Agenda
    • - 6. Public Comment - Public comments are welcome; however, no action can be taken by the Council on comments received for items not on this agenda. Anyone wishing to have the Council consider a new item should complete a Citizen Request Form to be reviewed by city administration.
    • - 7. Declaration of Any Potential Conflicts of Interest
    • - 8. Consent Agenda
    • - A. Approve the minutes of the March 16, 2026 Board of Adjustment meeting.
    • - B. Approve the minutes of the April 1, 2026, City Council study session.
    • - C. Approve the minutes of the April 6, 2026, City Council regular session.
    • - D. Approve a Temporary Construction Easement Agreement between Spearfish School District and the City, required for the Mountain View Elementary Alley Improvements Project \#2604.
    • - E. Approve the Water Line Easement Agreement with Spearfish School District to allow the City to perform construction and maintenance of the Water Line adjacent to Mountain View Elementary.
    • - F. Approve a Temporary Construction Easement Agreement, between the property owner
    • - G. Approve a Temporary Construction Easement Agreement, between the property owner
    • - H. Approve a Temporary Construction Easement Agreement, between the property owner
    • - I. Approve the Treasurer's Report dated March 31st, 2026.
    • - J. Ratify the Visit Spearfish Board of Directors' recommendation for a $3,000 sponsorship to the Ridge Riders.
    • - K. Approve dedication of infrastructure associated with Coley Road, phase VI of Elkhorn Ridge Golf Estates.
    • - 9. Added or Adjusted Wages
    • - A. Approve the following wage additions and adjustments as budgeted for 2026. Regular Positions Budgeted Position Wage Parks Facilities Maintenance Yes $22.12 Tech part-time
    • - 10. City Attorney
    • - A. Approve Real Estate Purchase Agreement with SEDC and Hills View Homes to sell sixteen additional lots to Hills View Homes for additional construction and development in Sky Ridge Subdivision.
    • - B. Approve Resolution 2026-08 - A Resolution to Transfer Real Property from the City of Spearfish to Spearfish Economic Development Corporation.
    • - C. Approve first reading of Ordinance No. 1426, an Ordinance Amending The Revised Ordinances Of The City Of Spearfish, Chapter 31: Organizations, Council On The Arts And Humanities, And Chapter 35: General Administrative Policies, Art In Public Places
    • - D. Approve first reading of Ordinance No. 1427, an Ordinance Amending the Revised Ordinances of the City of Spearfish, Chapter 31: Organizations, Black Hills Airport Task Force
    • - 11. Community Development
    • - A. Hold a public hearing for a minor final plat, subdividing an existing 13.22-acre lot into two lots, located within the Extraterritorial Jurisdiction of the City.
    • - 1. Approve a final minor plat, subdividing an existing 13.22-acre lot into two lots, located within the City's Extraterritorial Jurisdiction.
    • - B. Approve the Development Agreement for Eastside Acres.
    • - 12. Finance
    • - A. Approve the 3-year licenses for 162 Windows users on the City network at a cost of $13,122.
    • - C. Approve an application from Zac Eixenberger with Spread the Tunes for a special event malt beverage license for the Canyon Acoustic Series on June 10, 17, & 24 and July 1, 8, 15, 22, & 29, 2026, from 4:00 p.m. to 8:30 p.m. at the Spearfish City Park Bandshell.
    • - D. Approve an application from Allison Moore with Spearfish Creek Wine Bar for a special event on-sale wine license for the Canyon Acoustic Series June 10, 17, & 24, and July 1, 8, 15, 22, & 29, 2026, from 6:00 p.m. to 8:30 p.m. at Spearfish City Park.
    • - 13. Parks and Recreation
    • - A. Approve design of the Spearfish Trails Coalition \(STC\) Trail Hub project.
    • - 14. Public Works

    6 further added lines are not shown here.

    Content hash: c750809fb3cdb105cbc3b0718ebe00711ad6165a24590363129dec87fe97fa69

  4. Version 1

    Initial publication

    Initial automated publication — no human byline

    No earlier version is in this record, so there is nothing to compare against.

    Content hash: 04db3fdc73ff2a08cb8eedf34e5fd9aff72beb3e72ad9bd695b8ee3bb961a188

3 corrections have been issued.

See something wrong? Read the corrections policy or write to corrections@605buzz.com — though mail to 605buzz.com is not routed yet, so that address currently bounces.