Corrections record
Government / First published
Minnehaha County's meeting portal lists "Joint Planning Commission with City of Sioux Falls" for Sept. 28, 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-minnehaha-county-civicclerk-889
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 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 (5 lines )
- The portal gives the time as 19:00 on Sept. 28, 2026, printed exactly as published.
- The portal marks that time UTC, and it is not: the county'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 county published, reproduced without conversion.
- The portal is currently offering 2 documents for this entry, named here exactly as the county named them:
- 605Buzz does not summarise those documents. Follow the link above to read them at the county's own page.
Added (4 lines)
- The portal gives the time as 19:00 on Sept. 28, 2026. 605Buzz reads that as the county's own clock: 7 p.m. CDT.
- The portal is currently offering 3 documents for this entry, named here exactly as the county named them:
- - Minutes · 9-28-26 Joint SF Meeting Minutes · posted Sept. 30, 2026
- 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 county's own page.
Content hash:
0ff7bc207991565b6780d6128ba4877418b10b221cd4b6a974624af625ef4bc9 -
Version 2
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 1)
Removed (1 line )
- - Agenda Packet · 9-28-26 Joint SF Meeting Packet · posted Sept. 17, 2026
Added (1 line)
- - Agenda Packet · 9-28-26 Joint SF Meeting Packet · posted Sept. 23, 2026
Content hash:
5b8598fe66d30cd8613e14c2b2fd384618b5c0a0a78136cfba9fa41624926675 -
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:
3cd814ec5cd0c5d77b6aca74c4abae8b2bc61e22ade51ed0111b1a39e228ce6c
2 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.