Quality is multidimensional
One pass flag hides too much. Technical integrity, temporal synchronization, semantic validity, coverage, privacy, rights eligibility, and release approval should be recorded separately.
A failed in-game task can be valuable training data. A successful task can still fail release because its action stream is missing or rights remain unresolved.
Provenance survives transformation
Each released artifact should resolve to source capture, checksums, transformation code, parameters, collection context, and review decision.
Immutable lineage makes a bad transformation reproducible and a withdrawal targeted. Without it, every derivative becomes suspect.
Rights review fails closed
Discovered content is not releasable inventory. Records move through quarantine, rights review, approval or rejection, ingestion, release, and withdrawal.
The registry should cover allowed uses, redistribution, customer access, territory, duration, attribution, restrictions, and the evidence supporting each decision.
- No commercial claim based only on download access
- No silent mixing of first-party and third-party material
- No license string without source-level provenance
- No release when required authority remains unknown