# Versioning and Deprecation Policy

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: 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://guardian.hedera.com/guardian-dev/guardian/standard-registry/policies/versioning-and-deprecation-policy.md?ask=<question>
```

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.