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 "Planning Commission" 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-761

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

    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 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: 8c85901e62d740d385aa8d1c0ad3b79ff6b6ee013944e531f2fc56ab3f14c4da

  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)

    Added (15 lines)

    • The county's agenda for this meeting lists 10 numbered items, reproduced below exactly as the county wrote them:
    • - 1\) Approval of Minutes – August 24, 2026
    • - 2\) CONDITIONAL USE PERMIT 26 – 53 to transfer three building eligibilities from the SW¼ \(Except Tract 1 Lias Addition and Except Water Tower Addition Number 2 and Except H-1\) Section 15 to Lots 5 and 6 SW¼ Section 14 all within T102N-R52W Humboldt Township.
    • - 3\) CONDITIONAL USE PERMIT 26 – 55 to transfer two building eligibilities from Tract 1A Olson’s Addition NW¼ to the NE¼ \(Except Theis Addition\) all within Section 17 T101N-R47W Valley Springs.
    • - 4\) CONDITIONAL USE PERMIT 26 – 56 to allow Outdoor Industrial Storage on the property legally
    • - 5\) CONDITIONAL USE PERMIT 26 – 57 to exceed 3,600 square feet of accessory building space \(requesting 7,344 square feet\) on the property legally described as Tract 2 Krier Addition NE¼ NE¼ Section 9 T101N-R51W Wall Lake Township.
    • - 6\) CONDITIONAL USE PERMIT 26 – 59 to allow a Dog Kennel on the property legally described as Tract 1 Rovang’s Addition in the South 60 Acres NE¼ Section 21 T102N-R48W Brandon Township.
    • - 7\) REZONING 26 – 08 to rezone from the A-1 Agricultural and R-1 Residential Districts to the I-1 Light Industrial District the property legally described as the West 607 Feet of the North 383 Feet of Tract 1 Sweetman Addition N½ NW¼ Section 26 T102N-R48W Brandon Township.
    • - 8\) Old Business
    • - A. Discussion on Data Centers – Scott Anderson, Planner Director
    • - 9\) New Business
    • 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: 5c7289a2148cb1b8e0f1fbeca5ad6a6c61d329a46bdeeee941b6ceccc95d50bd

  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: cc7ecf100f33f3e0402fc0388f83fa1170db0d6614100fa3051d5611bc6f5a35

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.