Development record
Adopt Decided/Implemented as the fixed value set for the wiring-status field on brief surface rows. The convention serves the spec-moves-with-the-surface practice: a surface row that names a verb must state mechanically whether the verb is merely decided or actually implemented, because it was the absence of exactly this state that produced the empty-shipped/ incident, where a surface documented as shipped had nothing behind it. Detector: the spec-moves-with-the-surface cross-check reads the wiring-status field mechanically, so any row missing the field or carrying a value outside the two-token vocabulary fails the check; acceptance is the cross-check parsing every surface row without a free-text fallback.
Adopt Decided/Implemented as the fixed value set for the wiring-status field on brief surface rows. The convention serves the spec-moves-with-the-surface practice: a surface row that names a verb must state mechanically whether the verb is merely decided or actually implemented, because it was the absence of exactly this state that produced the empty-shipped/ incident, where a surface documented as shipped had nothing behind it. Detector: the spec-moves-with-the-surface cross-check reads the wiring-status field mechanically, so any row missing the field or carrying a value outside the two-token vocabulary fails the check; acceptance is the cross-check parsing every surface row without a free-text fallback.
Grounds
- declined: the shipped-state brief and the generated surface block make a wiring-status field redundant; this would be wrong if a brief row could again describe a verb the tree does not carry
Frontmatter
| id | iss-50 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-50-wiring-status-vocabulary.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26101810034672332026-10-18 — A pull request carries a reservation's work only through its head branch or a closing trailer (facilitator-on-delegation, itd-2610180912189125 review round 2, blocker 4; refines dcn-2610180936568358): the link is the record id in the pull request's head branch name, or on a `Resolves:` or `Delivers:` line of its body, matched on word boundaries so that iss-5 never matches iss-50. A `Refs:` line, which the issue-resolution gate requires of any pull request that only names an issue, carries the work only when the head branch is already this copy's own by another route, and never makes a branch own, so a sibling copy's pull request that mentions the record neither leaves this session waiting nor becomes its branch (grounds: plan review round 2, blocker 4; the RS004 rule in scripts/check-issue-resolution.sh)
- spc-2610180914469489A session left to work on never stops while it has work