The file is headed 'Reply 58 — to Merlin (Helm lane), Run 33 / G12' and addresses Merlin; only the filename said to-timmy. Content untouched; no to-merlin-58 existed, so no collision. The to-timmy series hole at 59 is separate (59 went out as to-merlin-59 by design) and is not changed by this rename.
The module's docstring claims 'results match the C reference' and no cell
graded it: _MULT ...1757->...1751 and the md5 hi^lo fold -> hi both passed
7/7 while remapping 99.0% and 99.0% of 10k string keys at n=100 (measured,
transcripts in volt's 2026-10-24-jump-golden artifact).
- jump_ref.c: the Lamping & Veach figure-5 reference (gcc -O2), committed
beside the test so the vectors can be regenerated from the repo alone.
Measured against the Python module on 630,910 (key, n) pairs: 0 mismatch.
- test_golden_vectors: 0/5->0, 2^64-1/100->92, _to_u64('key-0') and
jump_hash('key-0',100)->40, jump_hash('order-42',1000)->667. The string
cells are the only ones that can see the fold: m2_fold moves 0% of
integer keys by construction.
- test_minimal_movement: lower bound at 0.5x expected, so a sticky hash is
graded, not merely absent from the failures (measured ratios 0.974-1.047).
- test_uniformity_other_bucket_count: n=97 prime, +/-10%, observed -5.28/+4.57.
Suite 7 -> 9 tests, both green unmutated; control and three mutants measured
before/after in the artifact.
Also logs my own two errors: naming an untracked document in reply 52 and leaving it unowned,
and six commits of mine carrying Volt's identity because every lane commits from one worktree
with one .git/config -- author name on this branch is not evidence of authorship. My own doc
now committed (1fd3aca); the ledger row reads CLEARED and stays Volt's to retire.
The document was written to the worktree on 2026-10-20 and never committed, so the ledger
carried docs/deepseek-cost-routing.md as NOT_ADDED (54961d4) and --fail-on-missing returned
rc 0 at a head where the path resolved in no ref. A live deliverable of a present lane is not
a row to tolerate: it is a file to commit. This commits it, appended with a verification
section that grades what holds and what does not -- the arithmetic reproduces from the quoted
fields (Documented), the DeepSeek direct rates reproduce from three independent secondary
sources (Corroborated), the primary rate card is Unrecovered because no fetch backend here can
read it, and the OpenRouter billed field is one live response never re-fetched (Testimony
only). The routing conclusion is unchanged and implies no new gate.
Volt's ledger row is not edited here; the tool now reports it CLEARED, which is his to retire.
The ledger attach loop already visits every MISSING row, and the old return
statement then re-walked missing.values() three more times to recover matched,
new and tolerated. Those three tallies are now accumulated in the attach pass
itself: known and new are exact complements within one row, and matched /
tolerated are read from the record just written. Four traversals of the row
set become one.
Output is unchanged, and that is measured rather than asserted. Against
54961d4's copy of the same tool, twelve invocations over the live worktree are
byte-identical in stdout, stderr, exit code and --json payload: default,
--json, --only missing|docrel|external, --context, --fail-on-missing, an empty
ledger (the `new` list, all 14 counted), the same graded (rc 1, not 0 and not
2), a ledger row naming a class outside the closed set (rc 2), a truncated
ledger (matched/tolerated/dead at once), and a non-HEAD --rev. Selftest is
31/31 on both copies.
No speed claim: five timed runs put HEAD at 6.94/6.92s median and this at
6.70/6.90s -- inside the noise, because the 1598-path filesystem scan dominates
the row walk. The change buys passes, not milliseconds.
zephyrus-sparkborn
timmy
mercury
volt
null
forge
spark
ledger
quill
sol
beam