On this page
RNX code library · 5 controls
RNX-410Deterministic Guardrails & Liability Isolation
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-411 · Action-Boundary Manifest
RNX-411.T001
Declared boundary enforcement mapping
Experimental — not an established ranking requirement
Connect declared operating boundaries to real enforcement.
Why it matters. A policy document alone cannot stop a prohibited action.
Illustration — fictional. A manifest forbids deletion, but the service still accepts a deletion request.
When it applies. Inspected target: runtime boundary. 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-412 · Contractual Non-Repudiation Markers
RNX-412.T001
Consent revision trace
Experimental — not an established ranking requirement
Record who approved which exact revision of consent.
Why it matters. Agreement to an older version does not establish agreement to new terms.
Illustration — fictional. An approval with no recorded document version is reused for changed terms.
When it applies. Inspected target: consent revision. 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-413 · Liability Disclaimers for Inference
RNX-413.T001
Visible professional limitation
Experimental — not an established ranking requirement
Show professional limits clearly and keep behavior within them.
Why it matters. A disclaimer does not create legal immunity or extra qualifications.
Illustration — fictional. Disclaimer appears only after action.
When it applies. Inspected target: scope disclosure. 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-414 · Delegated Authority Envelope
RNX-414.T001
Delegated audience validation
core readiness
Check that delegated credentials are intended for the receiving service.
Why it matters. A valid credential for one audience is not permission for every other service.
Illustration — fictional. A credential intended for another service is accepted merely because its signature is valid.
When it applies. Inspected target: audience 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-415 · Executable Professional Boundary Enforcement
RNX-415.T001
Prohibited professional action test
Experimental — not an established ranking requirement
Refuse prohibited professional actions and offer an allowed escalation path.
Why it matters. A helpful agent should recognize when a qualified person must take over.
Illustration — fictional. The visible interface refuses a prohibited action, but the underlying tool performs it.
When it applies. Inspected target: professional action. 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.