On this page
RNX code library · 6 controls
RNX-210Fact Corroboration
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-211 · NAPD Multi-Hub Synchronization
RNX-211.T001
External listing identity match
core readiness
Match an outside listing to the right business and branch.
Why it matters. A correct-looking record for a different location is still the wrong evidence.
Illustration — fictional. Headquarters' phone is used to mark every branch phone number incorrect.
When it applies. Inspected target: external listing identity record. 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-212 · Entity Handshake & UID Mapping
RNX-212.T001
External identifier resolution
Experimental — not an established ranking requirement
Check that an external identifier resolves to the intended entity.
Why it matters. A same-name organization should not inherit another's identity.
Illustration — fictional. The business publishes a valid license number belonging to an unrelated similarly named contractor.
When it applies. Inspected target: external identifier mapping. 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-213 · Consensus Gap & Drift Detection
RNX-213.T001
Conflict register completeness
Experimental — not an established ranking requirement
Record factual conflicts with their sources and dates.
Why it matters. Historical information should not be confused with a current contradiction.
Illustration — fictional. A discrepancy record says bad citation but retains neither the wrong value nor its source/date.
When it applies. Inspected target: identity conflict register. 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-216 · Canonical Organization Fingerprinting
RNX-216.T001
Stable entity matching key
Experimental — not an established ranking requirement
Keep a stable internal identity while updating its facts and history.
Why it matters. Renaming a business should not accidentally create a different entity.
Illustration — fictional. A harmless rebrand creates a new identity and discards the old entity's source history.
When it applies. Inspected target: entity matching-key definition. 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-217 · Namespace Arbitration & Conflict Resolution
RNX-217.T001
Name-collision adjudication
Experimental — not an established ranking requirement
Use supporting identifiers to resolve same-name matches.
Why it matters. When the evidence is insufficient, leave the match unresolved.
Illustration — fictional. Two unrelated Acme businesses are merged because their display names are identical.
When it applies. Inspected target: namesake adjudication case. 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-218 · Authority Drift Severity Scoring
RNX-218.T001
Conflict risk rubric
Experimental — not an established ranking requirement
Prioritize identity conflicts by verified consequences.
Why it matters. An invented search-engine weight is not a sound reason to call a conflict urgent.
Illustration — fictional. An invented high-authority weight makes a harmless punctuation difference outrank a wrong booking phone.
When it applies. Inspected target: identity conflict severity decision. 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.