> For the complete documentation index, see [llms.txt](https://infosys.selmotech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-how-it-works/selmo-training/chapter-8-the-new-state-of-the-art/8.5-safety-as-an-inherent-property.md).

# 8.5 Safety as an inherent property

Safety arises in Selmo through structure.\
There are no add-on modules, no special programs.\
Safety logic is built into the architecture.

Every zone knows its state, every signal its meaning.\
Interlock, PairCheck and MXIC form the safety core.\
The HMI is not an add-on, but the visible expression of this logic.

This means Selmo fulfills not only technical but also normative safety principles:\
Traceability, auditability, reproducibility.


---

# 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://infosys.selmotech.com/selmo-solution/selmo-solution-en/selmo-how-it-works/selmo-training/chapter-8-the-new-state-of-the-art/8.5-safety-as-an-inherent-property.md?ask=<question>&goal=<endgoal>
```

`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.
