Development record
abcd 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).
issueresolvedminoriss-2610111759340919
abcd 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).
Grounds
- pursued: we expect the interview's verdict to agree with abcd intent ready and the build's check on every record it leaves; a record the interview calls READY that intent ready or the build refuses for open_questions would show it wrong.
Frontmatter
| id | iss-2610111759340919 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610111759340919-abcd-intent-interview-ends-with-a-ready.md
open on GitHub ↗ · commit history ↗
mentions1
- 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.