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

Sioux Falls annexed 8 acres by resolution 65-26, effective June 25, 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: annex-65-26

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 (1 line )

    • 605Buzz publishes the city's structured annexation record — its resolution number, its status, its effective date and its area. The record's own notes field is not reproduced here: it sometimes describes a single property by street address, and an annexation of a few acres can be one household's land.

    Added (1 line)

    • 605Buzz publishes the city's structured annexation record — its resolution number, its status, its effective date, its area and, where the city gives one, its description of the location. That description is reproduced only where it names a road, a right-of-way or a legal land description. Where the city's note is a street address it is withheld and no substitute is offered, because an annexation of a few acres can be one household's land.

    Content hash: 523ce050ad3a35ac19b67584c8bffed4a49970fbee7ccbd70aa87239f1359467

  2. Version 2

    Clarification

    Revised by 605Buzz — recorded under an internal label that names no person who read this version

    The headline and the body text both changed. (compared against version 1)

    Headline at this version: Sioux Falls annexed 8 acres by resolution 65-26, effective June 25, 2026

    Removed (1 line )

    • The city of Sioux Falls annexed 8.0 acres under **resolution 65-26**, effective June 25, 2026, according to [the city's own annexation record](https://gis.siouxfalls.gov/arcgis/rest/services/Data/Community/MapServer/0).

    Added (1 line)

    • The city of Sioux Falls annexed 8 acres under **resolution 65-26**, effective June 25, 2026, according to [the city's own annexation record](https://gis.siouxfalls.gov/arcgis/rest/services/Data/Community/MapServer/0).

    Content hash: 444bbd9fd91eed1ef43c3f62c0736ffa9bb20dfaf20761054d6ca7cc5d0e6edb

  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: 761d9086edcbeb5e37bc61abb3b5148e45e264d39a02ec94a7463c6b7679d39e

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.