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

The City of Madison's meeting portal lists "Community Center Advisory Committee Meeting" for Sept. 15, 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: meeting-madison-civicclerk-608

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

    Expanded reading — 605Buzz began publishing part of this record it had not published before; the record itself did not change

    605Buzz began publishing the numbered item lines from the agenda file this article already linked to

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

    Added (8 lines)

    • The city's agenda for this meeting lists 3 numbered items, reproduced below exactly as the city wrote them:
    • - 1. Community Center/EmBe Facility Usage Agreement Review
    • - 2. 2027 Budget Draft Review
    • - 3. Review and acknowledge Revenue / Expense Reports – August 2026
    • 605Buzz reproduces the numbered item lines from that file and nothing else. Lines the city labels Petitioner, Property Owner, Location or Staff Report are not reproduced here, and neither is a street address; the agenda packet is not read at all. Where an item names a person — an official presenting it, or a resident being appointed to something — that name is part of the item the city wrote, and it stands as written. The text is the plain-text rendering the city's own portal returns for that file. Nothing above is a summary, and an item on an agenda is something a body may consider rather than something it did.

    Content hash: 6fb57a6afa4fdf8d25aea145011a288b182a5ef0eff3f10d5846d512f62aef5f

  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: ad27f8eb4fbe7d50ae51d207bbda2c16de6e8ea077d6ba2a6b49cee61d22d9a0

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.