Skip to content

0042: Member rename record and client-side name uniqueness

  • Status: accepted (member-roles-and-rename archived 2026-10-30)
  • Date: 2026-10-25
  • Amended by: 0046 (the current name is the last rename link in chain order; the unknown-kind rule is replaced by enabling record kinds)
  • Builds on: 0006, 0008

Context

A member's display name is set once, as an encrypted enc_name in the genesis or add-member policy record, and vaultfold init always names the creator admin. On 2026-10-25 Ben wanted his member, created as admin, to be called Ben, and no policy record could change it (agentboard ticket 01M5S8FE3ZQRNGAEVW326MEBSP). Display names are sealed under the root collection KEK, so the policy fold, and the hosted service that runs it, cannot read or compare them. The OpenSpec change member-roles-and-rename has the details.

Decision

  • A new policy record kind, RenameMember (15), with the body {1: member, 2: enc_name}. The name is sealed exactly as the add-member name is, under the newest root collection KEK the author holds.
  • Authority: the member itself (any of its active devices), unless it is a machine identity, or a root admin. A machine identity never renames itself, even when it is a root admin: only a root admin device of another member may rename it. The recovery member cannot be renamed, and the target must be unrevoked. A root admin's rename of another member is subject to the causal-past rule for role reductions (ADR 0043). A rename is not a rights reduction and carries no event_heads.
  • The current name is the enc_name of the last valid rename in fold order, falling back to the add-member or genesis name. Fold order is deterministic, so concurrent renames converge.
  • Uniqueness among unrevoked members, and the reserved name recovery, are enforced by the authoring client, never by the fold. Duplicates that arise from concurrent writes are marked in member list, reported by doctor, and resolved by member id prefix.
  • Neither the record Version nor the vault format_version changes. Instead, clients from this change on warn about policy records of a kind they do not implement, rather than skipping them silently. A file counts as an unknown kind only if it is a well-formed version 1 envelope (this vault's id, 32-byte parent ids and author, a non-empty signature, a path that is its content id). The warning, and doctor's unknown-policy-kind error, name the author the record claims: the signature of a record of an unknown kind is not verified.
  • The authoring client seals under the newest root KEK it holds. When a newer root epoch exists whose wrap has not reached the device, the rename is still written and a warning names vaultfold sync: the name is a label, and refusing would block renaming offline. (Since ADR 0046 a rename is a privilege write that pulls first, so refusing would instead stop the rename until the newer epoch's wrap has reached the device.) A device revoked at the newer epoch can read such a name (threat model).
  • member grant, member ungrant and member rename address members by display name or by a member id prefix of at least 8 hex characters. A name shared by several members, or equal to a prefix of another member's id, is ambiguous and never silently resolved; revoked members are refused as revoked. init names the first member (--member-name, or a prompt defaulting to git config user.name on a terminal, otherwise admin).
  • member rename is refused in an agent session, like the other commands that change roles.
  • No policy record bounds enc_name yet. A cap must land before the first release (ticket 01M5VREMP4).

Consequences

  • Members can fix their own names without an admin, and the creator can pick a name at init.
  • A member can choose a misleading name. The renamer is shown in member list and in the policy history, and fingerprint verification remains the identity check. The threat model says that display names are labels.
  • A vaultfold built before this record kind ignores a rename and holds every later policy record as an orphan. This is acceptable only because nothing has been released. Teammates must upgrade before the first rename by any member (not only admins), and the hosted service must be redeployed first.
  • The hosted service learns that a member was renamed, and when, but not the name.

Alternatives considered

  • Reuse AddMember with the existing member id. Rejected: it would turn the duplicate-member refusal into a special case and confuse "added by" attribution.
  • A general member-metadata record with optional fields. Deferred: only the name exists today. Email and other metadata can get their own kind when they are specified.
  • Admins only. Rejected: a member naming itself is the common case, and an admin can rename again.
  • Uniqueness enforced by the fold. Impossible without exposing names, because the fold must run without any KEK (ADR 0006).
  • Bump format_version or the record version. Rejected: vault.json is write-once, so it cannot announce a kind added later. A version bump would make every existing record or vault unreadable to gain nothing.
  • Refuse to open a vault with an unknown kind. Rejected: anyone who can write to the storage could then deny service with one file.