Seats keep their former names — a rename is one DB op (ADR 0122, phase 2) #83

2026-09-27T14:34:40Z

jschoubben commented

2026-09-27 14:34:40 +00:00

Phase 2 of ADR 0122: the stable identity that makes a rename break nothing.

A seat's canonical name can change; its old name becomes an alias that resolves to it forever. SeatNamed, HolderAmong, and the seats display all resolve a name (former or current) to its seat — so a manifest's claim, a held record, the git-seat lookup, and even the build machine's embedded set go on working unchanged after a rename. No manifest edits, no rebuild, no re-registration, no freeze.

migration 0035 — seat_alias table
inventory.Aliases / inventory.RenameSeat (repoints chained aliases; refuses no-such-seat and same-name)
openInventory loads aliases; alias-aware SeatNamed/HolderAmong/seatsHeld
mesh-controller seat rename <from> <to> — the whole of a rename, one command

Behaviour-neutral until a seat is renamed (no aliases → lookups identical). Validated against postgres. This is what makes the outstanding renames (registry seats, the-private-network) trivial DB operations.

Phase 2 of ADR 0122: the stable identity that makes a rename break nothing. A seat's canonical name can change; its old name becomes an **alias** that resolves to it forever. `SeatNamed`, `HolderAmong`, and the `seats` display all resolve a name (former or current) to its seat — so a manifest's claim, a held record, the git-seat lookup, and even the build machine's embedded set go on working **unchanged** after a rename. No manifest edits, no rebuild, no re-registration, no freeze. - migration `0035` — `seat_alias` table - `inventory.Aliases` / `inventory.RenameSeat` (repoints chained aliases; refuses no-such-seat and same-name) - `openInventory` loads aliases; alias-aware `SeatNamed`/`HolderAmong`/`seatsHeld` - **`mesh-controller seat rename <from> <to>`** — the whole of a rename, one command Behaviour-neutral until a seat is renamed (no aliases → lookups identical). Validated against postgres. This is what makes the outstanding renames (registry seats, `the-private-network`) trivial DB operations.

jschoubben added 1 commit 2026-09-27 14:34:40 +00:00

Seats keep their former names, so a rename breaks nothing (ADR 0122, phase 2) 6da9a5478b

Phase 1 made the set data; a rename still broke every reference to the old
name. This adds the stable identity: a seat's canonical name changes and its
old name becomes an alias that resolves to it forever. SeatNamed and the holder
and display matching resolve a name (former or current) to its seat, so a
manifest's claim, a held record, the git-seat lookup and the build machine's
embedded set all go on working unchanged after a rename. seat_alias table
(migration 0035), inventory Aliases/RenameSeat, openInventory loads them, and a
'seat rename <from> <to>' command does the whole thing — one operation, no
rebuild, no re-registration, no freeze. Behaviour-neutral until a seat is
renamed. Validated against postgres.

jschoubben merged commit 75dab209d7 into main

2026-09-27 14:34:45 +00:00

jschoubben deleted branch feat/seats-rename-is-a-db-op

2026-09-27 14:34:45 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#83