> For the complete documentation index, see [llms.txt](https://docs.rainbird.ai/rainbird/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbird.ai/rainbird/knowledge-modelling/publishing-your-km/setting-a-live-version.md). # Setting a live version Publishing a knowledge map is the process of selecting the version that you want to be accessed by default via the Rainbird API. This ensures that any external solutions integrated into the knowledge map will use the correct version by default, and supports continuous improvement as additional changes can be made to the knowledge map without impacting live solutions. Once newer versions have been tested and signed off, the live version can be updated directly from the Studio. ## Publishing a version live To publish a version as live, navigate to the **Publish** tab, select the version to be published and select **Set Live**.

## Enabling interaction history Interaction history provides an alternative form of evidence and reporting on queries to the knowledge map. This can be enabled per version by clicking the **Record Interactions** checkbox. --- # 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.rainbird.ai/rainbird/knowledge-modelling/publishing-your-km/setting-a-live-version.md?ask=&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.