Agentmarkup, build-time JSON-LD and llms.txt checks for Vite/Astro
Build-time llms.txt generation before the spec becomes mandatory everywhere.
Machine-readable agent conduct rules for restaurants. A /.well-known/restarules.json discovery model.
Robots.txt for AI restaurant agents addressing real regulatory compliance needs.
Restaurant owners and AI agent developers
robots.txt · schema.org · OpenAPI Specification
Build-time llms.txt generation before the spec becomes mandatory everywhere.
Clear directives for AI training when robots.txt says nothing about LLMs.
Transparent AI bot posture tracking, but 'what bots touch you' is already solved by uBlock Origin.
Robots.txt for purchasing agents cuts token usage by 6x compared to scraping.
One UI format across all platforms; 97% token savings vs JSON for LLM agents.
This is someone treating a CV as structured data rather than a PDF: resume.json, evidence.json, availability.json, agent-card.json and a curated llms.txt are all exposed plus schema.org JSON-LD. Nice touches include GitHub Actions that validate links and push an IndexNow update on every commit — practical engineering to get content noticed by crawlers and agents. It’s a focused, well-implemented experiment, but its usefulness depends on broader adoption or tooling that consumes these bespoke conventions.