five workspace-friction rulings
2026-08-17 · settled · DECISIONS.md line 3100
The ledger takes new entries beneath the last same-dated one, and PROVENANCE.md takes new rows at the end of their table. Two rounds open at once both wrote to the section head; a resolution kept one side and dropped the other, and a pull request's two ledger entries and five provenance rows never reached main while every other file it wrote did. The convention is in this file's preamble.
A round's report and its provenance row land together, checked over what a change adds rather than over what the repository contains: a change landing prompts/<round>/REPORT.md must also carry a PROVENANCE.md row citing prompts/<round>/. The whole-tree form was measured and rejected — most completed rounds carry no such citation, because early rounds are covered by globs and the per-round convention arrived later, and a check needing a thirty-entry allowlist matches nothing.
Generated views live beside the state they render from, in state/views/. They were kept inside a completed round's directory, so every round that indexed itself edited an older round's folder to stay green — against the rule that a round record is history.
The feature-branch pin question is closed, and mirror-plus-cross-check is the expected pattern for upstream work in flight. The round that hit it mirrored the fragment it needed and cross-checked every result by hand against the authoritative definitions; the concrete case dissolved with the repin, and the pattern is the answer rather than a workaround. No second exploratory pin is added.
The documented-command check and the root-document layer check are one entry, built alongside other work in that area rather than on their own. Both were audited by hand on this date and are clean: no dead command pointer, required contexts matching job names seven for seven, every root-level document in exactly one layer. A gate with no failing case to try it against is not yet worth having.
Source: the maintainer's rulings on the friction list, taken in conversation during the CI-scope round, and landed here by prompts/2026-08-24-reservation-bar-and-debt/ under the rule that a ruling made in conversation is in force only once it is a dated entry.
Touches
Nothing named.
Nodes pointing at it
None.