Development record
itd-25 writes dredge synthesis reports under .abcd/logbook/dredge/, the retired logbook location
issueopenminoriss-2610262031301413
itd-25 writes dredge synthesis reports under .abcd/logbook/dredge/, the retired logbook location
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-25-dredge-cross-corpus-synthesist.md:35— "writessynthesis-report.{json,md}to.abcd/logbook/dredge/<timestamp>/" - End B:
.abcd/development/brief/02-constraints/04-naming.md:83— ".abcd/logbook/was the maritime name for per-run logs, state and reports. It is retired and must not be re-minted"
itd-25's dredge synth writes synthesis-report.{json,md} to .abcd/logbook/dredge/< timestamp>/, and dredge list reads them back from there. The naming chapter says .abcd/logbook/ is retired and must not be re-minted. The draft's storage location cannot be built as written.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 139.
Frontmatter
| id | iss-2610262031301413 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031301413-itd-25-writes-dredge-synthesis-reports.md
open on GitHub ↗ · commit history ↗
References1
- itd-25Patterns Surface Themselvesrelated
mentions2
- iss-2610262038565943itd-25 writes dredge reports under .abcd/logbook/dredge/; 04-universal-patterns puts dredge output in the local tier's logs
- iss-2610262040369028itd-25 writes dredge reports to .abcd/logbook/dredge/; the memory chapter puts them in .abcd/.work.local/logs/dredge/.