Skip to main content

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 "Board of Commissioners" for Oct. 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-minnehaha-county-civicclerk-787

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 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 (2 lines )

    • 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 (3 lines)

    • The portal is currently offering 3 documents for this entry, named here exactly as the county named them:
    • - Minutes · Minutes from October 20, 2026 · posted Oct. 21, 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: 8dd05be6bb62911e4d27b49463a74ac7c7148e53e15fb4eae50e32e4bf98763c

  2. Version 2

    Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change

    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 (3 lines )

    • The portal gives the time as 09:00 on Oct. 20, 2026, printed exactly as published.
    • The portal marks that time UTC. This entry carries nothing to check that mark against, so 605Buzz says nothing about whether it is right, and the time above is reproduced exactly as published, without conversion.
    • The portal is not currently offering any document for this entry. That is a statement about the portal and nothing more: an agenda that is not posted may belong to a meeting that has been called off or to one whose agenda has simply not gone up yet, and there is no field here that tells the two apart.

    Added (34 lines)

    • The portal gives the time as 09:00 on Oct. 20, 2026. 605Buzz reads that as the county's own clock: 9 a.m. CDT.
    • The portal is currently offering 2 documents for this entry, named here exactly as the county named them:
    • - Agenda · October 20 County Commission Meeting Agenda · posted Oct. 16, 2026
    • - Agenda Packet · October 20 County Commission Meeting Packet · posted Oct. 16, 2026
    • 605Buzz does not summarise those documents. Follow the link above to read them at the county's own page.
    • The county's agenda for this meeting lists 23 numbered items, reproduced below exactly as the county wrote them:
    • - 1\) Consider a Motion to Approve the Agenda
    • - 2\) Consider Motion to Approve the Consent Agenda
    • - 3\) Approve the Minutes of October 6, 2026
    • - 4\) Bills to be Paid $1,820,174.90
    • - 5\) Reports
    • - a\) Minnehaha County EMS 2026 3rd Quarter Report
    • - b\) Register of Deed Statement of Revenues for September 2026
    • - c\) 3rd Quarter Report for Human Services
    • - d\) Monthly Financial Report - September 2026
    • - 6\) Personnel Actions
    • - a\) Memorandum of Personnel Actions for Approval and Notice
    • - 7\) Items Within Policy Guidelines
    • - a\) MC24-05 Balancing Change Order for Structure 50-149-140
    • - 8\) 2026 The Link Presentation - Jason Lemke, The Link Project Manager
    • - 9\) Consider a Motion to Authorize the Chair to Sign the 2026 Sub-recipient Agreement with SD Department of Social Services for In Jail Competency Restoration Services - Mike Mattson, Warden
    • - 10\) Consider a Motion to Authorize the Chair to Sign Amendment NO 3 to Contract for Housing of Lincoln County Prisoners between Minnehaha County and Lincoln County - Mike Mattson, Warden
    • - 11\) Consider Bid Results and Award Recommendation for the Fairgrounds EXPO Roof Repairs and Authorize the Chair to Sign an Agreement with MJ Dalsin Roofing - Mark Kriens, Director of Facilities and Construction
    • - 12\) Consider a Motion to Authorize the Siouxland Heritage Muesums to Apply for a South Dakota Arts Council Grant to support the Winter Concert Series at the Old Courthouse Museum - Bill Hoskins, Museum Director
    • - 13\) Consider a Motion to Declare one Copier \(Asset \#10026\) as Surplus and Authorize Disposal by Transfer to Minnehaha County Auditor Department - Jacob Maras, Highway Superintendent
    • - 14\) Consider Bid Results and Award Recommendation for Project MC22-03 Structure 50-273- 090 Replacement and Authorize Chair to Sign an Agreement with Nolz Dragline and Construction pending SDDOT Concurrence \(Bids Opened October 7, 2026\) - Jacob Maras, Highway Superintendent
    • - 15\) Consider a Motion to Authorize the Chair to Sign a Professional Services Agreement Between Minnehaha County and Infrastructure Management Services \(IMS\) for Pavement Management Services, Project MC26-02 - Jacob Maras, Highway Superintendent
    • - 16\) Authorize Commission Administrative Officer to Sign an Amendment to the Filevine Sales Order Allowing for the Delay of County Payment to January 2027 - Tom Greco, Commission Administrative Officer
    • - 17\) Consider Motion to Enter Into Executive Session for the Purposes of South Dakota Codified Law 1-25-2\(1\), \(3\), \(4\), \(6\) and \(7\).
    • 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: 32ddca54b95a8c3d2d2aac9558781f7f64b45fbf22be06674894bcbbf9856ede

  3. 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: 72fcfe11d92ad11bdbf23d5444e83b0c99181b1ad9005460bcf4120583170238

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.