Corrections record
Government / First published
The City of Spearfish's meeting portal lists "Planning Commission Meeting" for Dec. 16, 2025
Published automatically from public-record data — not reviewed by an editor. This heading is the article's current headline.
Article identifier: meeting-spearfish-civicclerk-2017
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 -
Version 4
Source update — the underlying public record changed
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:
6fc21d2ce8ece0d64c6759e32a0a781c604ba9cd61f5f0903ae9397173eb8d4e -
Version 3
Source update — the underlying public record changed
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 · 12/16/2025 Planning Commission Agenda · posted 2025-12-12
- - Agenda Packet · 12/16/2025 Packet · posted 2025-12-12
- - Minutes · 12/16/2025 Planning Commission Minutes · posted 2026-01-08
Added (3 lines)
- - Agenda · 12/16/2025 Planning Commission Agenda · posted Dec. 12, 2025
- - Agenda Packet · 12/16/2025 Packet · posted Dec. 12, 2025
- - Minutes · 12/16/2025 Planning Commission Minutes · posted Jan. 8, 2026
Content hash:
18a22a77a78771cc675fd44269f7b54f0564f843d03661a100e3936b801dd30f -
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 (19 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 13 numbered items, reproduced below exactly as the city wrote them:
- - A. Call to Order
- - B. Roll Call
- - C. Approve Agenda
- - D. Approve Minutes
- - 1. Approve the minutes from the December 2nd, 2025 Regular Session.
- - E. Declaration of Conflicts of Interest
- - F. Items for Action
- - 1. Request: Consider a variance to 154.075 Blocks and associated preliminary plat of the Soncy Subdivision
- - 2. Request: Consider a final plat within the Extraterritorial Jurisdictional \(ETJ\) Area of Lot H Revised.
- - G. Items for Discussion
- - H. Items from Commissioners
- - I. Public Comment – Public comments are welcome at this time, however, no action will be taken.
- - J. Adjournment
- 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the city labels Petitioner, Property Owner, Location or Staff Report are not reproduced here, and neither is a street address; the agenda packet is not read at all. Where an item names a person — an official presenting it, or a resident being appointed to something — that name is part of the item the city wrote, and it stands as written. The text is the plain-text rendering the city's own portal returns for that file. Nothing above is a summary, and an item on an agenda is something a body may consider rather than something it did.
Content hash:
8c5124b676a673628914b17e4a5f4bf4a3a77bda5c2923f676ba8e2daca65c3b -
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:
7f2607d685593ee324145b2a871bd3cae4fb4600360652e6312786f99e3211fa
3 corrections have been issued.
See something wrong? Read the corrections policy or write to corrections@605buzz.com.