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

# Reference

This section provides comprehensive reference documentation for the United Manufacturing Hub (UMH) Core components. Here you'll find detailed technical specifications, configuration options, and structural documentation to help you implement, configure, and troubleshoot your UMH deployment.

The reference materials include:

* **Configuration Reference**: Complete documentation of the central configuration file (`/data/config.yaml`), including all available fields, data types, and examples
* **Container Layout**: Detailed overview of the container's file system structure, data organization, and persistent volume layout
* **Template Variables**: Comprehensive glossary of all available template variables for protocol converter configurations, including connection, location, and system variables
* **State Machines**: Reference documentation for state machine implementations and workflows
* **HTTP API**: GraphQL API reference for Topic Browser queries and programmatic access

Navigate through these pages to find specific configuration parameters, understand system architecture, or look up technical details for your UMH implementation.


---

# 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.umh.app/reference.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.
