Development record
Keeping a record from autonomous pickup is a sentinel-spec dependency in itd-57 and a held state the build loop checks in itd-2609201916151817
Keeping a record from autonomous pickup is a sentinel-spec dependency in itd-57 and a held state the build loop checks in itd-2609201916151817
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— "a permanent sentinel spec, scaffolded at configure time, that any future spec can depend on to stay invisible to autonomous pickup" - End B:
.abcd/development/intents/planned/itd-2609201916151817-one-verb-takes-a-single-intent-from.md:43— "The held state (iss-2609200830076665) is a prerequisite this intent depends on"
itd-57 proposes holding work back from autonomous pickup with a dependency on a permanent sentinel spec, which the selector already skips. itd-2609201916151817 makes 'not held' a readiness check and depends on a separate held state (iss-2609200830076665). The same ground, a person keeping an item out of an unattended run, gets two incompatible mechanisms, and neither record mentions the other.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1183.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262034233163. Same draft act as the hold record; the planned loop intent's prerequisite note about the held state is also satisfied now that the hold ships, so only itd-57 needs the edit.
Frontmatter
| id | iss-2610262044060780 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262044060780-keeping-a-record-from-autonomous-pickup.md
open on GitHub ↗ · commit history ↗
References2
- itd-57Every abcd Voyage Ships With A Manual-Hold Sentinel That Blocks A Spec From Autonomous Pickup Until A Human Lifts Itrelated
- itd-2609201916151817One verb takes a READY intent to delivered, and refuses while a decision is openrelated
mentions3
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2609200830076665A held draft has no frontmatter state, so nothing mechanical stops a lane from planning it. A hold on an intent draft is prose (a Review or Open Questions section saying it is held and why); the intent frontmatter the loader reads carries no hold field, and abcd intent plan checks the draft's sections and the bucket, never a hold. The surface page makes plan a human sign-off act that is never run unattended, which is the convention that holds today, and a sub-agent lane that follows its own brief rather than the page has nothing in its way. Relayed from the Gropius session gropiusllm-2b on 2026-09-20, which ran five record-only lanes on held drafts with a written prohibition on planning as the only guard. Wanted: a held: <reason> frontmatter key on a draft, written by a verb and refused as free text, with plan refusing a held draft and naming the reason, and the record dispatcher (abcd <itd-N>) reporting the hold as the next move. Sibling of iss-2609170726457256 (no verb stamps judged fields on a draft): this is the state field, that one the judgement fields.
- iss-2610262034233163itd-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.