Public contract

Discovery Surface

The machine-facing entry points that agents should use before they touch the rendered shell.

llms.txt, sitemap.md, markdown twins, and clean article slugs define the public discovery plane.

Authors: Joel Hooks (https://joelhooks.com) — author

Publisher: gremlin-cms

Updated: 2026-03-08T00:00:00.000Z

The discovery plane stays intentionally small and explicit.

Start at llms.txt, expand to sitemap.md, then follow markdown twins for public pages and articles. TanStack should surface the same machine-readable map as Next, not a framework-specific variant.

Public pages and articles should describe the same reality as the API and markdown twins. If they drift, the contract suite should catch it.

discoveryllmsmarkdown
Read the markdown twinFetch the public content documentRun a public search

Related resources

  • Platform — Gremlin CMS exposes the shared public discovery contract from the TanStack Start reference site.
  • Public API — The canonical machine-friendly JSON routes exposed by the public operator contract.
  • Agent-First Content Is SEO Now — If an agent cannot discover, fetch, quote, and trust your content without scraping chrome, your SEO is already behind.
  • The Public Contract Is the Interface — If an agent has to scrape your chrome to find the thing your system already knows, your interface is doing extra work for no reason.