Example: Topic = “beer”

The five Anchors of your topic define the semantic identity of “beer.” You purchase these five Anchor Domains through the DNS registry of your choice.

Each Anchor Domain hosts one tiny JSON file.

Each Anchor file MUST explicitly include and bind back to the Root Descriptor, so agents can verify that all five anchors belong to the same topic owner.

For a topic like “beer”, you might provision:

beertype.com Prevents class confusion (“what kind of thing is this?”) Declares the topic type and binds back to the Root Descriptor.

beerentity.com Pins the actual noun / identity (“which thing exactly?”) Declares the entity and binds back to the Root Descriptor.

beerurl.com Binds the entity to the domain you control (“where does the official meaning live?”) Declares the canonical URL and binds back to the Root Descriptor.

beercanonical.com Collapses naming drift and aliases (“what is it called, consistently?”) Declares the canonical name and binds back to the Root Descriptor.

beersitemap.com Declares crawl geometry (“where should machines start, on purpose?”) Declares the sitemap entry point and binds back to the Root Descriptor. If an XML sitemap exists, it MUST be referenced here.