Development record
abcd 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.
issueresolvedminoriss-2610101610446956
abcd 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.
Grounds
- pursued: we expect abcd intent ready and abcd build to agree on open questions, so no record the verb calls READY is refused by the build at check (open_questions); a READY verdict followed by a build refusal at open_questions would show it wrong.
Frontmatter
| id | iss-2610101610446956 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610101610446956-abcd-intent-ready-reported-itd-82-ready.md
open on GitHub ↗ · commit history ↗
mentions4
- iss-2610111759340919abcd intent interview ends with a READY verdict computed by plain intent.Ready, so it can report 'the record is READY' for a planned record whose ## Open Questions still lists an unanswered item, which abcd intent ready now reports NOT READY (open_questions) and abcd build refuses at check (open_questions). Found by the ruthless review of run-2610111657111142 lane-1 (iss-2610101610446956).
- iss-2610111759346608The abcd itd-N dispatcher computes a planned intent's next move from plain intent.Ready, so for a planned intent whose ## Open Questions still lists an unanswered item it says 'ready — implement against the spec body', while abcd intent ready reports NOT READY (open_questions) and abcd build refuses at check (open_questions). Found by the ruthless review of run-2610111657111142 lane-1 (iss-2610101610446956).
- iss-2610311501473953abcd 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.
- itd-82`abcd drain` fixes the issues that need no decision, and hands the rest back by kind