> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/checks/governance_control/gov_0001.md).

# Change management

<table><thead><tr><th width="138">Check ID</th><th>GOV_0001</th></tr></thead><tbody><tr><td>Category</td><td>Compliance</td></tr><tr><td>Summary</td><td><strong>Change Management</strong> ensures that all application and configuration changes are traceable, governed, and properly controlled. Based on the selected Coverage Profile, it verifies deployment traceability, approval before release, rollback registration, and—at the strictest level—independent review (separation of duties). Compliance is continuously evaluated using audit event evidence across the selected environments.</td></tr><tr><td>Options</td><td><p></p><ul><li><strong>Coverage Profile</strong> – Defines how rigorously the control is evaluated. It determines which audit events are required as evidence, what governance conditions must be met, and how strictly compliance is assessed.</li><li><strong>Environment Scope</strong> – Defines where the control applies. It determines which environment types (e.g., Production, Acceptance, Development) are evaluated for compliance with the selected Coverage Profile.</li></ul></td></tr></tbody></table>

### Coverage Profiles

The table below describes the coverage profiles available for this control. For a general understanding of how coverage profiles work please see the [Controls](/checks/governance_control.md) page.

<table><thead><tr><th width="118.5">Coverage Profile</th><th width="198.5">Profile Description</th><th width="204">Evidence Event Codes</th><th>Coverage Profile Description</th></tr></thead><tbody><tr><td><strong>Basic</strong></td><td>Traceability of changes: deployment lifecycle + configuration changes.</td><td><p><code>DEPLOY_STARTED</code></p><p><code>DEPLOY_COMPLETED</code></p><p><code>DEPLOY_FAILED</code></p><p><code>CONFIG_CHANGED</code></p></td><td><p>1. Revision changes are always linked to a release.</p><p>2. Configuration changes are always linked to a release.</p></td></tr><tr><td><strong>Standard</strong></td><td>Adds governance and recoverability evidence: approvals and rollback activity.</td><td><p><code>DEPLOY_STARTED</code></p><p><code>DEPLOY_COMPLETED</code></p><p><code>DEPLOY_FAILED</code></p><p><code>CONFIG_CHANGED</code></p><p><code>CHANGE_APPROVED</code></p><p><code>ROLLBACK_EXECUTED</code></p></td><td><p>1. Revision changes are always linked to a release.</p><p>2. Configuration changes are always linked to a release.</p><p>3. Deployments are always associated with an approval.</p><p>4. Rollbacks are always registered.</p></td></tr><tr><td><strong>Strict</strong></td><td>Adds explicit review evidence (separation of duties) on top of approvals and rollback activity.</td><td><p><code>DEPLOY_STARTED</code></p><p><code>DEPLOY_COMPLETED</code></p><p><code>DEPLOY_FAILED</code></p><p><code>CONFIG_CHANGED</code></p><p><code>CHANGE_APPROVED</code></p><p><code>ROLLBACK_EXECUTED</code></p><p><code>CHANGE_REVIEW_COMPLETED</code></p></td><td><p>1. Revision changes are always linked to a release.</p><p>2. Configuration changes are always linked to a release.</p><p>3. Deployments are always associated with an approval.</p><p>4. Rollbacks are always registered.</p><p>5. Change review (policy check) is always associated with a release.</p></td></tr></tbody></table>


---

# 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://docs.bluestorm.io/checks/governance_control/gov_0001.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.