This page is the public quality and discovery record for ARuntime.com. It explains how the site’s own runtime pages are structured so humans, search engines, answer engines, and generative systems can find the same visible facts without hidden bot text, copied guidance, or unsupported readiness claims.
Definition
For ARuntime.com, content quality means a public runtime page states its definition, scope, evidence, limitations, related pages, and maintenance record in visible HTML. Machine-readable files may summarize that content, but they do not add claims that are absent from the human page.
What changed in v3.8.0
The previous implementation created generic AI-ready, AEO, GEO, and SEO explainer pages. That was the wrong target. This release repurposes those routes as site-specific quality and discovery records, removes external guidance copy, removes UAIX source links from public release surfaces, and applies the actual practice to ARuntime runtime pages, metadata, navigation, feeds, sitemaps, and discovery files.
Visible page standard
| Page element | Required behavior | Why it exists |
|---|---|---|
| Direct answer | State the answer or definition near the top. | Helps readers and answer systems identify the canonical summary. |
| Scope boundary | Say what the concept owns and does not own. | Prevents broad runtime terms from becoming hype labels. |
| Evidence | Use source links, diagrams, route inventory, or visible maintenance records. | Keeps generated summaries grounded in reviewable material. |
| Limitations | Mark proposals, immature categories, unsupported actions, and review triggers. | Prevents certification or ranking claims without evidence. |
| Machine-readable companion | Mirror the visible page through sitemap, llms files, catalogs, and JSON only when they match. | Supports discovery without cloaking. |
What this site does
- Publishes a vendor-neutral reference model for AI runtime architecture.
- Explains runtime layers, category boundaries, implementation patterns, risks, and metrics.
- Provides public schemas, examples, diagrams, catalogs, glossary records, RSS, sitemap entries, and llms advisory files.
- Labels emerging runtime terms as architectural categories or proposals when they are not formal standards.
- Provides a correction path when source claims, routes, or descriptions are stale.
What this site does not do
- It does not certify a runtime product, website, or implementation.
- It does not grant scraping, account, credential, API, or tool authority.
- It does not promise search rankings, citation inclusion, answer placement, or generative-engine preference.
- It does not publish hidden bot-only text or prompt instructions to manipulate models.
- It does not replace human review for high-risk architecture, security, legal, medical, or financial decisions.
Evidence map
AI Runtime Overview
Canonical definition, adjacent-concept boundaries, and source-backed runtime explanation.
Emerging Runtime Types
Direct comparison matrix for AIR, AEE, MIR, SRE, CRE, and NEE.
Runtime Selection Guide
Decision path for selecting the correct runtime boundary instead of a marketing category.
Content catalog
Machine-readable route, review, audience, and search-intent metadata aligned with visible pages.
llms.txt
Plain-text orientation for public model retrieval and citation workflows.
Corrections
Human route for source drift, broken links, factual updates, and editorial fixes.
Explicit anti-patterns
- No copied guidance pages.
- No keyword-stuffed doorway pages.
- No cloaking or hidden bot-only instructions.
- No prompt-injection text directed at crawlers or AI tools.
- No fake citations, invented standards, guaranteed rankings, or endorsement claims.
- No JSON-LD that states a claim not present on the visible page.
Maintenance record
| Content release | aRuntime.com Content Repair Release: v3.8.0 |
|---|---|
| Last reviewed | 2026-06-27 UTC |
| Last materially changed | 2026-06-27 UTC |
| Review path | Corrections |