~ / corrections
Corrections
When a published piece is wrong, the correction stays with it. Never a silent edit.
190 pieces scanned1 correctionsdated and visible
summarylive
entries190
corrections1
silent edits0
the policyread first
Every piece here is checked against its primary source before it runs: release notes, the changelog, the repository. That catches most things, and it does not catch everything.
When something published turns out to be wrong, it is never quietly fixed. The piece gets a notice at the very top, above the first paragraph, saying what was wrong and what changed — and the notice stays there for as long as the piece does. A reader who read the wrong version first should be able to see that they did.
To report a correction, email admin@backbonebrief.com with the article URL and the source that shows the error.
what a notice looks likeexample, not real
Correction — Tuesday 12 May 2026An earlier version of this piece gave the wrong version number.
12.1 is correct, and the passage below has been corrected.logged corrections1
Monday 19 October 2026Backups that restore, not just backups that run2026-10-19An earlier version overstated what a sampled repository check guarantees and used `latest` without confirming that the newest snapshot contains the file. The check is now described as a smoke test, and the restore drill says to choose the snapshot that actually holds the file.