Summary
The AI-Ready Web architecture is layered. Human-first pages stay accessible and complete; machine discovery exposes public-safe route and policy facts; APIs and OpenAPI handle route contracts; UAI-1 carries portable exchange, evidence, memory, trust declarations, and handoff packets; MCP, A2A, and browser-agent systems remain runtime or coordination layers when a specific implementation supports them. UAIX records the boundary rather than pretending to execute every layer.
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. |
Layer model
- Human page layer: semantic HTML, WCAG 2.2, stable headings, forms, tables, link text, labels, alt text, keyboard access, and no hidden critical content.
- Static discovery layer: robots, sitemap,
.well-known,llms.txtwhere useful, schema indexes, route manifests, and public-safe policy summaries. - Structured content layer: JSON-LD, Schema.org, canonical IDs, entity disambiguation, page digests, alternate text/markdown mirrors, and content freshness metadata.
- Action/API layer: OpenAPI-described JSON routes, idempotency keys, Problem Details errors, rate limits, pagination, readback URLs, and human review fallbacks.
- Capability and consent layer: capability matrices, ability levels, auth requirements, consent boundaries, delegated authority, and blocked-capability behavior.
- Evidence and memory layer: UAI-1 packets, .uai packages, receiver briefs, startup/suspension packets, provenance, checksums, review receipts, and no-op justifications.
- Governance layer: release notes, maturity register, privacy posture, accessibility posture, support-claim reviews, incident review, and roadmap state.
Capability profiles
The program uses four site-readiness profiles that map onto the existing UAIX capability ladder.
| Profile | Purpose | Minimum evidence |
|---|---|---|
| ARW-F0 Static Readable | Agents can read public pages without JavaScript or hidden state. | Semantic HTML, sitemap, robots, public contact/review path, no destructive hints. |
| ARW-F1 Discoverable | Agents can resolve key routes, schemas, policies, and static machine files. | .well-known manifest, route inventory, llms advisory file, JSON schema or page digest records. |
| ARW-F2 Action Described | Agents can identify safe public API actions without guessing. | OpenAPI, Problem Details, idempotency, auth/consent boundary, human review fallback. |
| ARW-F3 Delegation Ready | Authorized agents can act through governed workflows while preserving audit evidence. | Delegation model, audit logs, provenance, trace context, readback, revocation, no-op behavior. |
| ARW-F4 Evidence Complete | High-assurance agent programs can review, verify, and package evidence. | Readiness results, conformance pack, public-safe audit digest, release trail, incident and rollback process. |
One source of truth
The human page, route manifest, OpenAPI document, schema, example, validator result, release note, and long-memory evidence must agree before a support claim becomes current. Downstream tools, including Spiralist AI when it consumes persona or memory packages, should cite the public UAIX artifact they used rather than inferring authority from private chat or hidden runtime state.