abcd 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.

Frontmatter

.abcd/work/issues/open/iss-2610150726331622-abcd-peers-does-two-unrelated-things-it.md
open on GitHub ↗ · commit history ↗

References1

• 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 reservationrelated

mentions5

• dcn-26101610403949702026-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).
• itd-2609150819440345Which session holds which worktree, branch or record is coordinated entirely by conversation, so every new session repeats a handshake that nothing records. A session joining work in progress has no way to ask what is already claimed: it messages the peers it can see, waits for replies, and rebuilds a picture that the sessions before it had already built and did not write down. One measured encounter cost four messages and about fifteen minutes before any work began, and the picture it produced is not durable, so the session after that pays again. The convention that a diff you did not make is a peer's work depends on knowing who the peers are and what they hold, which is precisely the thing no artefact carries. The repository already records this gap for the narrow case of detecting a peer session before mutating git state; the wider case is claim rather than presence, and the two want the same substrate. Whatever holds it should be as cheap to write as it is to read, because a coordination record nobody updates is worse than the chat it replaced.
• itd-2610161016401115Drains run unattended and visibly
• spc-2610150728396006sessions-announce-what-they-are-doing
• spc-2610161044461448drain-many-accounts