Skip to main content
605Buzz
Today Search Corrections About Join waitlist
605Buzz

Corrections record

Public safety / First published

Severe Thunderstorm Watch issued Aug. 12, 2026 by NWS Rapid City SD

Published automatically from public-record data — not reviewed by an editor. This heading is the article's current headline.

Article identifier: alert-69d98c5289eb621c4ce74c3ac25944b6c55f38c5-002-1

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

    Clarification

    operator: moved this desk's methodology out of the article text into the collapsed 'How this desk works' footer, where the rest of the desk already carries it. The same explanations are still on the page. No fact about the road changed, and no sentence was newly written.

    The body text changed; the headline did not. (compared against version 2)

    Removed (2 lines )

    • See the [corrections ledger](/corrections) if a field is wrong.

    Content hash: f231e5f457bb78f77ddaac799ca8c2c17becb649fe4b745cb9dd3d8c3f1b0bdc

  2. Version 2

    Clarification

    operator: rewrote machine timestamps as South Dakota clock readings, shown in both of the state's zones. The instants are unchanged and come from this article's own stored record; only how they are printed changed. The sentence naming the old zone was replaced because the new clocks made it untrue.

    The body text changed; the headline did not. (compared against version 1)

    Removed (5 lines )

    • **NWS Rapid City SD issued a Severe Thunderstorm Watch** on 2026-08-11T19:51:00-06:00, according to the National Weather Service's public alert record.
    • The alert states an effective time of 2026-08-11T19:51:00-06:00, an onset of 2026-08-11T19:51:00-06:00, and an expiry of 2026-08-11T22:00:00-06:00. Times are as the issuing office published them, in that office's own offset.
    • The alert separately states that the hazard itself ends at 2026-08-11T22:00:00-06:00. That is a different field from the message's expiry above and the two can differ.
    • The full text of the alert as issued on 2026-08-11T19:51:00-06:00, reproduced without changes:
    • The National Weather Service superseded this message at 2026-08-11T22:02:00-06:00 with a later one. This article records the message as issued.

    Added (5 lines)

    • **NWS Rapid City SD issued a Severe Thunderstorm Watch** on Aug. 11, 2026, 7:51 p.m. MDT / 8:51 p.m. CDT, according to the National Weather Service's public alert record.
    • The alert states an effective time of Aug. 11, 2026, 7:51 p.m. MDT / 8:51 p.m. CDT, an onset of Aug. 11, 2026, 7:51 p.m. MDT / 8:51 p.m. CDT, and an expiry of Aug. 11, 2026, 10 p.m. MDT / 11 p.m. CDT. South Dakota spans two time zones and this alert may reach both, so each instant is shown in Mountain and then Central time; the office's own published offset is preserved in the machine-readable record.
    • The alert separately states that the hazard itself ends at Aug. 11, 2026, 10 p.m. MDT / 11 p.m. CDT. That is a different field from the message's expiry above and the two can differ.
    • The full text of the alert as issued on Aug. 11, 2026, 7:51 p.m. MDT / 8:51 p.m. CDT, reproduced without changes:
    • The National Weather Service superseded this message at Aug. 11, 2026, 10:02 p.m. MDT / 11:02 p.m. CDT with a later one. This article records the message as issued.

    Content hash: f8ce3b8202d04853bcf2bad2881d127dd5588e25ab10d959512c0552d3f49dd4

  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: 4937105e34462ca9ff6395284fccaefed8bfdd35219ebea638fe087efa523181

2 corrections have been issued.

See something wrong? Read the corrections policy or write to corrections@605buzz.com.