Development record
2026-10-16 — A drain reserves an issue before it judges it (facilitator-on-delegation, drain-many-accounts): the drain reserves an issue before it asks any judgement over it, so the reservation push is the compare-and-swap that keeps two accounts from judging or promoting one issue; an issue or footprint another copy holds in the move's view is passed over with no push and no judgement; and within each group of one category and severity the drain takes file-scoped issues first and orders each part by a rendezvous hash of the holder, the copy key and the issue id, so accounts and copies spread across the group with no coordinator (grounds: competing consumers with skip-locked selection, and rendezvous hashing; iss-2610161015387318).
2026-10-16 — A drain reserves an issue before it judges it (facilitator-on-delegation, drain-many-accounts): the drain reserves an issue before it asks any judgement over it, so the reservation push is the compare-and-swap that keeps two accounts from judging or promoting one issue; an issue or footprint another copy holds in the move's view is passed over with no push and no judgement; and within each group of one category and severity the drain takes file-scoped issues first and orders each part by a rendezvous hash of the holder, the copy key and the issue id, so accounts and copies spread across the group with no coordinator (grounds: competing consumers with skip-locked selection, and rendezvous hashing; iss-2610161015387318).
Frontmatter
| id | dcn-2610161040368890 |
|---|---|
| type | decision |
| date | 2026-10-16 |
.abcd/work/decisions/dcn-2610161040368890-a-drain-reserves-an-issue-before-it.md
open on GitHub ↗ · commit history ↗
mentions4
- dcn-26101614122840182026-10-16 — Every issue lane's hand-back is published, and a drain judges a standing one from its view before it pushes (facilitator-on-delegation, drain-many-accounts): a lane of a run abcd build <iss-N> started publishes its kind as a drain's lane does, since the step's release already serves both and a hand-back names a person's decision whoever started the run; a drain move passes over a standing hand-back in its view, whichever copy made it, before any push or judgement, and the reservation it pushes still backs off one the view missed, which is the compare-and-swap; and a checkout holds a record as origin does when git's object name for its open file, as git hash-object stores it, equals origin's blob at the commit the move planned from, a promotion a killed call already made being found first (grounds: the view-then-compare-and-swap order of dcn-2610161040368890, and content-addressed equality as git defines it; spc-2610161044461448 step 3; iss-2610161015370582).
- iss-2610161015387318The host judgement is asked before the issue's reservation is checked, and an issue another account holds is retried on every move with a full check (plan, sibling worktree scan, fetch), so several drains all judge and retry the same head of the queue, since every drain takes the same order (category, severity, oldest).
- itd-2610161016394967Drains on several accounts share the work
- spc-2610161044461448drain-many-accounts