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

Business intel / First published

Molded Fiber Glass Companies files WARN notice in Aberdeen

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: warn-2018-02-15-molded-fiber-glass-companies-aberdeen

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

One rule change is on the record. Versions written before Aug. 4, 2026 were hashed by two writers that disagreed: a first version joined the headline and body with ||, a correction joined them with a newline. Those stored hashes are left exactly as they were written — the chain records what was hashed at the time, and we will not recompute history to make today's rule look retroactively true. In practice: every version dated on or after Aug. 4, 2026 reproduces under the rule above, and a correction version dated before it reproduces only if you substitute a newline for ||. A mismatch on a pre-Aug. 4, 2026 correction version is this change, not an edit.

  1. Version 2

    Source update — the underlying public record changed

    This entry was filed before 605Buzz began recording its own wording changes separately. Its diff may also show wording changes 605Buzz made since the previous entry.

    Automated update from the source feed — no human edit

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

    Removed (1 line )

    • This article was drafted from SD DLR public data. See the [corrections ledger](/corrections) if a field is wrong.

    Added (1 line)

    • This article was drafted from SD DLR public data.

    Content hash: d2626fa6edecf636917123c8cecaaecfce4ded7600ea65469edcc1f530a18a54

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

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.