Which site a deployment serves when a request names none: one deployment is one site, so an
unmapped host resolves to the primary recorded in the deployment document (objects record
themselves; a pre-existing site records as claimed, never primary).
The primary is, in order: the one an owner chose with PUT /deployment; the only claimed site;
with several, the one holding the most content (nodes plus accounts beyond uid 1), ties to the
oldest claim. A choice is recorded at once, so later content cannot move a hostname. Nothing is
merged or deleted: a non-primary site stays reachable through site:host:<host> or /export.
Which site a deployment serves when a request names none: one deployment is one site, so an unmapped host resolves to the primary recorded in the deployment document (objects record themselves; a pre-existing site records as claimed, never primary).
The primary is, in order: the one an owner chose with
PUT /deployment; the only claimed site; with several, the one holding the most content (nodes plus accounts beyond uid 1), ties to the oldest claim. A choice is recorded at once, so later content cannot move a hostname. Nothing is merged or deleted: a non-primary site stays reachable throughsite:host:<host>or/export.