abcd intent ready itd-39 reported the intent READY on 2026-10-31, listing scope_conditions as an advisory row ('no ## Scope Conditions section — the context claim is unrecorded'), and abcd build itd-39 then refused it at claim_sections for the same missing section. ReadyWithQuestions (internal/core/intent/ready.go) appends only the open-questions start check to the readiness verdict, so READY still does not mean the build will start, the defect iss-2610101610446956 fixed for open questions alone.

Frontmatter

.abcd/work/issues/open/iss-2610311501473953-abcd-intent-ready-itd-39-reported-the.md
open on GitHub ↗ · commit history ↗

mentions3

• iss-2610101610446956abcd intent ready reported itd-82 READY while abcd build itd-82 refused it at check (open_questions) for two open questions in its record: the readiness verb does not run the check the build makes, so READY does not mean the build will start.
• iss-2610312234315875Whether abcd intent ready gates on the claim_sections start check was ruled on 2026-11-01 (dcn-2611011332291422): it gates. Before that ruling, gating it would have reversed their ruling on iss-2609091009111294, which kept the mechanism and scope-condition rows advisory, so intent ready can report READY on a record that abcd build then refuses at claim_sections, as itd-39 showed on 2026-10-31. Split from iss-2610311501473953 so its drain-buildable half carries no ruling.
• itd-39abcd Surfaces the Right Memory at the Right Moment