From 7b7ac203aaa4db7cd8f2a06c8e59f3aac30c682b Mon Sep 17 00:00:00 2001
From: "@permadeath.com" <did:plc:nlzmjyfv6loqtxyzvdcznwgf>
Date: Sat, 5 Sep 2026 15:38:42 -0400
Subject: [PATCH] docs(dns-providers): say what a resync removes, and which
 zone shape a page draws

`ProviderView` still described `Route53Dns::resync` as hydrate-only; it drops
a name the zone no longer holds and takes the zone's value for a repointed
one. `docs/names.md` draws the wildcard zone, so it now says so and points at
the per-hostname shape beside it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Change-Id: I2a570c4cd7c1f1ca8aabd270ea4a63c18e2479e9
---
 docs/names.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/names.md b/docs/names.md
index e0dcf522..080663a4 100644
--- a/docs/names.md
+++ b/docs/names.md
@@ -49,6 +49,12 @@ propagation to wait for and no external call on the provisioning path.
 per-name bookkeeping every other backend keeps, refuses a host outside its
 zone, and publishes nothing, because there is nothing left to publish.
 
+This page draws the wildcard zone. `Route53Dns` takes the other shape and
+writes a record set per hostname — two per named account — which is the
+number `plan/capacity.md` budgets a hosted zone against, and the propagation
+provisioning then waits on. [Deployment](deployment.md) is where a zone picks
+between the two.
+
 ## Everything the server answers
 
 <div><svg viewBox="0 0 1000 570" role="img" aria-label="A zone pds.example holds three records: an apex A record, a wildcard A record, and an acme-challenge TXT record. Two agent hostnames are synthesized by the wildcard rather than written into the zone. Both land on one listener holding one certificate covering the apex and the wildcard, which dispatches on the Host header: the opaque hostname serves a DID document, the handle hostname serves a plain-text DID, and both point at the same account.">
-- 
2.51.2