Summary
Volume 5 makes the AI-Ready Web program machine-usable. A site can publish an AI-Ready manifest, a .well-known discovery pointer, a readiness assessment result, a route inventory, and aligned root discovery files without claiming certification. The goal is evidence portability: future humans and agents can see what was checked, what was skipped, what is blocked, what remains planned, and which package or root-file output must be deployed.
Agent implementation contract
When a user sends an agent to this AI-Ready Web guidance, the assignment is to apply the strategy to the user's target site, repository, or publication package. Treat UAIX as the reference standard and checklist. Do not copy UAIX page content into the target site, do not create a page about UAIX guidance, and do not publish an "AI-Ready Web" explainer unless the user explicitly asks for that output.
The expected target-site evidence set is concrete: public manifest, .well-known discovery, route inventory, readiness result, robots.txt, sitemap, llms.txt, structured data, visible support boundaries, targeted checks, and package or root-file output when publication is requested.
| Agent step | Do the real implementation | Do not do this |
|---|---|---|
| Resolve the target | Identify the target domain, repo root, public routes, build system, CMS, deployment package, root-file output path, and current evidence before editing. | Assume UAIX.org is the target site, summarize this page, or make a new guidance page because this page was provided as a reference. |
| Audit the existing site | Check human HTML, headings, metadata, canonical URLs, robots, sitemaps, schema, .well-known files, llms files, APIs, route inventories, readiness records, accessibility, privacy, and support boundaries. | Skip the target-site audit and only restate AEO/GEO/SEO definitions. |
| Implement improvements | Update the target site's pages, navigation, structured data, discovery files, route inventory, readiness records, public evidence, AEO/GEO/SEO copy, no-op guidance, review paths, and publish-package root files where the audit shows gaps. | Keyword-stuff, cloak, add hidden bot-only text, inject prompts for models, fabricate citations, or create synthetic doorway pages. |
| Verify and package | Run the site's targeted checks, record changed files and routes, name skipped checks and blockers, and provide the requested root files, root ZIP, or publish package when the user asks for deployable output. | Claim readiness, certification, endorsement, ranking gains, live publication, or agent authority without evidence. |
Artifact set
- 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.
Target-site artifact checklist
A target site applying this guidance should create or align the public manifest, .well-known discovery, route inventory, readiness result, robots.txt, sitemap, llms.txt, structured data, support-boundary text, targeted checks, and any deployable root-file package. If one of those artifacts is intentionally absent, the readiness result should name the skipped check and residual risk.
Manifest shape
The manifest schema declares site identity, public routes, discovery files, capability profiles, API contracts, policy boundaries, evidence links, freshness, and unsupported claims. It is designed for public-safe data only.
{
"profileId": "uaix.ai-ready-web.manifest.v1",
"site": { "name": "Example", "url": "https://example.com/" },
"readinessProfiles": ["ARW-F0", "ARW-F1"],
"discovery": { "robots": "https://example.com/robots.txt" },
"supportBoundary": "Public discovery and evidence only; no runtime authority."
}Readiness result shape
The readiness result records automated checks, manual checks, warnings, blockers, score bands, skipped checks, evidence URLs, and the statement that the result is not certification or endorsement.
Registry relation
AI-Ready Web artifacts complement UAI-1. Use UAI-1 when portable messages, memory packages, handoffs, review receipts, and evidence packets need to travel. Use the AI-Ready manifest when a website needs to state how it is readable, discoverable, actionable, governed, and bounded.
Validation rule
Every artifact must be parseable JSON, must use stable profile IDs, must contain a support boundary, must avoid secrets, must distinguish stable standards from proposals, and must point to human-review paths for unsafe or unsupported work.