Pillar 2 — Content Legibility
Layer A — Agent Readiness. Owner: Engineering + Content. Weight: 25 pts.
Items in this pillar
Section titled “Items in this pillar”| # | Item | Status | Authority |
|---|---|---|---|
| 05 | Markdown via content negotiation and URL-suffix fallback (/index.md) | recommended | Cloudflare convention — fallback is mandatory because most agents do not send Accept: text/markdown |
| 06 | HTML stub instructions for non-markdown agents | framix convention | House rule (mirrors the Cloudflare docs pattern) |
| 07 | /llms.txt at site root, < 50 KB, structured per spec | recommended | llmstxt.org — ship it; do not sell it as a citation lever |
| 08 | Hierarchical llms-full.txt per major section, ≤ 200 KB each | framix convention | House rule (mirrors the Cloudflare docs pattern) |
| 09 | Semantic HTML, SSR-first; all indexable content in the first response; JSON-LD blocks preserved through markdown conversion | required | Universal web convention |
Full item descriptions: Universal Requirements § Pillar 2.
On the llms.txt question
Section titled “On the llms.txt question”Independent studies through Q1 2026 show no measurable citation uplift from llms.txt alone. Framix ships it because the cost is negligible, the format lands well with developer-tools clients (Anthropic, Vercel, Cloudflare, Mintlify all use it), and the convention is becoming a discoverability standard. Frame it as plumbing, not a citation lever. Mike King argues a stronger case — that Claude and other non-Google systems may parse it (_sources/expert-mike-king.md); Google’s official guidance says publishers can ignore it (_sources/google-ai-optimization-guide.md.txt). v1.1 sits between the two.
Where this gets enforced
Section titled “Where this gets enforced”Gate A — Technical checks A.3 (/llms.txt), A.4 (llms-full.txt per section), A.5 (markdown content negotiation headers), A.6 (/index.md URL fallback), and A.15 (no-JS rendering) against these items before any property ships.