> 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-7-why-selmo-always-works/7.3-the-formal-framework-cause-and-effect.md).
# 7.3 The formal framework β cause and effect
The basic principle of every SEQ is:
\
**Every action must have feedback.**
\
This rule is universal β whether for cylinders, motors, calculations or sensors.
Without feedback the system does not know whether an action was actually executed.\
A timer can wait, but cannot confirm.\
Only feedback can do that.
Therefore every zone in the Selmo standard is structured\
so that it links action and feedback in a logical unit.\
If you follow this principle, Selmo always works.
𧩠1. Dialectical classification of the term βfunctionβ
#### **Thesis**
A function is the goal-directed effect of a system or subsystem that fulfills a defined purpose.
β A function **connects cause and effect** within a system.\
It is what *becomes effective*once certain conditions are met.
#### **Antithesis**
Function is not the physical component (mechanics, electrical, software),\
but the **principle of action**that is realized by these components.
* The mechanics provide the force,
* the electrical system the energy,
* the control the condition,
* but **the function is the meaning of the operation** β what is achieved.
Example:
> A cylinder extends to clamp.\
> β The **cylinder** is technology.\
> β The **extension** is behavior.\
> β That **clamp** is function.
#### **Synthesis**
Function is the **βwhyβ of a technical action**, not the βhowβ.\
It is **goal-directed, purpose-oriented and reusable**.\
In the Selmo context it is **formalized**, i.e. converted into a clearly describable, measurable and controllable definition.
π 6. Conclusion: Definition in the Selmo context
> **Function** in the Selmo context is a **formally described, reusable, deterministic operation**,\
> that fulfills a **clear purpose** and is embedded in the sequence via **defined interfaces, parameters and monitoring** .
It can:
* act physically (mechanics, electrical, pneumatic),
* act informatically (calculation, communication, control),
* or act systemically (monitoring, diagnosis, synchronization) β\
but always within a **defined state and process model**.
---
# 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-7-why-selmo-always-works/7.3-the-formal-framework-cause-and-effect.md?ask=&goal=
```
`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.