> 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.7-the-transition-from-theory-to-practice.md).

# 1.7 The transition from theory to practice

In theory, Selmo describes a set of logical states and transitions.\
In practice this means:\
Every real function of a machine is modeled as a zone.\
These zones are controlled by states, and the states are coordinated by the switching logic.

This results in a **formal hierarchy**:

* **process** → determines which states exist.
* **technology** → specifies which hardware zones are required.
* **Function** → describes what each zone must do and report back.

This PTF principle (Process–Technology–Function) is the methodological foundation.\
It ensures that every SEQ arises from real, traceable requirements.\
Thus Selmo is not only a control concept, but also a **design methodology** – a kind of grammar for machine behavior.


---

# 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.7-the-transition-from-theory-to-practice.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.