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

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.

• game-sdsu-15199 — v2, Source update — the underlying public record changed , Sept. 8, 2026, 7:05 a.m. CT
• meeting-spearfish-civicclerk-1995 — v3, Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change , Sept. 8, 2026, 7:04 a.m. CT
• meeting-minnehaha-county-civicclerk-749 — v3, Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change , Sept. 8, 2026, 7:02 a.m. CT
• sd511-restriction-12892252 — v12, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-road-work-12905663 — v7, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-restriction-12888149 — v6, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-road-work-12885780 — v6, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-restriction-12885780 — v6, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-road-work-12905246 — v4, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-road-work-12905358 — v3, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• sd511-restriction-12905358 — v3, Source update — the underlying public record changed , Sept. 8, 2026, 7:02 a.m. CT
• alert-e14699a7fc48ecfb122e9718144f778edace9b09-001-1 — v2, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-134415 — v14, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-135530 — v14, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-136062 — v8, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-137055 — v3, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-137164 — v3, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-137365 — v3, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• auction-sdauctions-137391 — v2, Source update — the underlying public record changed , Sept. 8, 2026, 7:01 a.m. CT
• event-sturgis-wet-t-shirt-contest-sidehack-saloon-daily-a-6ctnn1 — v8, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-texas-hippie-coalition-wednesday-august-12-15dziqo — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-jackpine-gypsies-motorcycle-club-august-10th — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-thunderdome-slow-races-august-10th-530pm — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191496 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191485 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191491 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191487 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191494 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191498 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191483 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191489 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191481 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191479 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191477 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191459 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191471 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191467 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191475 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191455 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191465 — v2, Clarification , Sept. 7, 2026, 6:43 p.m. CT
• event-sturgis-191469 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191473 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191457 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191104 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191101 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191031 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191089 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-190797 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-191070 — v2, Clarification , Sept. 7, 2026, 6:42 p.m. CT
• event-sturgis-190983 — v2, Clarification , Sept. 7, 2026, 6:42 p.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. 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 (email, letter, court filing, counsel demand). 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. Prompt review: we draft the correction and retain counsel review for any defamation-risk-adjacent matter, as promptly as practical.
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, newsletter, agent-native API) 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. A subject or auditor with a specific request may write to corrections@605buzz.com. We aim to acknowledge such requests promptly; scope depends on the request + counsel review.

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 correction cassette carries a jurisdictions array of ISO 3166-2 codes, so cross-jurisdictional retractions can be queried by locale for internal audit and downstream propagation.

Reason codes

Every correction is stored with one reason code, and the ledger shows it verbatim. The system can record exactly seven 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. The public record did not change; what changed is how much of it we print
• 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, counsel instruction, 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 today — 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

Send a written correction request to corrections@605buzz.com. Include the article URL, the specific claim you're correcting, and (if applicable) documentation of the correct facts. 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 jurisdiction, publisher-class, and counsel review.