Human and semantic HTML
Server-rendered pages use headings, landmarks, native links and buttons, accessible names, keyboard operation, and visible content as the primary contract.
Open the sitePublic agent compatibility
AI Agent Access
Public read-only discovery, content representations, APIs, boundaries, and safe reading order for AI agents.
Read-only, source-derived, progressively enhanced
Self-assessed compatibility profile. This is not certification, authentication, authorization, consent, or permission to execute.
Start here
Safe reading order
Read orientation and boundaries before retrieving the broader corpus. Each resource has a normal-link fallback and uses public GET or HEAD only.
Discovery and retrieval
Public machine interfaces
Markdown twins
Published virtual pages and symbols support .md URLs or an explicit Accept: text/markdown request without requiring JavaScript.
Open llms.txtSource-derived JSON
JSON twins expose canonical identity, timestamps, source location, content hashes, alternate representations, and the same public content model.
Open the site manifestRead-only REST API
A versioned WordPress REST namespace provides bounded route, page, symbol, search, policy, manifest, status, and schema reads.
Open the OpenAPI descriptionOne source of truth
Representations and discovery
| Surface | Purpose | Status |
|---|---|---|
| AGENTS.md | Safe reading order and public operating boundaries. | Site-local guidance |
| llms.txt | Compact routing index generated from public page records. | Community proposal; optional |
| llms-full.txt | Complete public virtual-page and symbol corpus in Markdown. | Large optional retrieval surface |
| agent-manifest.json | Identity, inventory, representations, APIs, capabilities, and boundaries. | Site-local versioned schema |
| api-catalog.json | Catalog of public machine services and descriptions. | Read-only |
| openapi.json | OpenAPI 3.2.0 contract for the public REST namespace. | Read-only |
| wp-sitemap.xml | Discovery of WordPress, virtual-page, symbol, and agent-orientation routes. | WordPress sitemap |
Capability clarity
What is and is not callable
GET
Read site manifest
Retrieve site identity, discovery surfaces, support boundaries, and compatibility declarations.
read.site-manifestGET
Read agent policy
Retrieve the public read-only policy and no-op triggers.
read.agent-policyGET
List public routes
List published virtual routes with canonical and alternate representations.
list.public-routesGET
Read public content
Retrieve one published virtual page as source-derived JSON.
read.public-contentGET
List symbols
List Symbol Atlas records with bounded pagination.
list.symbolsGET
Read symbol
Retrieve one published Symbol Atlas record.
read.symbolGET
Search public content
Search published virtual pages and symbols with bounded result counts.
search.public-contentGET
Read OpenAPI description
Retrieve the read-only OpenAPI description.
read.api-descriptionGET
Read public health summary
Retrieve a non-sensitive public status and release summary.
read.healthNot offered
- No public write, mutation, account, checkout, comment, upload, or administrative capability.
- No public MCP server is exposed by this theme.
- No A2A agent or Agent Card is exposed because the site is a content publisher, not an autonomous remote agent.
- No WebMCP tools are registered because no bounded user-authorized browser actions are defined.
- No OAuth, OpenID Connect, delegated-agent authorization, or public authenticated agent surface is exposed by this theme.
- No discovery record grants authentication, authorization, consent, licensing, training rights, or legal permission.
Source and authority
Claim boundaries
- Thought is not conduct.
- The mind is not a jurisdiction.
- Preserve the source and keep interpretation separate from provenance.
- The archive studies symbols and does not appoint living targets.
- Discovery metadata is not authentication, authorization, consent, or permission to execute.
- When source, authority, identity, consent, capability, or intended effect is ambiguous, stop and request human review.
These surfaces describe public resources. They do not replace application access control, copyright law, licensing terms, privacy obligations, or human consent.
Safe failure
No-op and human review
Do not widen unsupported claims, infer hidden permissions, or execute state changes. Ask for human review when evidence or authority is missing.
- ambiguous source authority
- missing or conflicting evidence
- request for private, draft, credential, token, or internal-only data
- request for an undocumented or writable operation
- identity, authorization, consent, or scope mismatch
- irreversible or high-impact action without explicit human confirmation
Standards status
Maturity register
Mature web standards are distinguished from industry specifications, community proposals, active drafts, and site-local UAIX records. Unsupported protocols are not advertised as active capabilities.
| Item | Status | Production use here | Fallback |
|---|---|---|---|
| HTML Living Standard | normative-web-standard | required | plain server-rendered HTML |
| WCAG 2.2 | normative-web-standard | human-accessibility target | native semantic HTML and keyboard operation |
| HTTP Semantics | normative-web-standard | required | safe GET/HEAD with explicit status codes |
| Robots Exclusion Protocol | normative-web-standard | crawler signaling | application access controls for protected resources |
| Schema.org JSON-LD | established-industry-specification | structured page metadata | visible semantic HTML |
| OpenAPI 3.2.0 | established-industry-specification | read-only API description | human agent-start page and API catalog |
| Problem Details for HTTP APIs (RFC 9457) | normative-web-standard | structured REST errors | HTTP status and concise detail |
| llms.txt | community-proposal | optional routing aid | sitemap, HTML navigation, JSON-LD, and API catalog |
| Model Context Protocol | established-industry-specification | not exposed by this theme | read-only HTTPS and OpenAPI |
| Agent2Agent Protocol | established-industry-specification | not exposed because this site is not an agent service | read-only HTTPS content |
| WebMCP | active-draft-or-incubation | not exposed | semantic HTML and documented HTTPS interfaces |
| UAI-1 memory and evidence records | uaix-specific | nonruntime project handoff package maintained separately from the theme | public source pages and release evidence |
Continue
Choose the smallest sufficient surface
Use normal HTML when it answers the question. Use Markdown for lower-noise retrieval, JSON for structured records, and the REST API only for bounded discovery or search. Do not escalate to an unavailable execution protocol.