> 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-selmo-attitude.md). # The Selmo attitude #### ## 1.3 The Selmo Attitude The Selmo attitude is **not a technology decision**\ and **not a tool promise**. It is a **conscious response** to the problems of modern machine logic: implicit logic, lack of traceability and non-tenable responsibility. *** ### Model before code In Selmo the code **is not the starting point**. The code is: * an implementation * a derivation * a result The model, on the other hand, is: * the formal description of behavior * the single source of truth * independent of programming language and platform > **What is not modeled does not exist.** This attitude enforces: * explicit states * clear expectations * defined reactions The code follows the model – not the other way around. *** ### Determinism Selmo assumes that machine behavior **must be unambiguous** at every moment. This means: * the machine is always in a clearly defined state * expectations are explicitly described * reactions to deviations are specified There are: * no implicit transitions * no “good enough” states * no context-dependent interpretation > **Same state + same conditions**\ > **always lead to the same behavior.** Determinism is **not a limitation**,\ but the prerequisite for: * Safety * Automation * Scalability * Analyzability *** ### Responsibility & Transparency As complexity increases, responsibility also increases: * for safety * for availability * for liability * for traceability Selmo consciously accepts this responsibility. Through the formal model it is always traceable: * which state is active * which expectations apply * why a reaction occurs * why a movement is allowed or prevented Transparency does not arise from comments, but from **modeled meaning**. > **What is explainable is verifiable.**\ > **What is verifiable is accountable.** *** ### Consequence of the attitude The Selmo attitude leads to clear consequences: * Machine logic becomes explicit * Diagnosis arises automatically * Documentation is consistent * Changes are controllable * Responsibility is justifiable This attitude is **non-negotiable**, because it forms the foundation of all further concepts. *** ### Transition to the model The Selmo attitude answers the **Why**. The following chapters answer the **How**: * how machines are structured * how behavior is modeled * how operation, safety and diagnosis arise from it > **First the attitude,**\ > **then the 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/1-why-selmo/the-selmo-attitude.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.