add(considered): /.well-known/cyclic-trigger is a control-plane RPC, not a website property

[jdevalk]

What changed

One new entry in src/content/considered/ — /.well-known/cyclic-trigger, registered with IANA as a provisional well-known URI suffix on 17 August 2026 (change controller: SmartStandards Community). No spec page, no changelog entry, no derived surfaces affected.

Why now

It is the only registry movement in this run's window. The suffix reserves /.well-known/cyclic-trigger/go: a POST with an empty JSON body that lets external infrastructure periodically wake a service which would otherwise keep a background worker or timer alive. Sensible enough for a cost-sensitive serverless estate — and not a website property.

Why it was turned down

Two independent reasons, either of which is sufficient:

1. Scope. Nothing a visitor, crawler or agent does is affected by whether the endpoint exists, and the only caller is the operator's own orchestrator. It is an RPC entry point with a fixed name, not a discovery document a third party fetches to learn something about the site. Reserving a suffix reserves a path; it does not make what lives there a website concern.
2. It contradicts a page we already publish. The specification requires that errors return 200 OK with a fault property in the body, deliberately, so orchestrators need no transport-level error handling. That is the soft-404 antipattern — which this spec marks avoid — generalised from one status code to all of them, and it cuts against error pages.

Adoption does not argue the other way: the registered reference is a two-commit GitHub repository created 23 June 2026 and untouched since — 0 stars, 0 forks, 0 watchers, 0 issues, no named implementers, and no security or authentication section for an endpoint whose purpose is to make a service do work on an unauthenticated POST.

revisit is deliberately strict: adoption alone would not move this. It would need to become something public sites publish for callers they do not control and to start signalling failure in the status line.

Reference case

This entry carries a narrower rule than the usual adoption one, which the register did not yet state: a /.well-known/ name is not automatically a website property. Some registrations are private machinery wearing a public prefix. It sits alongside #178 (scitt-keys) and #157 (webhook-authorized-senders) rather than duplicating them — those turn on infrastructure scope and on IANA permanence not being adoption.

Sources

• Well-Known URIs registry — IANA
• Cyclic Trigger specification — SmartStandards Community
• RFC 8615 — Well-Known URIs — IETF

Checks

npm run build, npm run lint, npm run format:check all pass; check:skill clean (page count unchanged at 168).

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying specification-website with    Cloudflare Pages

Latest commit:	fc66114
Status:	✅  Deploy successful!
Preview URL:	https://1410254f.specification-website.pages.dev
Branch Preview URL:	https://add-considered-cyclic-trigge.specification-website.pages.dev

View logs