> 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/readme.md).

# Welcome

The documentation home for YouDesign Command, the ServiceNow-native workspace for portfolio management, enterprise architecture and strategic planning.

YouDesign Command is a ServiceNow-native application for enterprise portfolio management, enterprise architecture and strategic planning. It runs entirely inside your ServiceNow instance and works on the records you already keep there. This page tells you what Command is and where to start reading.

{% hint style="info" %}
**Command is the next chapter of UPMX.** Same product spine, new capability. Existing UPMX customers keep their data, dashboards and configuration, with no forced migration.
{% endhint %}

<figure><img src="https://414746897-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx4mE784snR9Eb8oVrk4e%2Fuploads%2FuGkPwEWj4cofu5tim0bq%2Fproduct-evolution.svg?alt=media&amp;token=0aceaedb-0757-4e83-8fa6-a0fbf3d7884d" alt="UPMX is becoming YouDesign Command, powered by Transformation OS and native to the YouDesign suite"><figcaption></figcaption></figure>

## What it is

Command gives the people who plan and steer change one workspace over live ServiceNow data. You build roadmaps, maps, tables, analyses and dashboards that read the records each time they open, and an AI assistant, the **Command Dialog**, can build and explain them for you.

| Fact          | Detail                                                                                           |
| ------------- | ------------------------------------------------------------------------------------------------ |
| Where it runs | 100% inside your ServiceNow instance. No external integration.                                   |
| What it reads | Your ServiceNow records, with your own ServiceNow permissions.                                   |
| The assistant | Transformation OS™, a language model that runs locally. It does not call an external AI service. |
| Previous name | UPMX. Both names refer to the same evolving application.                                         |

## Start here

| If you want to                             | Read                                                                      |
| ------------------------------------------ | ------------------------------------------------------------------------- |
| Understand Command in five minutes         | [What is YouDesign Command?](/command/getting-started/getting-started.md) |
| Try it for the first time                  | [First steps](/command/getting-started/first-steps.md)                    |
| See every feature at a glance              | [Feature map](/command/getting-started/features.md)                       |
| Answer a real question step by step        | [Use cases](/command/getting-started/use-cases.md)                        |
| Look up how a screen or content type works | [The Portal](/command/the-portal/portal.md)                               |
| Install or upgrade the app                 | [Installation and setup](/command/get-the-app/installation.md)            |

## Good to know for UPMX customers

* **No action required.** Installations, data and configuration carry forward.
* **Technical identifiers keep the UPMX name.** The names inside your instance and the release notes do not change with the rename.
* **Which name to use.** **UPMX** describes what is installed in your instance today. **YouDesign Command** is the product as it is positioned across the YouDesign Enterprise Transformation Suite.

Browser support and the platform architecture are described in [About YouDesign Command](/command/overview/overview.md). The full version history is in the [Release notes](/command/overview/release-notes.md).


---

# 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/readme.md?ask=<question>&goal=<user_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.