add(considered): /.well-known/scitt-keys is infrastructure, not a website property - #178
Draft
jdevalk wants to merge 1 commit into
Draft
add(considered): /.well-known/scitt-keys is infrastructure, not a website property#178jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…site property IANA registered the scitt-keys suffix on 2026-07-01. It is served by a SCITT transparency service so relying parties can verify receipts — a supply-chain ledger operator, not a website. Recorded as too-narrow. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Deploying specification-website with
|
| Latest commit: |
5a2063b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5f105936.specification-website.pages.dev |
| Branch Preview URL: | https://add-considered-scitt-keys-20.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/, rendered at/considered/. No spec page, no status change.Why now
This run's IANA Well-Known URIs sweep turned up
scitt-keys, registered 2026-07-01 — the newest registration in the window, and new well-known URIs are exactly what this scan watches for.It does not earn a page.
/.well-known/scitt-keysis defined by the SCITT Reference APIs draft and is served by a transparency service so relying parties can fetch the keys that verify its receipts. A site that publishes to such a service is a client of the endpoint, never its host. There is nothing here a website serves alongside itssecurity.txt.The entry uses that to make a point that outlives SCITT:
/.well-known/is a shared namespace, not a checklist for every origin — the registry also holds suffixes for smart inverters and job-posting feeds. A registration says somebody needed a stable path, not that the somebody was a website.Sources
Reason
too-narrow. Note this is a scope turn-down, not a timing one — no amount of adoption among ledger operators would make this a property of a website, sorevisitpoints at the likelier neighbour (content provenance, C2PA-style) rather than at an adoption threshold.Checks
npm run buildpasses. Page count unchanged at 168 (considered entries are not spec pages), so no SKILL.md digest change. Lint and format clean.🤖 Generated with Claude Code