Corrections + retractions

605Buzz treats corrections as first-class content. Every correction is recorded with its reason and timestamp on the article's own ledger at /corrections/<article-slug>, which shows the diff — which fields changed and which body lines were added or removed, version by version. That ledger is the complete record for an article; the list below is the most recent corrections across all of them. The chain is append-only: a correction adds a version, it never rewrites one. Where the reporting is withdrawn rather than corrected, the original address serves a 410 Gone tombstone pointing at that ledger, so inbound links + search-engine caches still resolve to context.

Recent corrections

This list is corrections — times 605Buzz published something that was wrong, or that its source later changed. It does not include wording notes: occasions when we rewrote our own wording and the public record did not change. Those are recorded on each article’s own page of changes, with the same timestamps and the same version-by-version differences as everything else — this list is shorter on purpose, not more complete.

Showing the 50 most recent corrections across all articles — there may be older ones. Each article's complete, append-only version chain — every version, with the diff and timestamp — lives on its own ledger page, linked from each row below.

• chamber-event-mitchell-chamber-45671 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:11 a.m. CT
• chamber-event-pierre-43306 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:10 a.m. CT
• event-washington-pavilion-11723 — v2, Source update — the underlying public record changed , Oct. 24, 2026, 7:10 a.m. CT
• event-siouxfallsevents-audatours-sioux-falls-audio-tour-1oiqiwu — v16, Source update — the underlying public record changed , Oct. 24, 2026, 7:09 a.m. CT
• event-siouxfallsevents-10002685 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:09 a.m. CT
• event-siouxfallsevents-10002506 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:09 a.m. CT
• event-siouxfallsevents-10002566 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:09 a.m. CT
• game-rush-2026-11-21-toledo-walleye — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:08 a.m. CT
• game-usd-9685 — v5, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9579 — v4, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9684 — v4, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9650 — v4, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9718 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9742 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9743 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9744 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-usd-9745 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:07 a.m. CT
• game-sdsu-15164 — v5, Source update — the underlying public record changed , Oct. 24, 2026, 7:06 a.m. CT
• game-sdsu-15134 — v4, Source update — the underlying public record changed , Oct. 24, 2026, 7:06 a.m. CT
• game-sdsu-15242 — v4, Source update — the underlying public record changed , Oct. 24, 2026, 7:06 a.m. CT
• game-sdsu-15258 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:06 a.m. CT
• game-sdsu-15187 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:06 a.m. CT
• meeting-mitchell-civicclerk-1510 — v3, Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change , Oct. 24, 2026, 7:05 a.m. CT
• meeting-mitchell-civicclerk-1590 — v2, Source update — the underlying public record changed , Oct. 24, 2026, 7:05 a.m. CT
• meeting-sioux-falls-onbase-4415 — v2, Source update — the underlying public record changed , Oct. 24, 2026, 7:05 a.m. CT
• meeting-sioux-falls-onbase-4380 — v2, Source update — the underlying public record changed , Oct. 24, 2026, 7:05 a.m. CT
• meeting-aberdeen-agenda-1462 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:04 a.m. CT
• meeting-aberdeen-agenda-1469 — v3, Source update — the underlying public record changed , Oct. 24, 2026, 7:04 a.m. CT
• chamber-event-mitchell-chamber-45671 — v2, Source update — the underlying public record changed , Oct. 23, 2026, 7:24 a.m. CT
• chamber-series-yankton-55287 — v12, Source update — the underlying public record changed , Oct. 23, 2026, 7:23 a.m. CT
• event-siouxfallsevents-audatours-sioux-falls-audio-tour-1oiqiwu — v15, Source update — the underlying public record changed , Oct. 23, 2026, 7:21 a.m. CT
• event-siouxfallsevents-october-fall-drop-in-crafts — v4, Source update — the underlying public record changed , Oct. 23, 2026, 7:21 a.m. CT
• event-siouxfallsevents-october-halloween-drop-in-crafts — v4, Source update — the underlying public record changed , Oct. 23, 2026, 7:21 a.m. CT
• game-usd-9593 — v4, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-usd-9581 — v4, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-usd-9746 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-usd-9753 — v2, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15122 — v5, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15263 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15265 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15266 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15267 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15268 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• game-sdsu-15269 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:20 a.m. CT
• meeting-spearfish-civicclerk-2226 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:05 a.m. CT
• meeting-mitchell-civicclerk-1564 — v4, Source update — the underlying public record changed , Oct. 23, 2026, 7:05 a.m. CT
• meeting-mitchell-civicclerk-1508 — v3, Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change , Oct. 23, 2026, 7:05 a.m. CT
• meeting-mitchell-civicclerk-1509 — v3, Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change , Oct. 23, 2026, 7:05 a.m. CT
• meeting-minnehaha-county-civicclerk-807 — v3, Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change , Oct. 23, 2026, 7:04 a.m. CT
• meeting-sioux-falls-onbase-4409 — v3, Source update — the underlying public record changed , Oct. 23, 2026, 7:04 a.m. CT

Our correction workflow

