Development record
2026-10-16 — A drain does not ask a lapsed judgement request's issue again in the move it lapsed in, nor before a cool-down of the take-over margin (five minutes) from the move that dropped it, and then only after its other eligible work; that move releases the lapsed hold at once, every push a drain makes for a judgement is its hold except a renewal of this person's own live reservation, and a lapse is forgotten once its issue is asked again or answered. This refines dcn-2610161315385888: with no other work the tombstone and a new reservation landed in one move, so no other account ever had a window (spc-2610161044461448 step 2).
2026-10-16 — A drain does not ask a lapsed judgement request's issue again in the move it lapsed in, nor before a cool-down of the take-over margin (five minutes) from the move that dropped it, and then only after its other eligible work; that move releases the lapsed hold at once, every push a drain makes for a judgement is its hold except a renewal of this person's own live reservation, and a lapse is forgotten once its issue is asked again or answered. This refines dcn-2610161315385888: with no other work the tombstone and a new reservation landed in one move, so no other account ever had a window (spc-2610161044461448 step 2).
Frontmatter
| id | dcn-2610161420314313 |
|---|---|
| type | decision |
| date | 2026-10-16 |
.abcd/work/decisions/dcn-2610161420314313-a-drain-does-not-ask-a-lapsed-judgement.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26101613153858882026-10-16 — A drain takes its judgement hold on an issue once per request and never renews it on a poll; a request whose hold lapses unanswered is dropped, the hold released, and the issue asked again only after the drain's other eligible work, since judgement requests had no expiry of their own and a host that kept polling held the issue indefinitely (spc-2610161044461448 step 2).
- spc-2610161044461448drain-many-accounts