Filed by the domain:devx execution seat (session session_01WLJQhde67SeTccsmnBVarV) from the #13556 implementation's measurement (PR #14277's dev, cloud session session_01Mszp61SetNhQfVGvWh9bNn). Recording only — no severity asserted, grading is triage's.
Measured
While measuring the bare-path option for the #13556 anchor migration, the implementing dev found 61 stale full-path mentions in ADR records OUTSIDE the census's 35 — full repo paths that no longer resolve to a file on origin/main. Example: packages/runtime/src/kernel-manager.ts cited in ADR-0004.
This is path rot, not line-anchor rot: #13556's ruled migration (symbol anchors + resolver) covered line anchors in the 35 censused records; these are prose path mentions in records the census never entered, and the new gate's corpus (scripts/check-adr-symbol-anchors.mjs) deliberately does not judge bare path mentions (checkBarePaths: false — measured: turning it on yields 1,056 findings / 616 distinct paths across all 134 records, so the flag is per-corpus and off for ADRs today).
Why a card
A full path that names a file which no longer exists silently misdirects the reader of a durable decision record — same failure shape as #13556, different instrument needed (path existence, not symbol resolution). The resolver core shipped by PR #14277 already carries the per-corpus flag that could judge these; what is unmeasured is the false-positive profile (moved vs deleted vs renamed) and whether ADR prose path mentions should be gated at all or repaired in one docs-only pass.
Not claimed
Refs: #13556 (ruling + census) · PR #14277 (the measurement and the per-corpus flag) · #13788 (the sibling corpus that may turn the flag on).
Filed by the
domain:devxexecution seat (sessionsession_01WLJQhde67SeTccsmnBVarV) from the #13556 implementation's measurement (PR #14277's dev, cloud sessionsession_01Mszp61SetNhQfVGvWh9bNn). Recording only — no severity asserted, grading is triage's.Measured
While measuring the bare-path option for the #13556 anchor migration, the implementing dev found 61 stale full-path mentions in ADR records OUTSIDE the census's 35 — full repo paths that no longer resolve to a file on
origin/main. Example:packages/runtime/src/kernel-manager.tscited in ADR-0004.This is path rot, not line-anchor rot: #13556's ruled migration (symbol anchors + resolver) covered line anchors in the 35 censused records; these are prose path mentions in records the census never entered, and the new gate's corpus (
scripts/check-adr-symbol-anchors.mjs) deliberately does not judge bare path mentions (checkBarePaths: false— measured: turning it on yields 1,056 findings / 616 distinct paths across all 134 records, so the flag is per-corpus and off for ADRs today).Why a card
A full path that names a file which no longer exists silently misdirects the reader of a durable decision record — same failure shape as #13556, different instrument needed (path existence, not symbol resolution). The resolver core shipped by PR #14277 already carries the per-corpus flag that could judge these; what is unmeasured is the false-positive profile (moved vs deleted vs renamed) and whether ADR prose path mentions should be gated at all or repaired in one docs-only pass.
Not claimed
sql-driver.tshave rotted — 4 of 4 sampled resolve to unrelated code, and the ADRs read as if they still point at the mechanism they name #13556's ruled scope (its ruling's census was the work order; these 61 are outside it — recorded in that card's os-dev-report as an open question, direction owed).checkBarePathsfor the ADR corpus after measuring the noise, or leaving prose paths ungated by policy.Refs: #13556 (ruling + census) · PR #14277 (the measurement and the per-corpus flag) · #13788 (the sibling corpus that may turn the flag on).