Development record
Invariant 6 says the voyage record is never committed, but universal patterns says voyage is tracked under the visibility rule
Invariant 6 says the voyage record is never committed, but universal patterns says voyage is tracked under the visibility rule
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/02-constraints/03-invariants.md:19— "keyed on the root-commit SHA like the history store — never committed, and never accumulated as stale snapshots" - End B:
.abcd/development/brief/05-internals/04-universal-patterns.md:161— "Both are tracked under the visibility rule; they answer different questions"
Invariant 6 says operations history lives at the operator level, ~/.abcd.noindex/voyage/<source-root-sha>/, and is never committed. Universal patterns compares the log tier with voyage/ and says both are tracked under the visibility rule. Under that rule the .abcd/ namespace is committed in a private repository. The voyage store cannot be both outside every commit and tracked under the switch that decides what a repository commits.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 101.
Frontmatter
| id | iss-2610262031138510 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262031138510-invariant-6-says-the-voyage-record-is.md
open on GitHub ↗ · commit history ↗