2026-11-01 — Records-only changes keep the full review pair, a ruthless and a security review, before they merge under autonomous merging, as code changes do. The pair runs on the person's API key once a verb runs the review pair on the runner. The product thinker ruled this on 2026-11-01.

Frontmatter

.abcd/work/decisions/dcn-2611012113436014-records-only-changes-keep-the-full.md
open on GitHub ↗ · commit history ↗

mentions2

• dcn-26110422055562212026-11-04 — A delta review satisfies the full-pair rule of dcn-2611012113436014 for records and docs alone: after a change has passed a full ruthless and security pair, a small follow-up to the record or the docs may rest on that pair with a delta pair that reads only the follow-up and whether the earlier findings closed. Anything that touches code always takes a full pair. The product thinker ruled this on 2026-11-04.
• dcn-26110519080786962026-11-05 — The build loop records a review receipt only from a pair that read the pushed head, its records commit included. Where the mode is auto, a lane's full round is told each resolution it declares and judges it, and the records commit then takes a review round of its own, scoped to that commit, before anything is pushed, unless the commit moves an issue's record that round was not told of or holds more than plain markdown, when the lane parks before any round. A round that does not pass parks the lane at its pull request for a person, with no fix round, and a parked lane is not synced. By the coordinator's reading, this meets the reason behind clause 6 of dcn-2610291524030570 and the full-pair ruling in dcn-2611012113436014; the person is told and can overrule. It supersedes that clause's statement that the loop writes no receipt.