Development record
The build loop arms auto-merge whenever the ruleset gates through a queue; the facilitator-mode intent says that by default abcd never arms or queues a pull request
The build loop arms auto-merge whenever the ruleset gates through a queue; the facilitator-mode intent says that by default abcd never arms or queues a pull request
A premise contradiction (severity major) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2609201916151817-one-verb-takes-a-single-intent-from.md:62— "A pull request with auto-merge armed where the ruleset gates it through a queue, a pull request left open where it does not." - End B:
.abcd/development/intents/planned/itd-2610150602547271-a-repository-declares-whether-its.md:21— "person, a ready pull request waits for them: abcd never queues it or arms"
itd-2609201916151817 decision 3 makes the merge target depend only on the repository's ruleset: auto-merge is armed whenever a queue gates the branch. itd-2610150602547271 makes human the default mode for a fresh install and says that in this mode abcd never queues a pull request or arms auto-merge on it. Its merge gate is the function the build loop must ask. Built as written, the loop would arm auto-merge in exactly the repositories where the mode intent forbids it.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1169.
Deferral 2026-10-27
Deferred past v0.15.1: Deferred by the product thinker on 2026-10-27 (dcn-2610271112330536): the brief's single-home rewrite (dcn-2610271112339516, dcn-2610271112330235) rewrites or removes most of the passages this record quotes.
Frontmatter
| id | iss-2610262043535279 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2610262043535279-the-build-loop-arms-auto-merge-whenever.md
open on GitHub ↗ · commit history ↗
References2
- itd-2609201916151817One verb takes a READY intent to delivered, and refuses while a decision is openrelated
- itd-2610150602547271The facilitator's mode gates the mergerelated
mentions3
- dcn-26102711123302352026-10-27 — The product thinker ruled on 2026-10-27 that the design brief shows the target design, in the present tense, with a status tag where a part is built, rather than the shipped state. With the ruling that behaviour lives in the command pages, the brief holds the product as aimed for and why, and the command pages hold what abcd does today. This reverses itd-147's currency rule, so a superseding ADR is owed, and the brief's checks are rebuilt around the status overlay.
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- dcn-26102711123395162026-10-27 — The product thinker ruled on 2026-10-27 that each abcd command's behaviour is written once, in its command page, which agents follow when they run it. The brief's chapter for the command keeps why the command exists, its trade-offs and why it refuses what it does, with its sub-verb table and generated appendix, and points to the command page for behaviour. The documentation-fidelity check moves to the command pages. This reverses the behaviour half of adr-2609231028044006 and invariant 18, so a superseding ADR is owed.