> 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/engineering-through-the-ages/future-outlook-the-third-language-of-engineering.md).

# Future outlook – The third language of engineering

Today there are two recognized languages of engineering:

* **Drawing** (Mechanics)
* **Circuit diagram** (Electrical engineering)

Tomorrow Selmo will add them as a third language:

* **Selmo model** (Logic)

This means:

* Machine behavior will be standardized just like shape and circuit.
* AI can be used safely and traceably.
* Trust, legal certainty and responsibility are firmly anchored.

👉 **Selmo changes programming** – and becomes the third pillar alongside drawing and circuit diagram.

#### Historical development

* Drawing → since antiquity, standardized in the 19th/20th century.
* Circuit diagram → since the 19th century, standardized in the 20th century.
* PLC → since 1968, logic inconsistent
* **Selmo** → from today: logic standardized, formal and transparent

👉 Future: machine logic will be documented as matter-of-course as mechanics and electrical systems.


---

# 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/engineering-through-the-ages/future-outlook-the-third-language-of-engineering.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.