Development record
itd-57 proposes a sentinel spec that keeps planned work out of autonomous pickup; the board chapter says the build's start checks already skip a held record.
itd-57 proposes a sentinel spec that keeps planned work out of autonomous pickup; the board chapter says the build's start checks already skip a held record.
A scope leakage (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/drafts/itd-57-manual-hold-sentinel.md:17— "that any future spec can depend on to stay invisible to autonomous pickup until a human explicitly unblocks it" - End B:
.abcd/development/brief/04-surfaces/08-abcd.md:344— "the claim sections answered, no hold, no unsettled blocker, a step left to"
itd-57 promises a way to park planned work: a sentinel spec dependency that keeps a spec out of autonomous pickup until a person lifts it. 08-abcd.md says the build's pre-start checks, which both the pick and the board's head run, require no hold, so a held record is already skipped. Two mechanisms claim the same person-lifted block on autonomous pickup.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 492.
Frontmatter
| id | iss-2610262034233163 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262034233163-itd-57-proposes-a-sentinel-spec-that.md
open on GitHub ↗ · commit history ↗
References1
- itd-57Every abcd Voyage Ships With A Manual-Hold Sentinel That Blocks A Spec From Autonomous Pickup Until A Human Lifts Itrelated
mentions2
- iss-2610262037255566itd-57 says nothing holds a planned item back from autonomous pickup today; the build brief's hold check already refuses any record carrying held:
- iss-2610262044060780Keeping a record from autonomous pickup is a sentinel-spec dependency in itd-57 and a held state the build loop checks in itd-2609201916151817