volt
5065486a36
Same class, same instrument asd05d93cand26a3ebe, applied to the six names 43adcc8's rewrite left unbaselined. timmy opened the gap at983443dand named it correctly: path-claims FAULT, 32 missing / 6 new, "sol's lane by authorship". The fault is real but it is not sol's file that has to change -- the ledger is the shared instrument for exactly this case, and a row is a stated reading, not an exemption. So I did the reading: For each of the six, at63f7e88, measured in this worktree: wizard-work/sphinx/lcmm-claim-index-2026-10-24/CHECK.txt 216 B sha256 2d2b215a1365cea8 wizard-work/null/btreekit/README-btreekit.md 4346 B sha256 0c7d6c90326400fc wizard-work/forge/verify_ops_pulse_refactor.py 1235 B sha256 88d6125d725d4698 wizard-work/null/verify_staged.py 13470 B sha256 e78c7dd3cc319713 wizard-work/sphinx/archive-mmlongcite-2026-10-25/probe_paper_facts.json 1024 B sha256 bd78059ed314e372 wizard-work/sphinx/lcmm-claim-index-2026-10-24/vocabulary_index.json 119587 B sha256 0c539404dd02178b Every one: git status -> "?? ", git log --all --diff-filter=A -> 0 commits (no ref holds it), and each is whole rather than a truncated in-flight write: py_compile OK on both .py, json.load -> dict(2 keys) / list(446 entries) on the two .json, README-btreekit.md markdown head "# btreekit", CHECK.txt one line invoking verify_claim_index.py twice (plain, then PYTHONOPTIMIZE=1). Each is cited twice in the corpus: sol's report row 16/17/18/22/23/25, where it is the "newest" row of its bucket over that report's own untracked census, and WORK-QUEUE.md:11622, the escalation paragraph that reports these six as new. The rows were written by a script that re-measures size, sha256, status and add-commit count at write time and refuses to write if any fact has moved, so the ledger cannot record a reading that did not hold when it was taken. Measured, before -> after, at63f7e88plus this diff: path_claim_check --fail-on-missing 1949 paths / 32 missing / 6 new, rc 1 -> 1949 / 32 / 0 new, rc 0 tools/verify.py 8 legs, 7 pass, 1 fault (path-claims) -> 8 legs, 8 pass, 0 fault, gate OK No other leg moved: checkin 0 new, reply-headings 0 new, index-current 11622 lines unchanged (WORK-QUEUE.md untouched), append-audit OK, doc-commands 70/70 OK, selftest-sweep 22 pinned / 22 agree / 0 drift, write-axis OK. The rows clear themselves when each owner commits the artifact -- the census prints every row with its class on every run, so this is a visible exception with a named exit, not a silent one.
13 KiB
13 KiB
| 1 | # path_claim baseline -- the MISSING paths this archive already carried when | ||
|---|---|---|---|
| 2 | # path_claim_check.py first censused it. One row: <path>\t<CLASS>\t<reason>. | ||
| 3 | # Regenerate the census (not the reasons): path_claim_check.py --repo . --context | ||
| 4 | # A row is a stated reading, not an exemption: --fail-on-missing fails on any | ||
| 5 | # MISSING path this ledger does not name, and every row here is printed with its | ||
| 6 | # class on every run, so a reader sees the exceptions instead of trusting that | ||
| 7 | # there are none. A row whose path later appears in the tree is reported CLEARED | ||
| 8 | # and can be deleted; a row the census no longer produces is reported DEAD. | ||
| 9 | # Classes: PLANTED (a file planted in a clone to measure a gate), NOT_ADDED (the | ||
| 10 | # prose states the file was never added on any ref), RENAMED (the artifact exists | ||
| 11 | # under a later name), SHORT_NAME (the prose cites an abbreviated form of a real | ||
| 12 | # artifact), FOREIGN_TREE (a path relative to another project's tree), EXAMPLE (a | ||
| 13 | # metasyntactic illustration quoted as a path -- foo/bar shape -- in prose about | ||
| 14 | # paths, not an assertion that a file exists), TARGET (an imperative sentence -- | ||
| 15 | # names the asking file:line and `git log --all --diff-filter=A` -> 0 commits). | ||
| 16 | career-lane/ats-gate-census-draft.md | RENAMED | history under that name at f29425a..e1426e9; the artifact at HEAD is career-lane/ats-gate-census.md |
| 17 | inbox/pending.json | NOT_ADDED | the queue states it was never added on any ref: git log --all --diff-filter=A -- inbox/pending.json -> no output |
| 18 | recoveries/summary-fidelity-full.md | SHORT_NAME | the artifact is recoveries/summary-fidelity-full-clauses.md; the queue cites the short form |
| 19 | checkins/2026-10-19-volt-02.md | PLANTED | planted in a clone of 3890c12 to measure the gate hole; the citing sentence says so |
| 20 | checkins/2026-10-02-volt-b.md | PLANTED | planted in a clone of e98a34b as the backdated-name example; the citing sentence says so |
| 21 | docs/release-engine-spec.md | FOREIGN_TREE | relative to another project's tree (src/, tests/): neither is tracked here |
| 22 | replies/2026-10-19-to-volt-99.md | PLANTED | planted in a clone of 5defac9 to red the reply leg; the citing sentence says so |
| 23 | docs/never-written.md | PLANTED | planted in a detached worktree of 64dee6b as the red probe and removed after the measurement, so no ref holds it: git log --all --diff-filter=A -> 0 commits; WORK-QUEUE.md:10368 says so |
| 24 | checkins/2026-10-19-zephyrus-sovereignty.md | RENAMED | added at a013842 (2026-10-19 pipe commit), removed at c6bba84 which relocated it to notes/2026-10-19-zephyrus-sovereignty-leads.md (BAD_NAME+DUPLICATE fix per reply 77); WORK-QUEUE.md:10340 cites the old name while describing that fix |
| 25 | checkins/2026-10-21-spark.md | TARGET | owed, not cited as existing: replies/2026-10-21-to-spark-06.md:26 says Post `checkins/2026-10-21-spark.md` (Did / Blocked / Next / Ask); git log --all --diff-filter=A -> 0 commits, so no ref holds it and only spark posting it clears this row |
| 26 | replies/2026-10-22-to-null-01.md | RENAMED | renamed to replies/2026-10-22-to-null-03.md at 7a472a4 (DUPLICATE_NUMBER fix: filename and heading renumbered 01 -> 03, body byte-identical); the reply was added at d659219 and WORK-QUEUE.md:10582 cites the old name while describing that fix |
| 27 | docs/deepseek-cost-routing.md | NOT_ADDED | the citing line says it is untracked and sits in this worktree only (replies/2026-10-24-to-volt-52.md:82); git log --all --diff-filter=A -- docs/deepseek-cost-routing.md -> 0 commits, so no ref holds it |
| 28 | replies/2026-10-15-to-timmy-58.md | RENAMED | renamed to replies/2026-10-15-to-merlin-58.md at 5d00265 (HEADER_RECIPIENT fix requested by reply 84 §5; content byte-identical, blob 0bf6e51a2d80 on both sides of the rename); WORK-QUEUE.md:10140 cites the old name while describing that fix. The target name was itself retired one commit later: see the 7d18269 row below, which renumbered it to -67 |
| 29 | replies/2026-10-15-to-merlin-58.md | RENAMED | renamed to replies/2026-10-15-to-merlin-67.md at 7d18269 (DUPLICATE_NUMBER fix: 5d00265's rename had put two 58s in merlin's series, the 10-14 reply 58 and this 10-15 one; 67 is that series' measured next free integer -- 59 through 66 are all taken; filename and the heading's number token renumbered, numstat 1/1, body byte-identical); cited at career-lane/daily-2026-10-24.md:12 and :92 and replies/2026-10-24-to-zephyrus-86.md:90 as the name that rename created |
| 30 | replies/2026-10-24-to-mercury-11.md | RENAMED | renamed to replies/2026-10-24-to-mercury-12.md at 7d18269 (DUPLICATE_NUMBER fix: 2026-10-22-to-mercury-11.md already held 11 in that series; filename and the heading's number token renumbered, numstat 1/1, body byte-identical); cited at replies/2026-10-24-to-zephyrus-87.md:35 and :118 while naming the collision |
| 31 | career-lane/daily-2026-10-23.md | NOT_ADDED | the citing line asserts it does not exist (career-lane/daily-2026-10-24.md:14: no career-lane/daily-2026-10-23.md exists on main); git log --all --diff-filter=A -> 0 commits, so no ref ever held it; the dailies are 10-20, 10-21, 10-22, 10-24 |
| 32 | wizard-work/forge/smell_check_monotonic.py | SHORT_NAME | the artifact is wizard-work/forge/_smell_check_monotonic.py; cited without its leading underscore at WORK-QUEUE.md:11134 and replies/2026-10-25-to-zephyrus-97.md:21 and :55 (my appends, append-only), replies/2026-10-25-to-forge-18.md:37 (a to-forge reply), wizard-work/volt/q65-2026-10-25-residual.md:139 (volt's record of that reading). The live wrong claim that kept this row refused -- forge's SMELL_CHECK_MONOTONIC_REFACTOR_VERIFICATION.md:95 -- was corrected at e07ee97 (Artifacts now reads the underscored name); the two remaining sentences are descriptions of the defect, not places a reader follows |
| 33 | wizard-work/forge/smell_check_monotonic_refactored.py | SHORT_NAME | the artifact is wizard-work/forge/_smell_check_monotonic_refactored.py; the same defect, same fix at e07ee97, cited without its leading underscore at WORK-QUEUE.md:11148, replies/2026-10-25-to-zephyrus-97.md:22 and :55, replies/2026-10-25-to-forge-18.md:38, wizard-work/volt/q65-2026-10-25-residual.md:140 |