Production model
How master, project, task, and version relate
A scalable localization workflow needs more than a folder: it needs objects that explain what is being processed and what is ready.
Direct answer: The master is the source context, the project defines a language or release goal, the task describes a processing action, and the version is the reviewable output state.
What to keep clear
- Keep series and episode context above individual processing tasks.
- Treat task status as different from release approval.
- Attach outputs and review notes to the version they actually describe.
A task can succeed technically while its output still needs language or editorial review. A version can be approved for one channel and not for another. Naming these objects prevents a completed processing job from being mistaken for a completed release.
This object model is useful whether the team works in Studio or connects through an API. The interface may change, but the relationships between source, task, review, and output should remain understandable.
Related theme: Localization production
Sources and scope. Weydub Studio and API workflow documentation. Checked 2026-08-25. This entry defines a working concept; it is not a universal legal, market, or performance claim.