2026-10-16 — A drain lane's stage shows in abcd peers (facilitator-on-delegation, drain-many-accounts): a drain lane's stage is published as a closed-vocabulary trailer on its reservation's renewal commits, and abcd peers lists it beside the reservation with each holder's hand-back tombstones of the last day; the people's status view inherits the same rows when it takes the reservation listing over (itd-2609151838312703, iss-2610150726331622); and the holder a process resolves through the forge is cached for that process (grounds: the reservation is the record every account already fetches, so the stage costs no new act; iss-2610161015434746, iss-2610161015433495).

Frontmatter

.abcd/work/decisions/dcn-2610161040394970-a-drain-lane-s-stage-shows-in-abcd-peers.md
open on GitHub ↗ · commit history ↗

mentions11

• dcn-26101707572515472026-10-17 — abcd peers shows at most ten hand-backs per holder (facilitator-on-delegation, drain-many-accounts, step 18): the newest ten of the last day, newest first, with a count of the rest, never dropped silently (grounds: ten keeps one holder's block to a screenful while a session reading it before a pick still sees the latest of a busy day; refines dcn-2610161040394970).
• dcn-26101707572536442026-10-17 — A bad Abcd-Stage makes the reservation tip unreadable, as a bad hand-back does (facilitator-on-delegation, drain-many-accounts, step 18): two stages, a value outside the five lane stages, or a stage on a tombstone read as unreadable with one fixed reason, never as a stage, while an inexact spelling of the key reads as the key's, as for every reservation trailer (grounds: one consistent fail-closed rule across the family's closed-vocabulary trailers; only a renewal writes a stage, so a stage anywhere else is hand-made; refines dcn-2610161040394970).
• dcn-26101707572563742026-10-17 — A hand-back's last day is judged by the tombstone's Abcd-Released-At (facilitator-on-delegation, drain-many-accounts, step 18): abcd peers lists a hand-back released within 24 hours of the reader's clock, and never one dated more than lease.Skew ahead of it, which is left out rather than counted from when it was fetched (grounds: the release stamps Abcd-Released-At on every tombstone it writes, so it is the time the hand-back was made; a date ahead is not trusted, and leaving it out means a fast clock cannot keep it on show past its day, while the drain's own reading of the hand-back is unchanged; refines dcn-2610161040394970).
• dcn-26101707572677912026-10-17 — The lane stage and the hand-backs ride the reservation listing that abcd peers and abcd status share (facilitator-on-delegation, drain-many-accounts, step 18): the stage is a stage field on each reservation row and the hand-backs a hand_backs_by_holder list, each holder with its hand_backs and a more count, so status shows them too (grounds: the listing block is one shape for both surfaces by design, and dcn-2610161040394970 has the people's status view inherit the same rows; a list per holder keeps the order a map would lose).
• dcn-26101707591808942026-10-17 — Every lane renewal names its stage (facilitator-on-delegation, drain-many-accounts, spc-2610161044461448 step 18, the loop's half; refines dcn-2610161040394970): each renewal the loop pushes for a run's reservation, a drain move's, a lane step's, the land fence's and a resumed build's alike, sets claim's Request.Stage to the stage the run's current lane is in, spelled as the loop's Stage values worktree, brief, implement, validate and land, which are claim's LaneStages; a lane done, handed back, held or discarded names no stage, since it performs none; a loop test holds every Stage the loop renews with to claim.ValidLaneStage, since claim cannot import the loop (grounds: a run's state does not mark a drain's lane, and a build lane's stage is as useful to a peer and costs no act; the stage a worker reports is the one it is in, as job dashboards read it from the record each worker writes; iss-2610161015434746)
• iss-2610150726331622abcd peers does two unrelated things: it lists records that sibling worktrees and local branches hold that this checkout does not (an agent's duplicate check before filing), and it fetches and lists the reservations on the shared remote. The second duplicates abcd status from itd-2609151838312703, the people's view of what everyone else is doing. The product thinker ruled on 2026-10-15 that peers keeps its name for its future meaning, which sessions are running now, local first and later over a private network such as Tailscale or WireGuard (the session register itd-2609150819440345), and that the local duplicate check belongs under abcd status --local.
• iss-2610161015433495With a git email that is not a GitHub noreply address, every reservation act calls gh api user again, uncached.
• iss-2610161015434746abcd peers shows each account's reservations but nothing of a drain lane's stage, its judgements or its hand-backs, so one person cannot see what another account's drain is doing.
• itd-2609151838312703Sessions under any account, on any machine or in the cloud announce what they are doing through short fixed-form announcements on the shared remote, a person reads everyone's status with one command, and what is really a hold stays a reservation
• itd-2610161016401115Drains run unattended and visibly
• spc-2610161044461448drain-many-accounts