On this page

RNX code library · 6 controls

RNX-420Attribution & Intellectual Provenance

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-421 · Source-Chain Verification

RNX-421.T001

Cited source version digest

Experimental — not an established ranking requirement

Check that a recorded source fingerprint matches the version being cited.

Why it matters. A mismatch signals change, not automatic proof that the content is false.

Illustration — fictional. A source fingerprint is calculated from today's page instead of the older version actually cited.

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

Canonical parentage

RNX-400 · Governance, Compliance & Ethics RNX-420 · Attribution & Intellectual Provenance RNX-421 · Source-Chain Verification

RNX-422 · Licensed Content Attribution

RNX-422.T001

Reused asset permission

Experimental — not an established ranking requirement

Confirm permission and required credit before reusing an asset.

Why it matters. Public availability does not mean unrestricted reuse.

Illustration — fictional. Editorial-only image used in paid ad.

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

Canonical parentage

RNX-400 · Governance, Compliance & Ethics RNX-420 · Attribution & Intellectual Provenance RNX-422 · Licensed Content Attribution

RNX-424 · Canonical Authority Ledger

RNX-424.T001

Authoritative record revision

Experimental — not an established ranking requirement

Identify the approved current record and its version history.

Why it matters. Connected systems need to distinguish it from an old draft.

Illustration — fictional. A replaced fact is still returned without any indication that a newer approved version exists.

When it applies. Inspected target: revision resolution. 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-400 · Governance, Compliance & Ethics RNX-420 · Attribution & Intellectual Provenance RNX-424 · Canonical Authority Ledger

RNX-425 · AI Usage Rights Manifest

RNX-425.T001

Provider-specific usage policy accuracy

Experimental — not an established ranking requirement

Explain usage choices separately for each provider and purpose.

Why it matters. A published policy cannot promise universal enforcement across all AI systems.

Illustration — fictional. Custom page claims prevention of all training use.

When it applies. Inspected target: policy claim. 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-400 · Governance, Compliance & Ethics RNX-420 · Attribution & Intellectual Provenance RNX-425 · AI Usage Rights Manifest

RNX-426 · Human Verification Attestation

RNX-426.T001

Human approval evidence

Experimental — not an established ranking requirement

Support a human-review claim with an actual approval of a stated version and scope.

Why it matters. A review badge should not imply work nobody performed.

Illustration — fictional. Reviewed badge copied to unreviewed pages.

When it applies. Inspected target: review assertion. 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-400 · Governance, Compliance & Ethics RNX-420 · Attribution & Intellectual Provenance RNX-426 · Human Verification Attestation

RNX-427 · Machine-Readable Deprecation & Forgetting Protocol

RNX-427.T001

Controlled deprecation handling

Experimental — not an established ranking requirement

When retiring a controlled interface or record, provide its replacement or an explicit retired status.

Why it matters. Silent disappearance leaves connected users guessing.

Illustration — fictional. An owned retrieval index keeps an old price after the controlled source has been retired and refreshed.

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

Canonical parentage

RNX-400 · Governance, Compliance & Ethics RNX-420 · Attribution & Intellectual Provenance RNX-427 · Machine-Readable Deprecation & Forgetting Protocol

Related learning