> For the complete documentation index, see [llms.txt](https://doc.moost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.moost.io/platform-manual/rules/rule-configurator/rule-simulator.md).

# Rule Simulator

The Rule Simulator is a logical component which allows us to simulate changes or new rules based on existing data of existing buildings.

The simulator runs the current rule configuration against the datasets and the time rang which is selected. The notifications which would have been generated and sent to the message queue and eventually to the user are shown as green letters on top.

<figure><img src="https://2791588365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkz3AVy8mukfhOsBy0Lvo%2Fuploads%2Fbk81BprH7PPXd65BK9OI%2Fimage.png?alt=media&amp;token=fc44e458-e109-4676-8662-adaaf825dd96" alt=""><figcaption><p>Datagraph after Simulation run</p></figcaption></figure>

When hovering over the green notification icons, the text is shown, which would have been transmitted to the customer and eventually to the end user. Even placeholders are replaced with the actual text so that logic components within the message can be tested, before a new rule or changes to an existing rule go live.

<figure><img src="https://2791588365-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fkz3AVy8mukfhOsBy0Lvo%2Fuploads%2Flu4BdsMsATJt5ULmVZxR%2Fimage.png?alt=media&amp;token=b626b133-7d56-41ef-b9b7-ef86552972d1" alt=""><figcaption><p>Simulated Notification with replaced placeholders</p></figcaption></figure>


---

# 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://doc.moost.io/platform-manual/rules/rule-configurator/rule-simulator.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.
