Development record
itd-50 says a NOT_MET verdict is logged and "the voyage moves on", using voyage for project progress; the glossary reserves voyage for the operations namespace
itd-50 says a NOT_MET verdict is logged and "the voyage moves on", using voyage for project progress; the glossary reserves voyage for the operations namespace
A terminology drift (severity nitpick) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-50-loop-toward-acceptance.md:25— "records aNOT_METverdict and the voyage moves on" - End B:
.abcd/development/brief/glossary/core/voyage.md:59— "Do not use it for a "project" (too generic)"
itd-50's press release uses voyage for the project's onward progress after an audit. The glossary defines voyage only as the operator-level record of disembark and embark runs, and says not to use it for a project. adr-35 retired that lifecycle sense.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1007.
Frontmatter
| id | iss-2610262041325659 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2610262041325659-itd-50-says-a-not-met-verdict-is-logged.md
open on GitHub ↗ · commit history ↗
References1
- itd-50The Audit Loop Drives An Intent To Acceptance — Or Calls For A Replanrelated
mentions1
- adr-35The lifeboat is a coverage experiment — read-only, out-of-tree, and proven before it is packed (supersedes adr-4)