> 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/1-why-selmo/the-fundamental-problem-of-todays-machine-logic.md).

# The fundamental problem of today's machine logic

## 1.2 The core problem of today's machine logic

The central problem of modern machine controls is **not a lack of technology**\
and also **not a lack of programming competence**.

The core problem is that **machine logic today exists predominantly implicitly**.

***

### Implicit logic

In classical controls logic arises:

* distributed across many code locations
* as a combination of conditions, linkages and side effects
* often dependent on order and context

Machine states are:

* not explicitly defined
* not formally described
* only indirectly derivable from the code

This means:

> **The machine “knows” what it is doing –**\
> **but no one can clearly read it off.**

Logic exists, but it is **not visible**.

***

### Code ≠ Documentation

Traditionally it is assumed:

> *“The code is the documentation.”*

In simple systems that may be true.\
In complex machines, however, this assumption leads to a rupture.

Typical symptoms:

* Documentation describes an ideal state
* the code continues to evolve
* deviations are not propagated
* Comments explain *how*, but not *why*

The code shows:

* current signal linkages
* implementation details

It shows **not**:

* which states are intended
* which conditions are mandatory
* what behavior is expected

> **Code describes implementation –**\
> **not meaning.**

***

### Lack of traceability

From implicit logic and lacking formal documentation a fundamental traceability problem arises.

Typical questions are hard to answer:

* What state is the machine currently in?
* Why is it waiting?
* What is missing for the next step?
* Why is a movement being prevented?
* Which condition currently has priority?

Answers to that:

* depend on the person
* require experience or code knowledge
* are often not unambiguous in case of error

This has concrete consequences:

* diagnosis becomes vague
* changes become risky
* safety becomes hard to argue
* responsibility can hardly be demonstrated

***

### The actual deficit

The actual deficit is **not the code**.

The deficit is:

> **the absence of an explicit, formal model**\
> **for the expected machine behavior.**

As long as behavior exists only implicitly:

* it cannot be verified
* it cannot be automatically diagnosed
* it cannot be reliably documented

***

### Transition to the stance

The consequence of this finding is clear:

> machine logic must **visible**,\
> **unambiguously** and\
> **be verifiable** .

This demand is the starting point of the Selmo stance.


---

# 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/1-why-selmo/the-fundamental-problem-of-todays-machine-logic.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.