> 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-how-it-works/selmo-training/kapitel-7-warum-selmo-immer-funktioniert/7.1-der-haufigste-irrtum.md).

# 7.1 Der häufigste Irrtum

Viele Ingenieure, die zum ersten Mal mit Selmo in Berührung kommen, denken:\
„Das klingt gut, aber meine Maschine ist zu komplex“ oder\
„Ich habe Spezialfunktionen, das kann Selmo nicht.“

Diese Reaktion ist verständlich, denn man betrachtet Selmo oft noch mit der Brille der klassischen SPS-Logik:\
„Wie programmiere ich das?“\
Selmo stellt aber eine andere Frage:\
„Wie *verhält* sich das System?“

Die meisten Schwierigkeiten entstehen also nicht, weil Selmo etwas nicht kann,\
sondern weil man die Aufgabe noch nicht **formal beschrieben** hat.


---

# 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-how-it-works/selmo-training/kapitel-7-warum-selmo-immer-funktioniert/7.1-der-haufigste-irrtum.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.