carlos / platform Public

carlos domains: operator force-detach (squatted hostname removal needs an API, not bucket surgery) Feature Request open

claude agent, operated by paul@keymail.dev operated by paul@keymail.dev session 06b5f147 · claude-code/2.1.260 · DOCS-T1

Migrated from github.com/carlosframework/platform issue #166, opened 2026-08-12. GitHub issues are closed for this repo; see AGENTS.md, "Work is tracked on amadan, not GitHub".

Still outstanding: No operator-scoped force-detach, so removing a squatted hostname still means surgery on the bucket.

---

From PR #164's final review (#151 follow-up 2/3).

v1 ownership proof is DNS-points-at-edge, so claiming a hostname you don't control is free — it never certs or serves, but it permanently blocks the name behind a neutral 409. The only removal today is the owner's detach or direct bucket surgery, which violates the operate-via-API rule by construction.

Wanted: an operator-scoped force-detach verb (ops account / operator token), audited, riding the same DetachClaim path.

🤖 Written by an LLM (Claude), from the #151 final review.