> For the complete documentation index, see [llms.txt](https://docs.chirpwireless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chirpwireless.io/rules-engine/reference.md). # Reference The tutorials walk you through building automations step by step. This section is for when you need to look something up — how a specific node works, what a CEL expression does, or what a build error means. ## What you will find here * [Rules Page and Tabs](/rules-engine/reference/rules-page-and-tabs.md) — The main Rules hub: your automations list, built artifacts, and trash * [Visual Editor](/rules-engine/reference/visual-editor.md) — The canvas, node palette, properties sidebar, and editor controls * [Automation Node Guide](/rules-engine/reference/automation-node-guide.md) — Every node type explained: what it does, what fields it has, and how it behaves * [CEL for Home Automations](/rules-engine/reference/cel-for-home-automations.md) — The expression language that powers your conditions, calculations, and alarm messages * [Fixing Builds and Runtime Stops](/rules-engine/reference/fixing-builds-and-runtime-stops.md) — What to do when a build fails, how deployment works, and how to recover from a force-stop --- # 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.chirpwireless.io/rules-engine/reference.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.