On this page

RNX code library · 11 controls

RNX-600Topic Architecture Standard

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-611 · Semantic Cluster Cohesion

RNX-611.T001

Hub scope and relevant links

core readiness

Build topic hubs around relevant, accessible supporting pages.

Why it matters. A hub should help a reader complete a real task.

Illustration — fictional. Hub links unrelated financial offers.

When it applies. Inspected target: hub link. 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.

Canonical parentage

RNX-600 · Topic Architecture Standard RNX-611 · Semantic Cluster Cohesion

RNX-612 · Descriptive Anchor Integrity

4 controls. Check that important internal links reach usable pages.

RNX-613 · Crawl Path Efficiency

4 controls. For lists spread across pages, check that later pages have working links.

RNX-614 · Vector-Aware Information Segmentation

RNX-614.T001

Segmentation retrieval relevance benchmark

Experimental — not an established ranking requirement

For retrieval tests, judge whether returned pieces are relevant to the question.

Why it matters. The accuracy of a generated answer still needs its own check.

Illustration — fictional. A retrieval comparison changes both the model and the questions, making the claimed comparison unclear.

When it applies. Inspected target: retrieval comparison. 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.

Canonical parentage

RNX-600 · Topic Architecture Standard RNX-614 · Vector-Aware Information Segmentation

RNX-617 · Intra-Cluster Contradiction Detection

RNX-617.T001

Current-document contradiction

Experimental — not an established ranking requirement

Keep current documents in agreement and label historical ones.

Why it matters. An old PDF should not silently contradict today's eligibility rules.

Illustration — fictional. Current PDF and page disagree on eligibility.

When it applies. Inspected target: claim 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.

Canonical parentage

RNX-600 · Topic Architecture Standard RNX-617 · Intra-Cluster Contradiction Detection

Related learning