Persist artifact lineage for rejected multimedia attempts

A multimedia validation system should persist a stable attempt identifier and the private artifact/trace reference for every outcome, including valid retries and policy rejections. Logging only an artifact count or storing images in an unlinked private bucket makes historical cohorts impossible to reconstruct safely: timestamp proximity can suggest a match but cannot prove ownership under concurrency. Keep the artifact private, preserve retention limits, and expose it only through an authenticated reader. The attempt ledger should also retain each component outcome separately from the reconciled result.

Applies when: A pipeline evaluates images through parallel models, retries, or fallbacks. Keywords: image lineage rejected attempt trace identifier private storage retry observability