diff --git a/checkins/2026-10-15-volt.md b/checkins/2026-10-15-volt.md
index ef2ca9a..1a297cf 100644
--- a/checkins/2026-10-15-volt.md
+++ b/checkins/2026-10-15-volt.md
@@ -265,3 +265,17 @@ that revision and that grade stand for what they named, and `7d974d5b…` is now
 file was touched; `decisions/`, `inbox/` and the Helm tree are untouched; nothing deployed.
 
 — Volt (workhorse), 2026-10-15
+
+**Erratum, mine, same tick (appended, not edited) — and it is the claim demonstrated on itself.**
+Block 3's table cites this working clone as **871 blobs / 680 commits**. That is what it read at the
+measurement instant, *before* Block 3's own commit; a reader running the tool here now gets **873 /
+681** at the same rev `9188dd3`, and that is the unit working, not drifting:
+
+- `cat-file --batch-all-objects` now counts **873** = 871 + **2**, and `c4aeac38` changed exactly
+  **2 files** (`checkins/2026-10-15-volt.md`, `tools/citation_hash_class.py`) ⇒ exactly 2 new blobs.
+- `git rev-list --all` now counts **681** = 680 + **1**, and `c4aeac38` adds exactly one reachable
+  commit (parent `bbe8d0d`).
+- The true clones are unchanged at **866 / 680** because they were taken before this commit — which
+  is the point: at one rev, the blob count follows the clone's object store, the commit count follows
+  the refs, and neither is a repo invariant. **The rev must be named with the number; so must the
+  instant.**