> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/command/overview.md). # Overview - [About YouDesign Command](https://docs.ins-pi.com/command/overview/overview.md): What YouDesign Command is as a product, how it sits inside ServiceNow, and which browsers it supports. - [Architecture](https://docs.ins-pi.com/command/overview/architecture.md): How YouDesign Command is built as a native ServiceNow application with a browser portal, an in-browser assistant and one shared data model. - [Product Roadmap](https://docs.ins-pi.com/command/overview/roadmap.md): Which YouDesign Command versions are current, supported or retired, and what the current and next releases focus on. - [Release Notes](https://docs.ins-pi.com/command/overview/release-notes.md): What changed in each YouDesign Command release, newest first, from version 26.1 back to version 2.0. - [Calculations](https://docs.ins-pi.com/command/overview/calculations.md): The calculated indicators YouDesign Command keeps on portfolio elements, what each one tells you, and where newer Measures and Scoring take over. - [Lifecycle Stages & Phases](https://docs.ins-pi.com/command/overview/lifecycle-stages-phases.md): The lifecycle stages, phases and lifecycle types YouDesign Command uses to describe an element from its first idea to its retirement. --- # 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.ins-pi.com/command/overview.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.