52 lines
14 KiB
Plaintext
52 lines
14 KiB
Plaintext
# 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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
recoveries/apply-queue-status-2026-10-25.md NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:25 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (6271 B, sha256 12da1c5ef134a2f3, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
|
|
wizard-work/forge/_repro_bounds_original.py NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:21 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (900 B, sha256 498a42813df9a3d3, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
|
|
wizard-work/null/README-gatehygiene.md NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:20 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (7478 B, sha256 0c9e3060f15c37bd, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
|
|
wizard-work/null/_probe_repro7.py NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:24 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (1449 B, sha256 093b88d3cac7f587, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
|
|
wizard-work/null/gatehygiene.py NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:23 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (21867 B, sha256 e1d964ed3c380c54, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
|
|
wizard-work/sphinx/lcmm-claim-index-2026-10-24/DOSSIER.md NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:26 names it as a bucket's "newest" row over that report's own untracked census (its header measures 119 untracked files); untracked in this worktree (21874 B, sha256 cea2a26c1684d0d6, git status -> "?? "), and git log --all --diff-filter=A -> 0 commits, so no ref holds it; the row clears when its owner commits it
|
|
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
|
|
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
|
|
wizard-work/ledger/verify_dates.py NOT_ADDED pending work, not an artifact at a14a132: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:19 names it as the LEDGER bucket's "newest" row in the report's rewritten tick (4465237; its header now measures 125 untracked / 125 pending, was 119 at 5cae75b); untracked in this worktree (1172 B, sha256 717e81b33a0fd231), git log --all --diff-filter=A -> 0 commits
|
|
wizard-work/volt/q60_truncated_census.py NOT_ADDED pending work, not an artifact at a14a132: wizard-work/sol/daily-local-pipe-triage-2026-10-25.md:20 names it as the LORE bucket's "newest" row in the same rewritten tick (4465237); untracked in this worktree (14363 B, sha256 e8d61c033781faee), git log --all --diff-filter=A -> 0 commits
|
|
wizard-work/sphinx/lcmm-claim-index-2026-10-24/CHECK.txt NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:16 names it as the CHECK bucket's "newest" row (bucket count 2) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (216 B, sha256 2d2b215a1365cea8, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: one line, two verify_claim_index.py runs (plain, then PYTHONOPTIMIZE=1); also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
|
|
wizard-work/null/btreekit/README-btreekit.md NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:17 names it as the DOC bucket's "newest" row (bucket count 4) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (4346 B, sha256 0c7d6c90326400fc, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: markdown, head `# btreekit`; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
|
|
wizard-work/forge/verify_ops_pulse_refactor.py NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:18 names it as the FORGE bucket's "newest" row (bucket count 7) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (1235 B, sha256 88d6125d725d4698, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: py_compile OK; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
|
|
wizard-work/null/verify_staged.py NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:22 names it as the NULL bucket's "newest" row (bucket count 42) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (13470 B, sha256 e78c7dd3cc319713, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: py_compile OK; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
|
|
wizard-work/sphinx/archive-mmlongcite-2026-10-25/probe_paper_facts.json NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:23 names it as the PROBE bucket's "newest" row (bucket count 32) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (1024 B, sha256 bd78059ed314e372, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: json.load -> dict, 2 keys; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
|
|
wizard-work/sphinx/lcmm-claim-index-2026-10-24/vocabulary_index.json NOT_ADDED pending work, not an artifact at HEAD: wizard-work/sol/daily-local-pipe-triage-2026-10-26.md:25 names it as the SPHINX bucket's "newest" row (bucket count 43) over that report's own untracked census (147 untracked / 3 modified at 2026-10-26T03:51:30Z); untracked in this worktree (119587 B, sha256 0c539404dd02178b, git status -> "?? "), git log --all --diff-filter=A -> 0 commits, so no ref holds it; whole: json.load -> list, 446 entries; also cited at WORK-QUEUE.md:11622 (the escalation paragraph that reports these six as new). The row clears when its owner commits the artifact.
|
|
wizard-work/beam/test_jsonl_validate.py NOT_ADDED Q104's done-condition names this file as the suite to be written, not an artifact that was lost: `git log --all --diff-filter=A -- wizard-work/beam/test_jsonl_validate.py` -> no output and `git status --short wizard-work/beam` is clean, so no ref and no worktree holds it. The row clears when Q104 lands its test file and the lane CHECK runs it.
|