> For the complete documentation index, see [llms.txt](https://guide.crownicles.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.crownicles.com/en/navigate-through-the-wiki.md). # Navigate through the Wiki When reading this wiki, you may encounter tags at the top of the page, here are their meanings * "Old/alpha's bot images" : the page contains images from the test bot or are been taken before the bot's name change. * "Lightly outdated content" : the feature is still pretty the same but a part of the page have received changes/is no longer true. * "Heavily outdated content" : the feature has received significants changes and most of it is false. * "Work in progress" : the page is empty/missing a part of the informations. * "Missing things from fr" : things availables on the french version but not here, could be lesser importance informations or visual improvements. {% hint style="success" %} This wiki is communautary, everyone can make a change request ! (See more in [Writing / Translation of the guide](/en/help-us-to-develop-crownicles/how-to-contribute/writing-translation-of-the-guide.md)) {% endhint %} --- # 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://guide.crownicles.com/en/navigate-through-the-wiki.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.