605Buzz has no retained media-law counsel. This page said corrections were “coordinated with retained media-law counsel” from launch until Sept. 5, 2026. That was not true and is corrected here rather than quietly deleted. We will consult a lawyer where a matter carries legal risk; none is retained today. Statutory windows and remedies vary by jurisdiction and by publisher class, and 605Buzz is not in a position to tell you how they apply to your matter — if that question matters to you, take it to your own lawyer. What this page can promise is the operational cadence below, which is machinery rather than judgement:

1. Written notice arrives (an email, a court filing, or a demand from your lawyer). Today an email cannot arrive: mail to 605buzz.com currently bounces, and there is no postal address or contact form. The notice itself lives in our correspondence, not in the published record: the ledger records what we published and when we changed it, not when we were told. What each correction carries is its version number, its reason code, the timestamp it was written, who or what wrote it, and the SHA-256 hash of that version's text — with the full append-only chain, including the per-version diff, at /corrections/<article-slug>.
2. Review: we draft the correction as promptly as practical. We will consult a lawyer where a matter carries legal risk; none is retained today.
3. Republication: we publish the correction as promptly as practical after review completes. The correction is listed here with its reason + timestamp and appears in full — with the diff — on the article's own ledger at /corrections/<article-slug>; downstream channels (RSS, JSON Feed, and each article's JSON) receive the updated content on their next poll.
4. Follow-through: every downstream channel confirms receipt via the response's warnings array. Any reconciliation gap gets logged and manually cleared.
5. Corrections record: the public record is this page (article slug, reason code, and timestamp for every issued correction) plus each article's own ledger, which carries the per-version diff. Once mail is live, a subject or auditor with a specific request may write to corrections@605buzz.com, and we aim to acknowledge such requests promptly; scope depends on the request. Today mail to that address currently bounces.

Cross-jurisdiction handling

For articles reaching subjects outside South Dakota, the same cadence applies: 605Buzz reviews the notice and corrects or retracts on the merits. Statutory windows and remedies vary by jurisdiction and by publisher class, and because there is no retained counsel here, 605Buzz makes no claim about which framework governs your matter or what it entitles you to. The correction machinery is the same wherever you are; the legal question is one for your own lawyer.

Every article is stored with the jurisdiction it concerns, as a standard place code (ISO 3166-2, such as US-SD for South Dakota), and each correction belongs to an article — so a correction can always be traced to the place it concerns.

Reason codes

Every correction is stored with one reason code, and the ledger shows it verbatim. The system can record exactly eight today — this is the whole vocabulary, not a sample:

• factual — a stated fact was wrong and is now right
• clarification — the facts held, the wording misled
• spelling — a name, place, or figure was misspelled
• source_update — the underlying public record itself changed
• rewording — a language model reworded the article for length after the template wrote it; no figure, date, name, source link or caveat moved, and the diff below each version is how you check that rather than believe it
• expanded_reading — 605Buzz began publishing part of a record it had always linked to but had not published before — most often the numbered item lines of a meeting agenda, or, on an auction listing, its venue name, street address and map coordinates. The public record did not change; what changed is how much of it we print
• editorial_note — 605Buzz rewrote or reshaped its own prose for this article. It is not counted as a correction, because the public record did not change. Where a person approved the change the entry says so; an entry the pipeline filed itself makes no claim about whether the earlier wording was right or wrong. The diff below each version is how you check what changed rather than believe it
• retraction — the reporting is withdrawn; the article serves a 410 Gone tombstone

A database constraint enforces that list, so a correction cannot be filed under a code this page doesn't name.

Extraction fixes

Our articles are assembled from public records by software that reads those records. Sometimes the record was always right and our reading of it was wrong — a company name that lost a dash to a mis-decoded character, a field parsed out of the wrong column. When we fix that parsing, the articles it affected are re-published from the corrected reading, and each one gets a correction.

Those corrections are filed as factual, attributed to ingest-extraction-fix, and the ledger renders that as “Corrected extraction.” They are deliberately not filed as source_update, which this page defines as the underlying public record itself changing. In an extraction fix the public record did not change; our extraction of it was corrected. Filing our own mistake under a code that blames the agency would be a false statement in a ledger whose only job is to be true. The same rule covers the other correction we cause ourselves: operator-window-backfill, where an article gains records because we widened our own search window.

Not yet implemented. Our editorial process document specifies a finer-grained taxonomy for what drives a retraction — subject demand, a lawyer’s advice, court order or injunction, settlement obligation, regulatory order, EU DSA notice, child-safety trigger, defamation risk — each carrying tier-3+ approval and cryptographic evidence that the approval gate fired. None of those are recordable by the system today: a retraction from any of those drivers is stored as retraction, with the driver captured in the correspondence rather than the ledger. We'd rather name the gap than print a vocabulary the database would reject.

Seventeen desks publish — business intel, government, ag, public safety, sports, events, auctions and community. The editorial process document behind this policy is a working internal artifact and is not yet published in full; the operative rules that govern what you see on this site are the ones stated on this page.

How to request a correction

The address for a written correction request is corrections@605buzz.com, but mail to it currently bounces (see the notice below), so today there is no way to send one. A request needs the article URL, the specific claim you're correcting, and (if applicable) documentation of the correct facts; have that ready and send it the day the mailbox opens. Once mail is live, we aim to acknowledge every request promptly and respond (with either the correction or an explanation of why we're declining) as promptly as practical after review; specific timing depends on the request.