On this page
RNX code library · 5 controls
RNX-440Compliance Synchronization & Safe Selection
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-441 · Dynamic Compliance Header
RNX-441.T001
Private compliance metadata expiry
Experimental — not an established ranking requirement
For private compliance labels, check validity and expiry.
Why it matters. A machine-readable label is not by itself proof of compliance.
Illustration — fictional. An expired machine-readable label is accepted as proof of current certification.
When it applies. Inspected target: metadata fixture. 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-442 · Data Residency & Sovereignty Tags
RNX-442.T001
Residency declaration traceability
Experimental — not an established ranking requirement
Support processing-location claims with documented evidence.
Why it matters. A region named in a policy does not prove where processing actually occurred.
Illustration — fictional. A location declaration omits an active processor operating outside the claimed region.
When it applies. Inspected target: region declaration. 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-443 · Ethical Action Boundaries
RNX-443.T001
Enforceable ethical restriction
Experimental — not an established ranking requirement
Enforce declared ethical restrictions or the required human decision.
Why it matters. Principles need a working boundary at the point of action.
Illustration — fictional. No unauthorized-sharing gate despite policy.
When it applies. Inspected target: ethical gate. 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-444 · Emergency Crisis Protocol
RNX-444.T001
Emergency suspension drill
Experimental — not an established ranking requirement
Test emergency suspension and record what remains in sessions or saved copies.
Why it matters. Stopping new work may not erase every previous effect.
Illustration — fictional. An emergency stop blocks new logins while existing sessions can still perform prohibited actions.
When it applies. Inspected target: suspension fixture. 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-445 · Jurisdictional Processing Controls
RNX-445.T001
Processing-region enforcement
Experimental — not an established ranking requirement
Check actual processing against permitted regions.
Why it matters. Unknown outside processors must remain unresolved rather than being assumed compliant.
Illustration — fictional. The main service uses an approved region, but an unaccounted worker processes data elsewhere.
When it applies. Inspected target: routing observation. 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.