Delivery
Channel specifications belong in the delivery package
A release package should describe the files, language, version, metadata, rights, and destination together.
Direct answer: The package is complete when the destination can identify and use the correct video, subtitle, audio, metadata, and release state without reconstructing project context.
What to keep clear
- Record the target channel, territory, locale, and episode order.
- Keep separate-track, burned-in, dubbed, mix, and metadata requirements explicit.
- Verify filenames, manifests, rights scope, and version before handoff.
Different destinations accept different combinations of media and text. A package that plays locally may still fail a platform upload because its subtitle format, audio track, metadata, or rights window is wrong.
Attaching the specification to the output version keeps delivery review close to production. It also lets a team reuse the same localized work for another channel while making the new package requirements visible.
Related theme: Distribution and delivery
Sources and scope. Weydub public channel and delivery documentation. Checked 2026-08-25. This entry defines a working concept; it is not a universal legal, market, or performance claim.