Development record
`peers` means records held by sibling worktrees in the shipped reader, but the planned announcements ruling reserves it for sessions running now
peers means records held by sibling worktrees in the shipped reader, but the planned announcements ruling reserves it for sessions running now
A naming conflict (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/planned/itd-2609151838312703-sessions-announce-what-they-are-doing.md:120— "the product thinker ruled thatpeerskeeps its name for its future meaning, the sessions running now, local first and later over a private network" - End B:
.abcd/development/intents/shipped/itd-2609091416295622-a-session-sees-the-records-its-sibling.md:55— "Presence or liveness: A peer holding a record says the record exists, not that a session does."
itd-2609091416295622 defines peers as a read of records that sibling worktrees and branches hold, and puts presence out of scope: a peer holding a record does not mean a session exists. itd-2609151838312703 rules that peers keeps its name for the sessions running now. One verb name is given two different concepts.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1211.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. Today peers lists records held by sibling worktrees and branches, as the shipped intent says; the planned meaning is explicitly future and captured as its own record.
Frontmatter
| id | iss-2610262044300840 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262044300840-peers-means-records-held-by-sibling.md
open on GitHub ↗ · commit history ↗
References2
- itd-2609091416295622A session sees the records its peers hold before it mints or fixes onerelated
- 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
mentions1
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.