> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/techniques/environment-management/guiding-principles.md).
# Guiding Principles
Environment Management in flxbl project follow guidelines as laid out by the [Salesforce Well Architected ](https://architect.salesforce.com/well-architected/adaptable/resilient)guide, Rehashing some of the most important principles here
* **Release stages apply to release artifacts, not environments**.
* ***Every***** development environment should be refreshed or destroyed as soon as the relevant work is finished (within limits)**.
* **Environments are only as useful as the kind of production fidelity they do (and do not) provide. Optimize your environment setup workflows or automations to allow for environment teardown/refresh at the earliest possible interval**.
In order to cater the above requirements, flxbl projects work with the concept of environment categories, any number of sandboxes can be added to any of these categories. These environment categories form the deployment target in your pipelines.
Test Environments
In addition to the above categories, flxbl project utilize three categories of development environments
Development Environments
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.flxbl.io/flxbl/techniques/environment-management/guiding-principles.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.