> 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.2-thinking-in-states.md).

# 1.2 Thinking in states

One **State** is a clearly defined moment in the process – a slice of logical time.\
For example:

* The cylinder is retracted.
* The operator presses Start.
* The computation is running.
* The machine is waiting for feedback.

In each state the actions, monitors and reactions are unambiguously defined.\
The machine can **be in only one state at a time** .\
As soon as the conditions to advance are met, it leaves that state and transitions to the next.

That sounds simple, but it has far-reaching consequences:\
Such a process is **deterministic** – that means its behavior is predictable and mathematically describable.\
There are no coincidences, no hidden dependencies and no uncontrolled side effects.\
Every movement, every step has a defined cause and a verifiable effect.


---

# 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.2-thinking-in-states.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.