> 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-documentation/foreword.md).

# Foreword

### This documentation is normative

This documentation describes **the Selmo system in its binding form**.

“Normative” means in this context:

* The described terms, structures and principles\
  are **authoritative** for the understanding and application of Selmo.
* Divergent interpretations, alternative meanings or implicit assumptions\
  are **not part of Selmo**, unless they are described here.

> **What is described in this documentation applies.**\
> **What is not described is not part of the Selmo system.**

***

### What “normative” means here

This documentation is normative with respect to:

* the **terms** (Plant, Hardware Zone, Sequence, Zone, …)
* the **structure** of the model
* the **meaning** of states, operands and monitors
* the **principles** of operation, safety and diagnostics
* the **attitude**, from which Selmo is applied

It defines:

* **what Selmo is**
* **how Selmo is conceived**
* **how Selmo is correctly interpreted**

***

### What “normative” does not mean here

This documentation is **not a standard in the legal sense**\
and in particular does not replace **no**:

* legal regulations
* harmonized standards (e.g. ISO, IEC)
* risk assessments
* safety proofs
* the professional responsibility of the user

Selmo does not provide **an automatic conformity promise** .

> **Normative clarity does not replace responsibility –**\
> **it makes it comprehensible.**

***

### Relationship to implementation and projects

This documentation describes:

* **the model**
* not its concrete implementation

Project- or customer-specific adaptations:

* may be made
* but must **remain traceable to this model**

If an implementation deviates from this documentation,\
it is not the documentation that is wrong,\
but the deviation **must be explicitly justified and evaluated**.

***

### Changes and further development

This documentation is:

* versionable
* further developable
* traceably extendable

Changes to the Selmo system are made:

* consciously
* explicitly
* documented

Implicit changes or silent shifts in meaning contradict the basic idea of Selmo.

> **Stability does not arise from stagnation,**\
> **but from controlled further development.**

***

### Goal of this foreword

This foreword is intended to ensure that:

* all readers start from the **same understanding of terms** assume
* discussions take place on a **common basis** occur
* misunderstandings are avoided early
* Selmo is understood as what it is: a **formal model for explainable machine behavior**

***

### Concluding statement

Selmo is not a matter of opinion.\
Selmo is a **defined system**.

This documentation is its **reference**.

> **Whoever applies Selmo,**\
> **applies this 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-documentation/foreword.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.