Corrections record
Business intel / First published
Accelerate360 Distribution, LLC – Dakota Merchandising Remote Work files WARN notice in Sioux Falls
Published automatically from public-record data — not reviewed by an editor. This heading is the article's current headline.
Article identifier: warn-2025-04-25-accelerate360-distribution-llc-dakota-merchandising-remote-work-sioux-falls
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.
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. In 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.
-
Version 2
Factual correction
Corrected extraction — we fixed how 605Buzz reads this source and re-published the article from the corrected reading; the public record itself did not change, our extraction of it did
The body text changed; the headline did not. (compared against version 1)
Removed (1 line )
- The filing describes a workforce action in Sioux Falls, per a notice the DLR received April 25, 2025. The notice does not state when the workforce action takes effect. 324 employees are affected (11 reside in South Dakota, per the notice).
Added (1 line)
- The filing describes a workforce action in Sioux Falls, per a notice the DLR received April 25, 2025. The notice does not state when the workforce action takes effect. 324 employees are affected (11 reside in South Dakota, per the notice).
Content hash:
ba118ba7bc5e049945cc70fa9a0631f799e93c4f8f5fbcc0e1bd15f5a7f57d9b -
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:
3d38b6f768f957b3f9615243b6783b461a8ba5cdd26e8b468a2f5d6ed2fff2b7
1 correction has been issued.
See something wrong? Read the corrections policy or write to corrections@605buzz.com.