Decide what happens to a verified custom domain when the plan that allowed it ends #331

Open
opened 2026-11-14 23:17:14 +00:00 by cgalo5758 · 0 comments
Owner

The question

A plan can carry the right to claim a custom domain (the on/off entitlement external_domain_claims). A member on such a plan verifies wiki.example.org and places it on a site. Then the plan ends, and nothing the organization still holds carries that right.

Today nothing changes for the domain:

  • The entitlement is read in one place only, when a new claim starts (internal/server/external_claim_gate.go).
  • The certificate check answers from the site's own state (internal/domains/authorizer.go), and a site counts as servable while it is active or read-only. So the console keeps approving certificates for the domain and the farm keeps serving the site on it.
  • The workspace can create further sites under the verified claim, because a name inside an active claim is added at once with no entitlement check (internal/integrations/fedwiki/web/site_actions.go). The code states this as its rule: the entitlement buys the right to claim a new domain, not the right to use one already claimed.

Should a custom domain stop serving when the right to claim one ends, and if so, when, and how does it come back?

What depends on the answer

  • Whether a member who pays once for a plan with custom domains keeps them for nothing. A custom domain is often the reason a member chooses the higher plan, and each one costs certificates and routing for as long as its DNS points at the farm.
  • What a member sees on the domains page and on the site when the right ends.
  • What the integration contract says about an on/off entitlement the console itself owns. Today such an entitlement can only say that existing things are left alone.
  • The fix for #330, which settles the same thing for the sites themselves.

Options known so far

  1. Leave it as built and say so: a claim, once verified, stays the member's for as long as they keep the DNS records.
  2. The domain stops serving when the right ends, at once or after a stated period, and serves again when a plan carries the right again. The claim and its verification are kept.
  3. The existing domain keeps serving, and only new sites under the claim need the right.

Decided when

The rule is written in openspec/specs/domains-registry/spec.md, which today covers only the start of a claim, and in the page that describes the domains model, and the certificate check and the site-creation path follow it.

### The question A plan can carry the right to claim a custom domain (the on/off entitlement `external_domain_claims`). A member on such a plan verifies `wiki.example.org` and places it on a site. Then the plan ends, and nothing the organization still holds carries that right. Today nothing changes for the domain: - The entitlement is read in one place only, when a new claim starts (`internal/server/external_claim_gate.go`). - The certificate check answers from the site's own state (`internal/domains/authorizer.go`), and a site counts as servable while it is active or read-only. So the console keeps approving certificates for the domain and the farm keeps serving the site on it. - The workspace can create further sites under the verified claim, because a name inside an active claim is added at once with no entitlement check (`internal/integrations/fedwiki/web/site_actions.go`). The code states this as its rule: the entitlement buys the right to claim a new domain, not the right to use one already claimed. Should a custom domain stop serving when the right to claim one ends, and if so, when, and how does it come back? ### What depends on the answer - Whether a member who pays once for a plan with custom domains keeps them for nothing. A custom domain is often the reason a member chooses the higher plan, and each one costs certificates and routing for as long as its DNS points at the farm. - What a member sees on the domains page and on the site when the right ends. - What the integration contract says about an on/off entitlement the console itself owns. Today such an entitlement can only say that existing things are left alone. - The fix for #330, which settles the same thing for the sites themselves. ### Options known so far 1. Leave it as built and say so: a claim, once verified, stays the member's for as long as they keep the DNS records. 2. The domain stops serving when the right ends, at once or after a stated period, and serves again when a plan carries the right again. The claim and its verification are kept. 3. The existing domain keeps serving, and only new sites under the claim need the right. ### Decided when The rule is written in `openspec/specs/domains-registry/spec.md`, which today covers only the start of a claim, and in the page that describes the domains model, and the certificate check and the site-creation path follow it.
cgalo5758 added the
kind
design
area/entitlementsarea/domainsarea/fedwiki
labels 2026-11-14 23:17:14 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#331