Measured
docs/META_DASHBOARD.md carries a "CLARA Deliverables Progress" table — twice — whose Location column names four paths. None is on disk:
MISSING docs/clara/test_vectors/
MISSING docs/clara/clara_test_vectors_2026-04-08.zip
MISSING docs/clara/CLARA_TECHNICAL_NARRATIVE.md
MISSING docs/clara/CLARA_INTEGRATION_GUIDE.md
EXISTS docs/clara/examples/
They were produced — git log --diff-filter=A names c1582008b — and removed on 2026-04-19 by 91653d2b9, "fix(bootstrap): restore working main.rs — recovery from detached HEAD (#523)", a 1214-file recovery commit that took them out as collateral. The table has read ✅ COMPLETE for four and a half months.
Proposed
Correct the rows rather than delete them — DELIVERED, then removed in 91653d2b9 — so the work is still recorded and the files stay recoverable from 91653d2b9^. A dashboard that quietly drops a deliverable is worse than one that says where it went.
Plus a check: every path a status table marks COMPLETE must exist.
The matcher, and why it is narrow
| matcher |
population |
"missing" |
| any backticked token on any line mentioning COMPLETE |
232 |
153 (66%) |
a markdown table row naming a token with a /, under a top-level directory that exists |
12 |
8 |
The loose one was catching bare extensions (.bit, .rs), signal names (BSCAN.JTAG_CHAIN_1), URLs and markdown links. 66% is past the line this repository calls a matcher describing its input rather than the tree. The narrow one has zero false positives and all eight hits are the one file.
docs/reports/**, docs/session-* and docs/coordination/** are excluded with the reason stated: a path that existed then and not now is not a defect in a dated log.
Four more, from the same fan-out, measured but not fixed here
| document |
claim |
today |
docs/fpga/PIN_COVERAGE.md:134-135 |
bootstrap/src/main.rs xdc_qmtech_minimal() / xdc_qmtech_full() are the Rust pin definitions |
0 definitions in the tree, 0 mentions outside docs |
docs/CORPUS-RATCHET.md:99 |
specs/scratch/ excluded — 606,113,688 of 612,924,235 bytes (98.89%) |
specs/scratch/ holds 0 files; the corpus is 650 files / 7,030,194 bytes |
docs/metrics/NUMERIC_FORMATS_83_METRICS.md:6 |
data source gen/numeric/formats_catalog.json (77 formats) |
file does not exist |
docs/SYNTH_REPORT.md:4 |
measured with yosys 0.65 |
bench runs Yosys 0.68+post; last touched 2026-08-06 |
Measured
docs/META_DASHBOARD.mdcarries a "CLARA Deliverables Progress" table — twice — whose Location column names four paths. None is on disk:They were produced —
git log --diff-filter=Anamesc1582008b— and removed on 2026-04-19 by91653d2b9, "fix(bootstrap): restore working main.rs — recovery from detached HEAD (#523)", a 1214-file recovery commit that took them out as collateral. The table has read ✅ COMPLETE for four and a half months.Proposed
Correct the rows rather than delete them —
DELIVERED, then removed in 91653d2b9— so the work is still recorded and the files stay recoverable from91653d2b9^. A dashboard that quietly drops a deliverable is worse than one that says where it went.Plus a check: every path a status table marks COMPLETE must exist.
The matcher, and why it is narrow
/, under a top-level directory that existsThe loose one was catching bare extensions (
.bit,.rs), signal names (BSCAN.JTAG_CHAIN_1), URLs and markdown links. 66% is past the line this repository calls a matcher describing its input rather than the tree. The narrow one has zero false positives and all eight hits are the one file.docs/reports/**,docs/session-*anddocs/coordination/**are excluded with the reason stated: a path that existed then and not now is not a defect in a dated log.Four more, from the same fan-out, measured but not fixed here
docs/fpga/PIN_COVERAGE.md:134-135bootstrap/src/main.rs xdc_qmtech_minimal()/xdc_qmtech_full()are the Rust pin definitionsdocs/CORPUS-RATCHET.md:99specs/scratch/excluded — 606,113,688 of 612,924,235 bytes (98.89%)specs/scratch/holds 0 files; the corpus is 650 files / 7,030,194 bytesdocs/metrics/NUMERIC_FORMATS_83_METRICS.md:6gen/numeric/formats_catalog.json(77 formats)docs/SYNTH_REPORT.md:4