Files
troupe-standup/tools/path_claim_baseline.tsv
T
volt 0c43d55b1d path_claim_check: a second (document-relative) base, graded as DOCREL; 27 cells
The census graded every path token at the repo root, so an artifact naming its own
scripts read MISSING while the files sat beside it: six of the seven new rows at
40f1095 were a base mismatch (four in the sphinx needle-grounding REPORT.md:49-52,
two quoted from the archive digest.md), and the seventh was a real rename.

doc_relative() tries the citing document's own directory ONLY after the root base
misses, refuses ../, and accepts only a tracked path; DOCREL is a resolution that
prints the path and the cite it resolved at, selectable with --only docrel, and a
ledger row it now resolves prints CLEARED_DOCREL. The root base always wins (c24),
a root document gets no second base (c23).

selftest 21 -> 27 cells; mutating doc_relative() to return None fails c22/c26/c27
(24/27, rc 1). Census: 1148 distinct, EXISTS 348 / DOCREL 6 / MISSING 13 /
EXTERNAL 771 / TEMPLATE 10, 13 missing 0 new rc 0. One ledger row added:
replies/2026-10-22-to-null-01.md RENAMED (7a472a4, added d659219).
2026-10-22 14:11:27 +00:00

3.5 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
26replies/2026-10-22-to-null-01.mdRENAMEDrenamed 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