Summary
Volume 3 is the normative AI-Ready Web specification surface. The machine-readable registry at ai-ready-web-requirements.json is the canonical requirement list; this page explains the requirement families and how to apply them without overclaiming support.
Requirement families
| Family | Requirement IDs | Result |
|---|---|---|
| Core architecture | ARW-001 to ARW-003 | Human-first surface, explicit support boundary, stable maturity labels. |
| Accessibility and rendering | ARW-010 to ARW-014 | Accessible semantic page surface, keyboard/focus reliability, no JavaScript-only critical facts. |
| Discovery and content | ARW-020 to ARW-026 | Robots, sitemap, .well-known, llms advisory file, route inventory, canonical IDs, alternate representations. |
| APIs and capabilities | ARW-030 to ARW-037 | OpenAPI routes, idempotency, Problem Details, capability matrix, no-op fallback, human review URL. |
| Identity, security, privacy | ARW-040 to ARW-049 | Least privilege, consent, data minimization, rights signals, auth boundaries, secret exclusion. |
| Provenance and operations | ARW-050 to ARW-058 | Trace Context, audit packets, freshness, monitoring, incident review, release evidence. |
| Governance and lifecycle | ARW-060 to ARW-066 | Claim review, maturity register updates, roadmap gates, validator results, translation parity. |
Normative language
MUST means the site cannot claim that profile without evidence. SHOULD means the site needs either implementation evidence or a documented exception. MAY means optional or ecosystem-dependent. Proposal and research-track mechanisms must not be the only evidence behind a current support claim.
Stable standards baseline
- WCAG 2.2 and semantic HTML are the baseline for both people and agent-visible accessibility trees.
- HTTP Semantics, HTTP Caching, and Robots Exclusion Protocol anchor delivery and crawl boundaries.
- JSON Schema 2020-12, OpenAPI, Problem Details, and Trace Context anchor structured exchange, errors, and evidence.
- JSON-LD 1.1 and Schema.org anchor public entity clarity where appropriate.
Support boundary
AI-Ready Web requirements describe public site preparation and review evidence. They do not authorize scraping, bypass terms, validate credentials, grant tools, certify agent behavior, or prove safety. When requested work exceeds declared support, the correct behavior is no-op plus human review through Contact and Review.
Machine-readable registry
- Requirement registry JSONStable ARW requirement identifiers, tests, evidence, and anti-patterns.
- Maturity register JSONCurrent stable, configuration-specific, proposal, research, and unsupported mechanisms.
- Route inventory JSONSource/live audit facts, publication boundary, and route exposure plan.
- AI-Ready site manifest schemaPortable declaration for discovery, capabilities, policies, evidence, and support boundaries.
- AI-Ready site manifest exampleConcrete UAIX-flavored example without claiming hosted runtime execution.
- Readiness result schemaAssessment result model for automated checks plus manual review evidence.
- Readiness result exampleExample scoring packet with warnings, blockers, and no certification claim.