Development record
no gate requires a terminal folder record to carry a grounds entry so fourteen resolved records have none
issueopenminoriss-2608301747006182
no gate requires a terminal folder record to carry a grounds entry so fourteen resolved records have none
Reported by the round-5 builder. PRE-EXISTING in substance -- the old rule
checked the grammar of a grounds value only if one was present -- but far
more visible now that grounds is a section rather than an optional key.
A gate demanding one would be red today: the fourteen records that reached
resolved/ before grounds existed carry none, and nothing backfills them. So
the gate cannot simply be armed; it needs a cutover rule saying from when the
obligation runs.
Remedy grounds (2026-09-29)
- The deferral measured 690 of 1663 resolved and 17 of 46 wontfix records without grounds, and one post-cutover exception, so option (a) is green after one backfill; ordinal ids such as iss-59 carry no timestamp and predate the cutover, so they pass by construction.
- No outside-practice check: the question is a cutover date for an internal rule.
- Rejected: arming the rule without a cutover, which would refuse hundreds of settled records.
Frontmatter
| id | iss-2608301747006182 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2608301747006182-no-gate-requires-a-terminal-folder.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-59Two-layer verification lesson from the iss-36 sweep: 73 mechanical fixers + per-file grep-verify reported 100% clean, yet a 4-segment judgement review found ~30 real truth defects (invented homes for unmigrated material, false present-tense capability claims). For the run seam (itd-29/Phase 5) and any future corpus sweep: grep-verify proves pattern absence, never truth; a sweep is done only after a judgement review layer passes. Also: fix agents given precise per-finding instructions applied 100% cleanly — precision of the fix list, not agent capability, was the quality lever.
- iss-2608310912203724a record authored straight into resolved never invokes capture resolve so the grounds obligation reaches only records that pass through the verb
- itd-179The reasoning behind what was pursued no longer evaporates at the gate — readiness and triage record grounds for the conjecture, not only the decision