Conversation
…ot the site's Records the decision not to spec Automattic's hosting-provider well-known URI. It is served by the origin, but written by the hosting platform, about the platform, and its own specification calls the value spoofable — so there is no instruction to give a site author and no outcome to audit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
caafa5c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://a4cf97ae.specification-website.pages.dev |
| Branch Preview URL: | https://considered-hosting-provider.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
One new entry in
src/content/considered/—hosting-provider-well-known.md— recording the decision not to spec/.well-known/hosting-provider. No spec page, no derived surface, no SKILL.md impact (page count and categories are unchanged).Why now
Surfaced by this run's sweep of the IANA Well-Known URIs registry. It is not a new registration — Automattic registered it provisionally in July 2020 and the specification, a single README, has not changed since April 2019 — but it is a registered, website-served well-known URI we neither cover nor have ever recorded a decision on, so the register was incomplete.
The call:
out-of-scopeA participating host serves a bare
text/plainstring naming itself, so that a third party combining it with hostname and IP checks can tell who is actually serving a site whose DNS points at a CDN.Two things keep it off the spec:
That leaves no instruction to give a reader and no outcome to audit.
The entry is written as the counterpart to the existing
scitt-keysentry: that one failed on who serves the file, this one is genuinely served by the origin and fails on who benefits. Together they state the test that admitssecurity.txtandchange-password— serving the file has to make this origin better for the people and programs that visit it.Sources
hosting-provider, provisional, registered 2020-07-21)Verification
npm run lint,npm run format:checkandnpm run buildall pass; the pre-commit hook's agent-skill drift check confirms 170 pages / 10 categories / MCP 2026-07-28, unchanged.🤖 Generated with Claude Code