Home assignment on first publish
PyPI calls the shipped HA first-home claim during its local upload path. Mode dc has no authority assignment; its
configured writer owns writes.
An authority owns a set of related writes and has one home datacenter. The first successful publication assigns that home and mints its first epoch. Later writes must pass the current epoch fence.
Authority transfer moves an assigned home. The availability contracts define the durability required during assignment and transfer.
Authority identity
The content owner derives a canonical authority key from its client-visible identity. Name variants that identify the same subject must produce one key. Owners use disjoint keyspaces. Availability treats the key as opaque and never parses owner naming rules.
Home selection
The ingress datacenter for the first successful publication becomes the home. It is already a live member of the committed cluster because it accepted the request. Assignment needs no separate placement pass.
Concurrent assignment
The control quorum applies a compare-and-set command to an unassigned authority. The first committed command records the home and epoch. A later command for the same authority returns the committed assignment without replacing it.
The winning command records its cause, leader term, log index, and minted epoch. Ownership snapshots retain that audit record. Rejected commands do not replace it.
Retries and partitions
A datacenter in a control-plane minority cannot commit an assignment. It forwards the claim to the leader and does not assign a local home. A restart or partition repair reads the quorum result and uses the committed winner.
A failed best-effort claim does not publish conflicting authority state. A later publication can repeat the claim after quorum access returns.