Development record
2026-10-30 — itd-2610150602547271: now that the merge gate reads facilitator.mode, the board's merges line says what the gate does, read through the gate's own resolver (the default branch's committed config and the machine layer) so the board and the gate never disagree: human reads as merging once the technical facilitator approves the head, auto as merging autonomously once a review pair has passed the head, each with the layer that set it, and the facilitator view keeps the key and the mode. A contributor's pull request needing approval in either mode is said in the docs, not on the line.
2026-10-30 — itd-2610150602547271: now that the merge gate reads facilitator.mode, the board's merges line says what the gate does, read through the gate's own resolver (the default branch's committed config and the machine layer) so the board and the gate never disagree: human reads as merging once the technical facilitator approves the head, auto as merging autonomously once a review pair has passed the head, each with the layer that set it, and the facilitator view keeps the key and the mode. A contributor's pull request needing approval in either mode is said in the docs, not on the line.
Frontmatter
| id | dcn-2610300439004187 |
|---|---|
| type | decision |
| date | 2026-10-30 |
.abcd/work/decisions/dcn-2610300439004187-itd-2610150602547271-now-that-the-merge.md
open on GitHub ↗ · commit history ↗
mentions1
- itd-2610150602547271The facilitator's mode gates the merge