> 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-1-the-theoretical-background/1.6-why-this-structure-is-so-powerful.md).

# 1.6 Why this structure is so powerful

This structure makes Selmo a **domain-specific language** for machine behavior.\
Every component — whether physical or logical — is embedded in a defined context.\
This has several advantages:

1. **Transparency:**\
   Anyone can instantly see which state is active, which zone is waiting, and why.
2. **Reusability:**\
   Zones and procedures are standardized.\
   They can be reused across projects without being reprogrammed.
3. **Safety:**\
   Every movement is secured by its feedback.\
   Error states are detected automatically (interlock, pair check).
4. **Automatic documentation:**\
   The model itself is the documentation.\
   States, zones, texts, feedbacks — everything is traceable.


---

# 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-1-the-theoretical-background/1.6-why-this-structure-is-so-powerful.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.