Development record
itd-94 says autonomous drain runs are held by the intent readiness gate; the intent chapter says the drain verb's lanes are issues
itd-94 says autonomous drain runs are held by the intent readiness gate; the intent chapter says the drain verb's lanes are issues
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/shipped/itd-94-an-intent-that-is-not-planned-cannot-be.md:25— "Autonomous drain runs get the same gate for free: exit 1 is a journaled SKIP, never a guess." - End B:
.abcd/development/brief/04-surfaces/05-intent.md:278— "a run of the top-level drain verb never does, since its lanes are issues and an issue has no criteria."
itd-94 says autonomous drain runs get the implement-readiness gate for free, so exit 1 becomes a journaled SKIP. The intent chapter says the lanes of the top-level drain verb are issues, which have no acceptance criteria. An intent readiness gate has no intent to judge in a run whose lanes are issues, so the two documents disagree about what drain runs work on.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 555.
Frontmatter
| id | iss-2610262035127167 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262035127167-itd-94-says-autonomous-drain-runs-are.md
open on GitHub ↗ · commit history ↗
References1
- itd-94An intent that is not planned cannot be implemented: abcd gains a machine-checkable implement-readiness gate that refuses with a remedy and offers the planning interviewrelated
mentions2
- iss-2610262038051992itd-94 says autonomous drain runs inherit the implement-readiness gate, exit 1 a journaled SKIP; 35-drain's lanes are issue runs checked only by the drain rule and the peers check
- iss-2610262045139907itd-94 has autonomous drain runs implementing intents; itd-82 defines drain as working issues only and leaves picking intents to `abcd build next`