> 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/9-standards-responsibility-and-future.md). # 9 Standards, responsibility & future ## 9. Standards, Responsibility & Future This chapter describes, **why formal models like Selmo are relevant beyond pure technology**. It's not about citing standards or replacing laws, but about showing: > **How explainable machine behavior**\ > **enables responsibility, traceability and future viability.** *** ### 9.1 Standards as a requirement for traceability Modern standards in mechanical and plant engineering demand not only functioning technology, but **traceable behavior**. They have in common: * Focus on risk analysis * Requirement for justifiable safety assumptions * Proof of measures taken What is crucial here: > **The code is not what's inspected,**\ > **but the argumentation behind the behavior.** *** ### 9.2 The role of formal models Formal models fulfill precisely this requirement. A formal model: * describes states explicitly * defines permitted and forbidden behavior * specifies reactions unambiguously * is independent of implementation details This makes behavior: * explainable * be verifiable * auditable > **A formal model is not an addition to the standard –**\ > **it is the basis for meeting it.** *** ### 9.3 Responsibility through transparency With increasing automation, responsibility grows: * for safety * for availability * for the system's decisions Selmo shifts responsibility: * away from implicit knowledge * toward explicit models Through the model it is always traceable: * why a process stops * why a movement is prevented * why a diagnosis appears > **Transparency is the prerequisite for responsibility.** *** ### 9.4 Liability and demonstrability In case of error, decisive questions are: * What was the expected state? * Which condition applied? * Why did the system react this way? With implicit logic these questions are difficult to answer. With a formal model: * assumptions are documented * decisions are justified * behavior is traceable > **Demonstrability does not arise afterwards,**\ > **but during modeling.** *** ### 9.5 AI, code & responsibility The use of AI in automation will increase: * in code generation * in optimization * in assistance functions This raises a new question: > **Who bears responsibility for generated behavior?** Selmo separates these levels clearly: * AI can generate code * AI can make suggestions * **the model defines the allowed behavior** This means: * AI may implement * AI may optimize * AI may **not** decide what is permitted > **The model limits the AI –**\ > **and makes its use accountable.** *** ### 9.6 Future viability through model clarity Systems that are explainable: * can be extended * can be tested * can be automated * can be accounted for Selmo creates: * a stable foundation for new technologies * a clear boundary between human, model and machine * a robust basis for further development > **The future is not created by more code,**\ > **but by better models.** *** ### Summary Selmo addresses not only technical complexity, but structural requirements of modern automation: * Standards require traceability * Responsibility requires transparency * The future requires clear boundaries for automation and AI > **Selmo is a formal model**\ > **for explainable, accountable machines –**\ > **today and in the future.** --- # 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/9-standards-responsibility-and-future.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.