> For the complete documentation index, see [llms.txt](https://docs.bierbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bierbot.com/getting-started/terminology.md). # Terminology "**Bricks**" are all physical devices at your site, no matter if a Sonoff TH with one relay and one temperature sensor, an Raspberry PI with several relays and temperature sensors or TILT, iSpindel, Hydrom, Float ... all are "Bricks" offering interfaces/capabilities. An overview over all Bricks is given [here](/hardware/hardware.md). In the BierBot interface you then create "**Equipment**" - to which you then assign the interfaces/ capabilities of your Bricks via drag and drop. So for example a relay from the Raspberry Pi then becomes the heater of your mash tun. A relay of a Sonoff TH the stirrer. Another Sonoff TH can then control the cooling of your fermenter and your TILT contributes the value for the original gravity. The "equipment" has different types (mash tun, fermenter, BIAB) each with different capabilities. A mash tun, for example, has no field for original gravity and only the BIAB device allows you to configure initialization cycles for the pump. You can read more about the various equipment types support [here](/using-bricks/equipment.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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bierbot.com/getting-started/terminology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.