Development record
Capture defines 'promoted' as the two-ended join between an issue and an intent; drain hands back as `promoted` any issue whose related_intents names an intent.
Capture defines 'promoted' as the two-ended join between an issue and an intent; drain hands back as promoted any issue whose related_intents names an intent.
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/06-capture.md:189— "the pair is what "promoted" means: an issue may name an intent it is only related to, and it is promoted into the one that names it back" - End B:
.abcd/development/brief/04-surfaces/35-drain.md:93— "An issue whoserelated_intentsnames an intent is handed back underpromoted, naming each intent: an intent already owns it"
06-capture says 'promoted' means the pair: the issue's related_intents and the intent's related_issues naming each other. An issue may name an intent it is only related to without being promoted. 35-drain hands back under promoted every issue whose related_intents names an intent, even when only the issue names it. That includes the audit-check issues the verdict ingest files as merely related to an intent, and 35-drain says an intent already owns them. The same word means a two-way join on one page and a one-way relation on the other.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 409.
Frontmatter
| id | iss-2610262033286211 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033286211-capture-defines-promoted-as-the.md
open on GitHub ↗ · commit history ↗