# path_claim baseline -- the MISSING paths this archive already carried when
# path_claim_check.py first censused it. One row: <path>\t<CLASS>\t<reason>.
# Regenerate the census (not the reasons): path_claim_check.py --repo . --context
# A row is a stated reading, not an exemption: --fail-on-missing fails on any
# MISSING path this ledger does not name, and every row here is printed with its
# class on every run, so a reader sees the exceptions instead of trusting that
# there are none. A row whose path later appears in the tree is reported CLEARED
# and can be deleted; a row the census no longer produces is reported DEAD.
# Classes: PLANTED (a file planted in a clone to measure a gate), NOT_ADDED (the
# prose states the file was never added on any ref), RENAMED (the artifact exists
# under a later name), SHORT_NAME (the prose cites an abbreviated form of a real
# artifact), FOREIGN_TREE (a path relative to another project's tree), EXAMPLE (a
# metasyntactic illustration quoted as a path -- foo/bar shape -- in prose about
# paths, not an assertion that a file exists), TARGET (an imperative sentence --
# "Post <path>" -- names a deliverable its owner owes; no ref holds it, the row
# names the asking file:line and `git log --all --diff-filter=A` -> 0 commits).
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
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
recoveries/summary-fidelity-full.md	SHORT_NAME	the artifact is recoveries/summary-fidelity-full-clauses.md; the queue cites the short form
checkins/2026-10-19-volt-02.md	PLANTED	planted in a clone of 3890c12 to measure the gate hole; the citing sentence says so
checkins/2026-10-02-volt-b.md	PLANTED	planted in a clone of e98a34b as the backdated-name example; the citing sentence says so
docs/release-engine-spec.md	FOREIGN_TREE	relative to another project's tree (src/, tests/): neither is tracked here
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
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
docs/bar.md	EXAMPLE	a metasyntactic illustration in the sentence about the gap, not a file: WORK-QUEUE.md:10362 quotes "the record docs/bar.md" as the shape of a path claim; no ref ever held it
recoveries/foo.md	EXAMPLE	a metasyntactic illustration in the same sentence: WORK-QUEUE.md:10362 quotes "recoveries/foo.md" as the shape of a path claim; no ref ever held it
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
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
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