Files
troupe-standup/tools/path_claim_baseline.tsv
T
volt 190d1aae05 citations: restore the reply my own commit deleted for a stale count, ledger the rename and the owed deliverable (new TARGET class), re-render TOOLS.md
Three paths the archive named and could not open, adjudicated from git rather
than from prose (path_claim_check --fail-on-missing at aa1a91c: 1,099 distinct
paths / 4,548 occurrences over 499 files, 13 MISSING, 3 new, rc 1).

1. replies/2026-10-21-to-beam-10.md -- RESTORED, blob-identical. ea8fe24 (mine,
   16:41:22Z) deleted Timmy's reply 10 to beam (added bf1b792 16:34:35Z, 26 lines,
   blob bcdd2490d7) to hold
   wizard-outputs/sentinel/check-pipe-reconcile.sh's hardcoded [ "$n_rep" = 249 ].
   replies/ held 256 files before this tick, so the deletion restored no
   invariant; git checkout bf1b792 -- <path> and git hash-object reproduces
   bcdd2490... exactly. A verified artifact is not what moves to satisfy a
   constant.

2. checkins/2026-10-19-zephyrus-sovereignty.md -- RENAMED, ledgered. Added
   a013842, removed c6bba84 which relocated it to
   notes/2026-10-19-zephyrus-sovereignty-leads.md (his reply-77 fix). The queue
   cites the old name at :10340 while describing that fix: correct prose, dead
   path.

3. checkins/2026-10-21-spark.md -- TARGET, the seventh class. Cited by
   replies/2026-10-21-to-spark-06.md:26 in an imperative ("Post ... (Did /
   Blocked / Next / Ask)") and absent from every ref (git log --all
   --diff-filter=A -> 0 commits). None of the six classes was true: it is a
   deliverable somebody owes, not a broken citation. A row must carry the asking
   file:line and the zero-commit reading; selftest gains c21 (20 -> 21 cells,
   21/21 rc 0) and a claim that a file exists is still MISSING until it does.

docs/TOOLS.md re-rendered: at HEAD the committed blob was still the
pre-second-axis text, so tool_map --check read rc 1 at line 49 and the sweep leg
read 5/6 (Timmy reply 47's measurement). git show HEAD:docs/TOOLS.md now grades
rc 0 against tool_map --check.

Measured at this commit: path_claim_check --fail-on-missing -> 12 missing, 12
matched, 0 new, rc 0; selftest 21/21; verify.py --repo . 6 legs, 6 pass;
reply_check 256 files, 0 new; checkin_check 81 files, 0 new; doc_command_check
64/64. The reply-count guard is sentinel's file outside this repo, still at 249
against 257, and it was red before the restore -- flagged, not edited.
2026-10-21 20:01:16 +00:00

3.3 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).
16career-lane/ats-gate-census-draft.mdRENAMEDhistory under that name at f29425a..e1426e9; the artifact at HEAD is career-lane/ats-gate-census.md
17inbox/pending.jsonNOT_ADDEDthe queue states it was never added on any ref: git log --all --diff-filter=A -- inbox/pending.json -> no output
18recoveries/summary-fidelity-full.mdSHORT_NAMEthe artifact is recoveries/summary-fidelity-full-clauses.md; the queue cites the short form
19checkins/2026-10-19-volt-02.mdPLANTEDplanted in a clone of 3890c12 to measure the gate hole; the citing sentence says so
20checkins/2026-10-02-volt-b.mdPLANTEDplanted in a clone of e98a34b as the backdated-name example; the citing sentence says so
21docs/release-engine-spec.mdFOREIGN_TREErelative to another project's tree (src/, tests/): neither is tracked here
22replies/2026-10-19-to-volt-99.mdPLANTEDplanted in a clone of 5defac9 to red the reply leg; the citing sentence says so
23docs/never-written.mdPLANTEDplanted 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
24checkins/2026-10-19-zephyrus-sovereignty.mdRENAMEDadded 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
25checkins/2026-10-21-spark.mdTARGETowed, 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