Skip to main content

1 of 17 desks have not been read in over 48 hours. 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

community / First published

Pierre's Library calendar lists "Rawlins Library Chess Club" for November 5, 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: community-pierre-2371

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 2

    Source update — the underlying public record changed

    Automated update from the source feed — no human edit

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

    Removed (1 line )

    • The city's feed says it published this entry on 2026-07-22 at 18:48, printed as published. That is when the listing went up, not when the event is. The feed labels that time -0600, which is the publishing platform's own default rather than a statement about this city, so it is recorded but not applied.

    Added (1 line)

    • The city's feed says it published this entry on 2026-10-26 at 17:39, printed as published. That is when the listing went up, not when the event is. The feed labels that time -0600, which is the publishing platform's own default rather than a statement about this city, so it is recorded but not applied.

    Content hash: d5bebcb8cee9094c819f8cd09e2eb97c6376209ee8315c795767b09c05f6875a

  2. 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: 17032653dd65edf6226a1e717bf24a92c933c3ca30e4f87e39164b399d3d9678

1 correction has 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.