Development record
The layered configuration reader silently ignores a misspelt namespace at a file's top level, such as facilitater for facilitator, or one padded with whitespace: only a claimed namespace's own spelling, its case twins and its dotted form are refused, because nothing claims a file's top level. So a person who writes {"facilitater":{"mode":"human"}} in the machine file is outvoted by a repository's auto with no word, and the same holds for every claimant's namespace. Found by the review pair of the merge gate's step 1 on 2026-10-27.
issueopenminoriss-2610272213410875
The layered configuration reader silently ignores a misspelt namespace at a file's top level, such as facilitater for facilitator, or one padded with whitespace: only a claimed namespace's own spelling, its case twins and its dotted form are refused, because nothing claims a file's top level. So a person who writes {"facilitater":{"mode":"human"}} in the machine file is outvoted by a repository's auto with no word, and the same holds for every claimant's namespace. Found by the review pair of the merge gate's step 1 on 2026-10-27.
Frontmatter
| id | iss-2610272213410875 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610272213410875-the-layered-configuration-reader.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26102722135332722026-10-27 — Merge-gate step 1 (itd-2610150602547271) ships refusing a claimed namespace's case twins and its dotted form, but not a misspelt or padded namespace at a file's top level, captured as iss-2610272213410875. Grounds: both review-pair members found no way past the human-wins rule other than a top-level misspelling; that gap applies to every claimant of the layered reader alike, not to this step, and closing it needs a design choice between a top-level key registry and a near-miss check, which is its own change. Decided by the agent under the autonomous-run delegation of 2026-10-27.