# Website and agent discovery

**Publication design, not a ranking promise.** The website is a static build of versioned Markdown. Preview builds are intentionally noindex; public mode must be explicitly selected after review.

## Three surfaces

**Answer-engine discovery:** crawlable HTML, precise headings, original sources, stable canonical URLs, a sitemap, and structured data matching visible content. Google says ordinary search fundamentals remain relevant to AI features; no special AI schema is required. [1]

**Developer discovery:** searchable documentation, a versioned litepaper, engineering journal, source references, and tested examples when the runtime exists.

**Machine use:** OpenAPI and schemas, supported network/asset descriptions, error behavior, timeouts, payment terms, and deterministic verification instructions. A directory listing is not runtime permission.

The site supplies llms.txt, llms-full.txt, Markdown mirrors, a JSON search index, RSS, and an explicitly design-only OpenAPI file. It does not publish a fictitious live MCP server or A2A Agent Card. Its custom capability document states that the API and SDK are not released.

## Publication controls

Preview mode disables indexing. Public mode must be an intentional build setting after the owner approves publication and the domain is configured. robots.txt is not access control: keep unpublished files behind authentication or out of the deployment entirely. Private operational notes are excluded from the build.

OAI-SearchBot and GPTBot have separate controls. Search access and training access are site-owner choices. Machine documents are reader conveniences, not guaranteed ranking factors. [2]

## Metrics

Measure source-attributed discovery, successful examples, authorized first invocation, paid repeat use, and independent verification. Do not report self-funded testing as external demand. Do not inject instructions into third-party agents to force adoption.

## Sources

1. [Google AI search features](https://developers.google.com/search/docs/appearance/ai-features)
2. [OpenAI crawlers](https://developers.openai.com/api/docs/bots)

<!-- p21-source-payment-v08 -->

## Commercial activation and implementation status

NAT and USDC are both required for the initial commercial-launch acceptance test. Public documentation, source code and policy fixtures are not live payment endpoints. The static payment-policy resource lists required launch methods with `enabled: false`, no recipient and no live endpoint until each rail passes end-to-end settlement, accounting, failure/reorganization, security and owner-approval gates. Do not advertise a USDC-only release as the completed initial payment scope.

No token has been issued, no source element is announced, and no mainnet inscription, customer charge, treasury swap or wallet authorization is performed by this release. Production service availability remains separate from website publication. No Trac partnership, hosted SLA or independent cryptographic audit is implied.


[1] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/digital-elements/.element-registry

[2] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/src/index/updater/inscription_updater/tap/ops/dmt_element.rs

[3] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/nat-use-cases/usdnat-method-1-live

[4] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/non-arbitrary-tokens-nats/nat-token-transfer

[5] https://docs.x402.org/core-concepts/network-and-token-support

[6] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/README.md

[7] https://arxiv.org/abs/1605.04559

<!-- p21-enforcement-v10 -->

## Machine-readable enforcement resources

The static site publishes `.well-known/enforcement-profile.json` plus draft JSON Schemas for action authorization, consumer decisions and equivocation evidence. Agent catalogs link these resources in every language. They describe protocol shapes only: `runtimeAvailable` remains false and there is no live signer, wallet controller or dispute endpoint.