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

Minnehaha County's meeting portal lists "Archived - Building Committee" for Oct. 7, 2025

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-671

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 8

    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 7)

    Removed (2 lines )

    • The portal gives the time as 08:00 on Oct. 7, 2025, 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.

    Added (9 lines)

    • The portal gives the time as 08:00 on Oct. 7, 2025. 605Buzz reads that as the county's own clock: 8 a.m. CDT.
    • The county's agenda for this meeting lists 4 numbered items, reproduced below exactly as the county wrote them:
    • - 1. Call to Order
    • - 2. Approve the Meeting Minutes from September 2, 2025
    • - 3. Update on Campus Master Planning Project
    • - 4. Discussion on Swapping the Public Advocate and Planning Office Suites
    • 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the county 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 county wrote, and it stands as written. The text is the plain-text rendering the county'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: 4322086d8573f040f919f5025d093db564ff29c3a672f05f82cab9ac260a0de0

  2. Version 7

    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 6)

    Removed (9 lines )

    • The county's agenda for this meeting lists 4 numbered items, reproduced below exactly as the county wrote them:
    • - 1. Call to Order
    • - 2. Approve the Meeting Minutes from September 2, 2025
    • - 3. Update on Campus Master Planning Project
    • - 4. Discussion on Swapping the Public Advocate and Planning Office Suites
    • 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the county 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 county wrote, and it stands as written. The text is the plain-text rendering the county'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: 67e9f25101d94f7afc281ebc1cb8bb6e97c7970cbd816068f3f5b5489ee94896

  3. Version 6

    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 5)

    Added (9 lines)

    • The county's agenda for this meeting lists 4 numbered items, reproduced below exactly as the county wrote them:
    • - 1. Call to Order
    • - 2. Approve the Meeting Minutes from September 2, 2025
    • - 3. Update on Campus Master Planning Project
    • - 4. Discussion on Swapping the Public Advocate and Planning Office Suites
    • 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the county 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 county wrote, and it stands as written. The text is the plain-text rendering the county'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: e4f30f08399c36164967ea49805fed2aa908b885a24feb304a7fea5b29a8cda4

  4. Version 5

    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 4)

    Removed (9 lines )

    • The county's agenda for this meeting lists 4 numbered items, reproduced below exactly as the county wrote them:
    • - 1. Call to Order
    • - 2. Approve the Meeting Minutes from September 2, 2025
    • - 3. Update on Campus Master Planning Project
    • - 4. Discussion on Swapping the Public Advocate and Planning Office Suites
    • 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the county 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 county wrote, and it stands as written. The text is the plain-text rendering the county'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: 67e9f25101d94f7afc281ebc1cb8bb6e97c7970cbd816068f3f5b5489ee94896

  5. 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 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. South Dakota keeps two time zones — Central east of the Missouri River, Mountain west of it — so 605Buzz prints the county's own wall clock rather than converting it for anyone.
    • This article was assembled from [Minnehaha County's public meeting information page](https://www.minnehahacounty.gov/commission/meetingInfo/meetingInfo.php). See the [corrections ledger](/corrections) if a field is wrong.

    Added (2 lines)

    • 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.
    • This article was assembled from [Minnehaha County's public meeting information page](https://www.minnehahacounty.gov/commission/meetingInfo/meetingInfo.php).

    Content hash: e4f30f08399c36164967ea49805fed2aa908b885a24feb304a7fea5b29a8cda4

  6. 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 · October 7 Building Committee Meeting Agenda · posted 2025-10-03
    • - Agenda Packet · October 7 Building Committee Meeting Agenda Packet · posted 2025-10-03
    • - Minutes · Minutes from October 7 · posted 2025-10-08

    Added (3 lines)

    • - Agenda · October 7 Building Committee Meeting Agenda · posted Oct. 3, 2025
    • - Agenda Packet · October 7 Building Committee Meeting Agenda Packet · posted Oct. 3, 2025
    • - Minutes · Minutes from October 7 · posted Oct. 8, 2025

    Content hash: 6cc849195a61c443500c56fe5aa2a873982a3af405a43615ed53cd6095cd5b50

  7. 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 county's own page.

    Added (10 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 county's own page.
    • The county's agenda for this meeting lists 4 numbered items, reproduced below exactly as the county wrote them:
    • - 1. Call to Order
    • - 2. Approve the Meeting Minutes from September 2, 2025
    • - 3. Update on Campus Master Planning Project
    • - 4. Discussion on Swapping the Public Advocate and Planning Office Suites
    • 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the county 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 county wrote, and it stands as written. The text is the plain-text rendering the county'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: 0541ac9c4b661193c9b2bbd705a2d6650d6d9f1f35f8d6acef460fb25de96e24

  8. 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: aa21e7f9d191c2fb3f168e5bff47e5f7f2549125eb47bc61f82cf26e1580c3cf

7 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.