Summary
Volume 5 makes the AI-Ready Web program machine-usable. A site can publish an AI-Ready manifest, a readiness assessment result, and a route inventory without claiming certification. The goal is evidence portability: future humans and agents can see what was checked, what was skipped, what is blocked, and what remains planned.
Artifact set
- Requirement registry JSONStable ARW requirement identifiers, tests, evidence, and anti-patterns.
- Maturity register JSONCurrent stable, current optional, 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.
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."
}[]Field order follows the keyed JSON example, the published schema order, and the public field registry.
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.