Development record
2026-09-02 — The per-position configuration the 2026-09-01 ruling asked for ("one shared pile by default, and a per-position include table as configuration when a run needs a position handed only its own object", recorded against iss-2608311501240566) is delivered by the per-position preset entry of the object-set ruling of this day, which carries each position's object set, kinds and window, applied with no operand. One configuration surface, not two: a per-position include-table section beside the preset entry would be a second answer to one question, and the change carrying it is reconciled to the preset entry or waits for the maintainer.
2026-09-02 — The per-position configuration the 2026-09-01 ruling asked for ("one shared pile by default, and a per-position include table as configuration when a run needs a position handed only its own object", recorded against iss-2608311501240566) is delivered by the per-position preset entry of the object-set ruling of this day, which carries each position's object set, kinds and window, applied with no operand. One configuration surface, not two: a per-position include-table section beside the preset entry would be a second answer to one question, and the change carrying it is reconciled to the preset entry or waits for the maintainer.
Frontmatter
| id | dcn-2609020000000018 |
|---|---|
| type | decision |
| date | 2026-09-02 |
.abcd/work/decisions/dcn-2609020000000018-the-per-position-configuration-the.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608311501240566Three of the four reading positions receive a byte-identical item set. Comparing the manifests of a real assembly at one commit, widening, comparative and detection each carry the same 951 items with the same fields, and only entailment differs, by the 346 draft and planned items the drafts asymmetry admits. That asymmetry is itd-183's and it works exactly as designed. The other three do not. The definitions state four distinct objects: widening reads the brief, glossary, disciplines, specs and shipped tree; comparative reads the candidate set, which is the widening reading's pre-admission output, against the declared selection criteria; detection reads the shipped tree against the claim record. What the assembler actually passes at comparative and at detection is the widening object unchanged. The comparative case is the sharper one, because its object is not a subset of the repository at all but the output of a previous reading, and the assembler has no channel for it -- spc-64 says as much in passing, that the in-cycle candidate set arrives by whatever channel spc-61 defines and the eval makes no claim about it, but nothing states that the position therefore receives the wrong object. No criterion measures cross-position differentiation, and the evals run on a fixture too small for the difference to show.