How a Brazilian Rock Band Implemented llms.txt (And Why It Makes Sense)

Most llms.txt implementations you'll find are SaaS products, developer
tools, or documentation sites. This one is different.

HADEMANASTIA is a Brazilian rock band — or more precisely, a "sonic
inoculation protocol." Their site is an enigmatic system interface,
not a typical band page. And they've implemented llms.txt properly.

What they did

• llms.txt at the root: https://hademanastia.com/llms.txt
• llms-full.txt with full context: https://hademanastia.com/llms-full.txt
• JSON-LD subjectOf reference in the WebSite schema pointing to the llms-full.txt file
• .htaccess rules explicitly allowing both files
• Both files referenced in sitemap.xml and robots.txt
• Wikidata entry updated with described at URL pointing to both files

The JSON-LD part is interesting

Most implementations stop at just placing the file. This one goes further
by declaring it in structured data:

"subjectOf": {
  "@type": "DigitalDocument",
  "url": "https://hademanastia.com/llms-full.txt",
  "name": "HADEMANASTIA LLMs Full Context"
}

This means crawlers that parse schema.org markup will find the LLM
context file as a declared property of the WebSite entity — not just
a file that happens to exist.

Why non-tech sites should care

llms.txt isn't only for documentation. Any entity that wants to control
how AI systems describe them benefits from it:

• Musicians and artists
• Independent creators
• Small businesses
• Personal brands

If you don't define your context, AI will infer it from whatever it finds.
llms.txt lets you set the signal.

The broader point

The llms.txt standard is still early. Most adopters are developer-facing
products. But the use case extends to anyone who wants accurate AI
representation.

A band implementing it — especially one with an intentionally cryptic
online presence — is a signal that the standard is moving beyond its
original niche.

Worth watching.

llms.txt spec: https://llmstxt.org