What is implemented
Concise content maps
Root and language-specific llms.txt files route agents to the most relevant public resources instead of duplicating an entire site.
Markdown counterparts
Key English and Chinese pages publish a corresponding Markdown document with the same title, summary and substantive content.
Page-level discovery
HTML pages use alternate and describedby link relations to identify their Markdown counterpart and the applicable llms.txt map.
How it fits the wider web stack
Machine-readable content maps complement semantic HTML, structured data, sitemaps and crawler policy. Each mechanism has a different job: discovery, interpretation, indexing policy or content access.
How Winin verifies it
- AvailabilityEvery declared machine-readable resource must return a successful response with an appropriate content type.
- ParityMaterial claims in the Markdown version are checked against the corresponding canonical page.
- DiscoveryAutomated tests verify alternate, describedby and internal route integrity after every build.
- Outcome measurementChanges in retrieval, citation or representation are evaluated through repeated cross-model observations.
How the implementation evolves
Winin versions its content maps, page associations and automated tests. As AI access patterns change, the implementation can be updated without breaking the relationship between public pages and their machine-readable counterparts.