> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/helm/get-started-with-helm/helm-terminology.md).

# Helm terminology

* **Dependency:** This is what may be referred to as a component in other systems. It is the firmware, software, patches, or operating system that is installed on the physical representations of your device (e.g., Windows, OpenSSL). In this help center, it is referred to as a component.\
  \
  **Note:** We are in the process of moving from using the term, dependency, to component in our UI (and therefore, docs), thus you will see these terms used interchangeably during this transition. Currently, both of these terms refer to the same thing.
* **Component:** Currently this means the same as dependency. See note above.
* **Version:** This is the component’s version (e.g., 10.1 for Windows).
* **Supplier:** This is the component’s version (e.g., 10.1 for Windows).
* **Badges:** These are used like tags. They may also be referred to as chips.
  * In the editable state, they include an x to remove them.
  * Depending on the use case, some chip states can only be removed by unchecking the drop-down options.
* **Panels:** Panels refer to panels that slide-out from the right of the main page. You can close a panel to return to the main (or parent) page from which it was launched.


---

# 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.medcrypt.com/medcrypt-documentation/helm/get-started-with-helm/helm-terminology.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.