Development record
itd-199's three scope-condition identity markers are wrapped in backticks in its shipped record, so the claim reader treats each as documentation of the marker grammar rather than an identity: ParseClaims reports zero conditions, the verdict dispositions keyed to cond-2608312031029678, cond-2608312031028702 and cond-2608312031020321 key to nothing the record carries, and abcd intent condition refuses to re-disposition cond-2608312031028702, the worked example its own spec names
issueresolvedminoriss-2609250947113245
itd-199's three scope-condition identity markers are wrapped in backticks in its shipped record, so the claim reader treats each as documentation of the marker grammar rather than an identity: ParseClaims reports zero conditions, the verdict dispositions keyed to cond-2608312031029678, cond-2608312031028702 and cond-2608312031020321 key to nothing the record carries, and abcd intent condition refuses to re-disposition cond-2608312031028702, the worked example its own spec names
Grounds
- pursued: we expect itd-199 to carry three readable condition identities; a read of intent condition itd-199 reporting fewer than three would show it wrong
Frontmatter
| id | iss-2609250947113245 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609250947113245-itd-199-s-three-scope-condition-identity.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-199A reading is about something narrower than everything, and its scope is a committed, adjustable choice