# Versioning: Drafts, Versions, and Promotion Versioning in Agentic Studio is the mechanism that keeps digital worker changes controlled, auditable, and reversible. It ensures that Production environments always run a known, stable configuration while teams are free to iterate in UAT. ### **Draft vs Versioned Copies** Every digital worker has exactly one Draft at any time. The Draft lives in UAT and is the only copy you can actively edit. When your changes are complete and testing is done, you publish the Draft. At that point, a versioned copy is created and the Draft resets as the starting point for your next round of changes. Versioned copies are read-only. Once published, they cannot be modified. This immutability is what makes the version history reliable and auditable. ### **Version Format** Versions use a major. Minor format, for example 1.4 or 2.0. Publishing always increments the minor version. Major version changes are typically reserved for significant structural changes to the digital worker. | Version Event | Result | | -------------------------------------- | ------------------------------------------------------------- | | Install from Marketplace (version 1.5) | Digital worker is set to 1.5; a Draft copy of 1.5 is created. | | Make changes and publish | Draft becomes version 1.6; a new Draft is created from 1.6. | | Make further changes and publish | Draft becomes version 1.7; and so on. | | Push version 1.6 to Production | Production runs 1.6 even if 1.7 exists in UAT. | ### **Installing from the Marketplace** When you install a digital worker from the Marketplace, the template version is preserved exactly. If the Marketplace template is at version 1.5, your installed digital worker starts at version 1.5, and a Draft copy of 1.5 is created as your starting point for customization. ### **Pushing to Production** You can promote any published version, not just the most recent one, to Production. This gives you the flexibility to roll back to an earlier stable version if a newer one introduces issues. Important: The platform does not enforce version order or require evidence of testing before promotion. Your team is responsible for defining and following a release process that ensures only tested, approved versions reach Production. ### **Why Immutable Versions Matter** Immutable versions mean that what ran in Production on a given date is always recoverable and comparable. This is critical for audits, incident investigation, and evaluating whether a change to instructions or skills actually improved performance. If you need to know exactly what configuration was running last Tuesday, you can look it up by version number. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kb.theloops.io/agenticstudio/resource-library/explainers/versioning-drafts-versions-and-promotion.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.