Development record
The readings companion's section 4.3 says what a disposition's grounds must contain varies by state (a rejection names the purpose protected, an admission or a decline states why) and that the variation is a lint rule rather than four fields. Nothing enforces it: the disposition command refuses only a blank or whitespace-only grounds field, and no lint reads the grounds against the state. Held by protocol today; the readiness statement for Phase A records it as not held by mechanism.
issuewontfixminoriss-2609021816039081
The readings companion's section 4.3 says what a disposition's grounds must contain varies by state (a rejection names the purpose protected, an admission or a decline states why) and that the variation is a lint rule rather than four fields. Nothing enforces it: the disposition command refuses only a blank or whitespace-only grounds field, and no lint reads the grounds against the state. Held by protocol today; the readiness statement for Phase A records it as not held by mechanism.
Grounds
- declined: a state-keyed grounds lint would be a new refusal inside the parked gates; this would be wrong if the rethink of the reading work re-arms grounds refusals
Frontmatter
| id | iss-2609021816039081 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2609021816039081-the-readings-companion-s-section-4-3.md
open on GitHub ↗ · commit history ↗