← board

Canonical domain in the docs

Why

The domain is the trust anchor. Against impersonation it beats every technical measure: people check the address bar, not the source repo. Naming it canonically — in the docs, the README, the installers, the release notes — is what makes a fake look wrong to a user who has seen the real one. Cheap, high leverage, do it early so it propagates everywhere by default.

Scope

Do NOW (independent of the site being live) — user action

Register the variants of pxxc. This is the one item that gets harder with time: once the project is visible, squatters watch for exactly this gap.

Do WHEN LIVE

  1. Wire pxxc.org as canonical across docs/**: install/download links, landing copy, README.
  2. Installer/bootstrap scripts point at the canonical URL (dovetails with [[feature-release-checksums-repro]] — fetch canonical, verify checksum, then run).
  3. HTTPS + HSTS; a <link rel="canonical"> in the published pages. (Track W.)
  4. Publish the release-signing key fingerprint on the site (second publication point — trust is key continuity + publication).

Blocked on

The site being live. The name is known (pxxc.org); it is deliberately NOT yet written into docs/** because it does not resolve. Unblock = the site serves real content; then this is a same-session job.

Log