backlog(#340): the armed-auto-merge signal is unfalsifiable from outside - #144
Merged
Merged
Conversation
Follow-on to #143, which merged before this measurement existed. Adds the one argument #340 was missing, and it is a better one than the cycle-count case. Measured 2026-08-02T13:41Z, re-derived here rather than relayed: open=14 armed=9 armed_and_inert=6 armed_and_CLEAN=0 #142 BEHIND #139 BEHIND #128 BEHIND #101 BEHIND #96 BEHIND #71 DIRTY Two-thirds of the armed PRs in this repo cannot land, and NOT ONE armed PR was CLEAN. #71 is armed and DIRTY, so it can never land at all. Why this belongs in the item: everything else in #340 is an efficiency argument, and an efficiency argument has a "then be patient" answer. This one does not. Every session here reads autoMergeRequest != null as "this will land" -- I said exactly that about my own PR an hour before measuring this -- when for six of nine it means "this waits until a human runs gh pr update-branch", with nothing reporting the difference. That is the ADR 0158 defect class (a green signal that means nothing) caught live rather than in retrospect. ADR 0158 is referenced by number, not linked: it is not on main yet. The measurement came out of the sandbox-codec session's queue claim, checked by the announce-hook session, and the connection to 0158's class is sandbox-codec's. Both routed it to me rather than writing it, since #340 is claimed here. Re-derived independently before writing; their figures and mine agree exactly.
wshallwshall
enabled auto-merge (squash)
August 2, 2026 13:43
This was referenced Aug 2, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-on to #143, which merged at 13:36:39Z — before this measurement existed. Adds the one argument #340 was missing, and it is stronger than the cycle-count case already in the item.
Measured 2026-08-02T13:41Z, re-derived here rather than relayed:
Two-thirds of the armed PRs in this repo cannot land, and not one armed PR was
CLEAN. #71 is armed andDIRTY, so it can never land at all.Why it belongs in #340. Everything else in the item is an efficiency argument, and an efficiency argument can always be answered with "then be patient." This one cannot. Every session here reads
autoMergeRequest != nullas "this will land" — I said exactly that about my own PR an hour before taking this measurement — when for six of nine it means "this waits until a human runsgh pr update-branch", with nothing reporting the difference.So the shape of the item stops being "merges are slow" and becomes "the merge-readiness signal cannot be distinguished from its own absence without a second query nobody runs." That is the ADR 0158 defect class — a green signal that means nothing — caught live rather than in retrospect.
ADR 0158 is referenced by number, not linked: it is not on
mainyet.Two lines, one paragraph, inside item #340 only. #344 untouched (another session owns it). Banner invariant holds (264 items, one status each); ledger gate passes; CRLF preserved (0 bare LF).
Attribution: the measurement came out of the sandbox-codec session's queue claim, checked independently by the announce-hook session; the connection to ADR 0158's class is sandbox-codec's. Both routed it here rather than writing it, since #340 is claimed by this session. I re-derived it independently before writing — their figures and mine agree exactly.