# Environment drift
**Environment drift** is the difference between two unique environments in a [project](/sleuth-dora/modeling-your-deployments/projects.md), measured in the number of commits and deploys between them as well as the amount of time between the current date and the last commit date for the environment that's lagging.
For example, if you just deployed your staging environment to production, drift will be zero since both environments have the same code. As soon as you make a deploy to your staging environment, Sleuth detects a drift between staging and production as *1 commit and 1 deploy*. An example drift value between *Production* and *Staging* environments could be:*\*\* 1 commit and 3 days\*\**.
Sleuth displays environment drift for individual code deployments within the Code Deployment dashboard, and for Projects with multiple code deployments, it also displays environment drift for each of those code deployments from within the Project Status dashboard.
What's more, when drift is detected, Sleuth also provides visibility into drift details, showing exactly which deploys, PRs, commits, and issues need to be resolved across the two environments.
---
# 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://help.sleuth.io/sleuth-dora/modeling-your-deployments/code-deployments/environment-drift.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.