A 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.

Frontmatter

.abcd/work/issues/resolved/iss-2609200830076665-a-held-draft-has-no-frontmatter-state-so.md
open on GitHub ↗ · commit history ↗

mentions6

• iss-2609170726457256No verb stamps impact or builds_on on an existing intent draft. --impact exists only on the filing call (abcd intent "<text>" --impact) and again at the close that ships the intent (spec close --impact); between those two points a draft that was filed without a judgement has no verb that adds one, and builds_on, a schema-known frontmatter field the readers walk, has no flag on any verb at all. Relayed from the Gropius managed-repo session gropiusllm-56 on 2026-09-17, where two sessions hand-edited the frontmatter of five drafts with sed to set both fields, which bypasses every validator the verbs carry (ParseImpact, the never-internal rule for intents, the record-id shape of a builds_on target). Confirmed against the v0.9.0 command tree: intent plan takes only --production-mode, intent link writes spec_id only, and no verb names builds_on. Sibling records: iss-126 (resolved) gave impact a home at the close, and iss-2609091256264547 (open) covers the three typed relations the schema lacks; this finding is about the one relation it has and the one judgement it accepts, neither of which a verb can write onto a draft. Intent-shaped by the itd-84 four-piece table (a capability: a draft's judged fields are settable through a verb after filing), so the routing to an intent draft is the human's to confirm; recorded here first.
• iss-2609210748122003A hand-spelled held key with a space before the colon is honoured by every reader and reported by no lint rule. The frontmatter scanner's key regex accepts a space before the colon and the intent loader, intent plan and the record dispatcher all read such a line as a legal hold, but the record_provenance rule sees the key only after the scanner has normalised it, so a line no verb writes (the verb writes held: with no space) passes lint silently; intent unhold refuses it (the remover matches the exact spelling) and sends the caller to repair the line by hand, which is the right refusal but the only signal. Found while applying the review ruling on iss-2609200830076665's fix round. Wanted: record_provenance reports the spelling as a shape no write path produces, the way it reports the disclosure pair, or the scanner exposes the raw key spelling so the rule can see it.
• 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
• itd-57Every abcd Voyage Ships With A Manual-Hold Sentinel That Blocks A Spec From Autonomous Pickup Until A Human Lifts It
• itd-2609201916151817One verb takes a READY intent to delivered, and refuses while a decision is open
• spc-2609202134338445one-verb-takes-a-single-intent-from-ready-to-delivered-witho