Development record
The voyage entry has the voyage record every disembark and embark run; the configuration chapter says only disembark runs are logged and the embark side is staged.
The voyage entry has the voyage record every disembark and embark run; the configuration chapter says only disembark runs are logged and the embark side is staged.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/voyage.md:4— "an append-only record of what abcd did to produce a lifeboat (every disembark and embark run)" - End B:
.abcd/development/brief/05-internals/03-configuration.md:500— "every disembark run; nothing else is written anywhere under the store, and an"
The voyage glossary entry defines the voyage as an append-only record of every disembark and embark run, and lays out embark/provenance.json and embark/from/<timestamp>/. 03-configuration says what ships is an append-only manifest log of every disembark run, that nothing else is written under the store, and that an embark-side record is staged. Embark runs are either recorded there or not.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 793.
Frontmatter
| id | iss-2610262038256056 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262038256056-the-voyage-entry-has-the-voyage-record.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610262040315792The voyage glossary says the voyage records every disembark and embark run; the verification matrix says the voyage ledger has a disembark half only.