Development record
2026-10-30 — Withdrawals a person made under their login on a release that has ended, before their home keeps a holder id, are re-armed only once their first reservation or announcement keeps an id (iss-2610290809526033); until then the peers listing says each time that held merges from before the holder id stay held until that act, without naming the login. The cost accepted is that those merges stay held longer for a person who has not acted since the update. Three alternatives were rejected: minting the holder id on a read path such as the peers listing, since a read never writes the person's identity file; pushing a tombstone that names the login, since nothing pushed carries the login; and re-arming without the tombstone that claims the end, since that tombstone is the compare-and-swap that keeps two copies of the person from settling against different tips. The act that keeps the id writes each of those withdrawals under it, in the tombstone that settles them and in every later push of the person's that carries them, so no push names the login; a home whose id is set or kept but refused is not told the id is awaited, since every act refuses until it is fixed. Ruled by the facilitator on delegation from the product thinker.
2026-10-30 — Withdrawals a person made under their login on a release that has ended, before their home keeps a holder id, are re-armed only once their first reservation or announcement keeps an id (iss-2610290809526033); until then the peers listing says each time that held merges from before the holder id stay held until that act, without naming the login. The cost accepted is that those merges stay held longer for a person who has not acted since the update. Three alternatives were rejected: minting the holder id on a read path such as the peers listing, since a read never writes the person's identity file; pushing a tombstone that names the login, since nothing pushed carries the login; and re-arming without the tombstone that claims the end, since that tombstone is the compare-and-swap that keeps two copies of the person from settling against different tips. The act that keeps the id writes each of those withdrawals under it, in the tombstone that settles them and in every later push of the person's that carries them, so no push names the login; a home whose id is set or kept but refused is not told the id is awaited, since every act refuses until it is fixed. Ruled by the facilitator on delegation from the product thinker.
Frontmatter
| id | dcn-2610300525431448 |
|---|---|
| type | decision |
| date | 2026-10-30 |
.abcd/work/decisions/dcn-2610300525431448-withdrawals-a-person-made-under-their.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610290809526033Reservation and announcement commits that abcd pushes to origin name the holder by their forge login: the Abcd-Holder and Abcd-Sender trailers carry it, and the announcement branch is named after it, so every reservation publishes which account made it in text and in the branch list.