On this page
RNX code library · 7 controls
RNX-150Headless Perception & Rendering Guardrails
Read what these checks mean, why they matter and which evidence they concern. Each ID below keeps its canonical place in the RNX hierarchy.
These are free learning summaries, not full technical tests or an industry certification. Specialized checks apply only to the relevant feature. Experimental labels are preserved from the canonical source.
RNX-150.T001
Rendered content availability
core readiness
Check that the intended reader or crawler can load the main content.
Why it matters. A page that works only in an unsupported display mode may look empty.
Illustration — fictional. A service description appears for the owner but never appears in the display mode supported by the tested crawler.
When it applies. Inspected target: url render. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-150.T002
Rendering resource access
core readiness
Allow the files and services needed to display public content.
Why it matters. Blocking a required resource can hide an otherwise healthy page.
Illustration — fictional. The file needed to show the product description is blocked, leaving the public page incomplete.
When it applies. Inspected target: render request set. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-150.T003
Route status integrity
core readiness
Make missing addresses return a genuine missing-page response.
Why it matters. A success signal with an error message gives tools conflicting evidence.
Illustration — fictional. A nonexistent page says Not found while its server response reports success.
When it applies. Inspected target: nonexistent route. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-150.T004
Hydration identity stability
core readiness
Check that browser scripts do not replace correct business facts with old ones.
Why it matters. A price should not change accidentally as the page finishes loading.
Illustration — fictional. The correct price appears first, then a browser script replaces it with an older price.
When it applies. Inspected target: url render. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-150.T005
Mobile primary-content parity
core readiness
Give mobile visitors equivalent essential content.
Why it matters. A smaller screen should not remove the facts needed to understand the business.
Illustration — fictional. Mobile template hides service eligibility entirely.
When it applies. Inspected target: mobile page. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-150.T101
Direct-entry route content parity
core readiness
Make a valid page work when opened directly as well as through site navigation.
Why it matters. Shared links should not lose the main content.
Illustration — fictional. In-app navigation works but direct entry loads the homepage shell or wrong product.
When it applies. Inspected target: route entry pair. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.
RNX-155 · RAG-Ready Documentation
RNX-155.T001
Owned RAG answer evidence support
Experimental — not an established ranking requirement
For your own retrieval-based answer system, support material answers with the retrieved evidence or admit uncertainty.
Why it matters. Finding a relevant document does not prove every answer is correct.
Illustration — fictional. Answer invents a delivery promise absent from sources.
When it applies. Inspected target: generated answer. Use this check only when that object or feature exists in the review scope; provider-specific checks require that provider's integration. Missing evidence remains unknown.