Generated Video Delivery — Status-Gated Download URLs in Marketplace OCR Pipelines
Short answer: issue a generated-video download URL only after the persisted asset is ready and its moderation evidence covers the bytes a buyer will receive. OCR coverage belongs in that release gate, not in a browser guess about whether a worker has finished. The page that wakes me is rarely the first failure. A seller sees a clip in the download center, clicks it, and gets a file that cannot…
The key to a reliable generated video delivery system is ensuring that the generated asset is properly released and ready for download only after the necessary OCR coverage has been completed and verified. This means that the download URL should not be issued until the asset is in a "ready" state and its OCR evidence covers the bytes that the buyer will receive.
The OCR coverage should be recorded as a part of the release gate, rather than being dependent on a browser's guess about whether the worker has finished processing.
The download URL should only be minted from a "ready" record that has an attached OCR decision, ensuring that the viewer's marketplace scope is taken into account. The URL service should be authoritative and re-read the record, check the viewer's permissions, and create a short-lived capability tied to the asset ID. This prevents duplicate deliveries and maintains the integrity of the moderation workflow.
When designing the moderation workflow, it's important to define what OCR must see before release, whether it's all frames, a sampled set, or only the seller's source images. The policy version should be recorded with the asset, so reviewers can understand why a link was allowed or blocked. A decision table can be used to document the constraints and release conditions, ensuring that all stakeholders are aware of the release criteria.
The download center should clearly indicate the current state of the asset, transitioning from "submitted" to "processing" to "ready" to "blocked," "failed," or "expired." Each state should have a distinct action, with unavailable downloads at non-ready states and a clear path for review when necessary. It's crucial to stop polling at terminal states to prevent unnecessary noise and ensure that real queue-age alerts are not masked.
The media format, container, and codec should be recorded and validated before publication, with a clear fallback behavior documented. This ensures that the downloaded asset meets the intended requirements and can be properly processed by the buyer's intended tools. By following these guidelines, generated video delivery systems can maintain a robust and reliable moderation workflow, providing buyers with safe, trustworthy, and reliable access to the generated assets.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
