> For the complete documentation index, see [llms.txt](https://docs.patcher.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patcher.xyz/reference/modular-glossary.md).

# Modular Glossary

This glossary is intentionally short and practical. It focuses on terms that matter while using Patcher.

## Collection

The list of modules you have saved as part of your own workspace. In Patcher, the collection powers racks, patches, and manual shortcuts.

## Digital twin

A practical digital representation of your real modular setup. In Patcher, that means your saved modules, racks, patches, and related context staying connected instead of being spread across separate tools.

## Module

A single hardware unit in a modular system. In Patcher, module pages can include size, manufacturer, power information, panel images, manuals, and related public usage.

## Panel variant

An alternate visual version of the same module. This can matter when you want a rack plan to match the real hardware you actually own.

## Patch

A saved record of a modular setup or signal-routing idea. In Patcher, a patch can include modules, connections, names, and notes for later recall.

## Public profile

A shareable page tied to a user's username. It can show selected public racks and patches, plus profile-related stats.

## Rack

A saved case or layout plan. In Patcher, a rack is not just a picture - it can be edited, rearranged, analyzed, and shared.

## Recall

The ability to reopen an old session and still understand what mattered. This is one of the main reasons to document patches and racks carefully.

## User Area

Your signed-in workspace inside Patcher. It brings together your modules, racks, patches, manuals, comments, and search.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.patcher.xyz/reference/modular-glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.