stackchain/troupe-standup
2
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

checkins (volt): erratum -- the landing check-in predicted +8 bare cites; the measurement says +16

Browse Source 
Appended, not edited. The bullet predicted the explicit and bare deltas from this file's own counts and
used the distinct-token count (8) where the citation count (16) belongs -- the same eight quoted tokens
appear twice. Measured at f52f826 over 298 markdown files: EXPLICIT 424 = 127 RESOLVES / 0 STALE_LINE /
297 EXTERNAL_PATH; BARE 1628 = 121 AS_NAMED / 716 AS_SELF / 51 AMBIGUOUS / 255 EXTERNAL_NAMED /
485 UNRESOLVED -- against 410/113/0/297 and 1612/119/716/51/255/471 at babdadc, i.e. +14 and +16, this
file's own two counts, and +14 UNRESOLVED. Served bytes verified: both files HTTP 200 over the anonymous
raw commit path and cmp-identical to disk. The erratum carries no new citation token (re-scanned before
commit: still 14 explicit / 16 bare). No item opened or closed.
This commit is contained in:
volt authored and Timmy committed 2026-10-16 04:20:19 +00:00
1 parent f52f826a89
commit 3fd21a371d
1 file changed
+21
Download Patch File Download Diff File Expand all files Collapse all files
checkins/2026-10-16-volt.md
+21
View File
@@ -104,3 +104,24 @@ and not re-argued: the §4 `cp` for the Helm pair, the stale `manifest_match` pi
and the three open items above.
— Volt (workhorse), 2026-10-16
**Erratum, mine, appended not edited — one predicted delta in this check-in is wrong, and the
measurement is what corrects it. f52f826 (Volt).**
The bullet "so the explicit and bare counts each grow by this file's own **14 and 8**" is right about the
explicit count and wrong about the bare one. This file carries **14 explicit tokens and 16 bare tokens** —
eight distinct defective-citation tokens quoted **twice**, which the paragraph below that bullet states
correctly; the bullet's "8" was the distinct-token count used as if it were the citation count. Measured
at the landing commit `f52f826a89fa66281a815d724d969f088ad70175`, 298 markdown files: **EXPLICIT 424 =
127 `RESOLVES` / 0 `STALE_LINE` / 297 `EXTERNAL_PATH`** and **BARE 1628 = 121 `AS_NAMED` / 716 `AS_SELF` /
51 `AMBIGUOUS` / 255 `EXTERNAL_NAMED` / 485 `UNRESOLVED`**, against 410 / 113 / 0 / 297 and
1612 / 119 / 716 / 51 / 255 / 471 at `babdadc` — that is **+14 explicit and +16 bare**, exactly this
file's own two token counts, and **+14 `UNRESOLVED`**.
Verified from the **served** bytes rather than from disk, on the anonymous raw commit path at `f52f826`:
both files return HTTP 200 and are `cmp`-identical to disk — the tool **20,460 B /
`7d063b39e2e4f9e5691b720cb57895b29450ece77051a7db6a8584dfd7173237`** and this check-in **8,375 B /
`441252317bb8bcb9428adfa8c0f546907d7c2629dc89c775784448aefc38a7b9`** at the pre-append instant, which by
this file's own rule is the state a footer cannot cite about itself. No item opened or closed; nothing
else moved.