> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/develop/guardian/workspace/policies/versioning-and-deprecation-policy.md).

# Policy Versioning and Deprecation

Policy versioning in Guardian allows a methodology or workflow to evolve over time without breaking existing projects. Each policy can have multiple versions, ensuring traceability, flexibility, and regulatory compliance.

**Key Points:**

* New versions are created when standards bodies, registries, or auditors update rules, schemas, or workflows.
* Old versions remain intact so existing projects continue without disruption.
* Each version has a unique identifier (e.g., VM0042 v1.0, VM0042 v2.1).
* Backward compatibility is maintained via data migration tools.

Deprecation means a policy version is officially discontinued and cannot be used for new projects, though historical data is preserved for auditability.

**Key Points:**

* A deprecated policy cannot onboard new users or issue new credentials.
* Existing projects under that policy may either:
  * Continue under old rules (frozen state), or
  * Migrate to a newer version using Guardian’s Migration Wizard.
* Deprecation ensures stakeholders are aligned with up-to-date methodologies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guardian.hedera.com/docs/develop/guardian/workspace/policies/versioning-and-deprecation-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.