Development record
The ac-3 operator-surface guard walks the generated baseline caches under the abcd directory, whose map keys are arbitrary data: the citations baseline is machine-written from cited URLs, so a legitimate citation whose URL contains the substring 'regime' turns the guard red with findings that name no real defect. On a branch whose subject is supply regimes that is not a hypothetical, and the failure sends the reader hunting a regime knob that does not exist. A generated cache is not an operator surface and does not belong in the enumeration.
issueresolvedmajoriss-2608311100440709
The ac-3 operator-surface guard walks the generated baseline caches under the abcd directory, whose map keys are arbitrary data: the citations baseline is machine-written from cited URLs, so a legitimate citation whose URL contains the substring 'regime' turns the guard red with findings that name no real defect. On a branch whose subject is supply regimes that is not a hypothetical, and the failure sends the reader hunting a regime knob that does not exist. A generated cache is not an operator surface and does not belong in the enumeration.
Grounds
- pursued: a generated cache is not an operator surface, so excluding it removes a false red rather than a real channel; what would show this wrong is something coming to read a baseline as configuration, at which point the single stated exclusion is where that changes
Frontmatter
| id | iss-2608311100440709 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2608311100440709-the-ac-3-operator-surface-guard-walks.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-184Four cold-reading definitions, one blindness core — each position licenses a different output, and none may hold another's licence