From 2475433e065988b1f7a1945b8450998264e4f193 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Arkadiusz=20J=C4=99drzejewski?=
 <arkadiusz.jedrzejewski.ext@qorix.ai>
Date: Thu, 20 Nov 2025 10:04:51 +0000
Subject: [PATCH] docs: initial docs from template

Adapted docs from template.
---
 docs/index.rst                                |  19 +-
 docs/module/log/architecture/index.rst        |  97 +++++
 docs/module/log/component_classification.rst  | 188 ++++++++++
 docs/module/log/detailed_design/index.rst     |  72 ++++
 docs/module/log/index.rst                     | 164 +++++++++
 docs/module/log/requirements/index.rst        |  35 ++
 docs/module/log/safety_analysis/dfa.rst       |  51 +++
 docs/module/log/safety_analysis/fmea.rst      |  51 +++
 docs/module_docs/index.rst                    |  27 ++
 docs/module_docs/manual/index.rst             |  21 ++
 docs/module_docs/manual/safety_manual.rst     |  90 +++++
 docs/module_docs/release/release_note.rst     |  92 +++++
 docs/module_docs/safety_mgt/index.rst         |  23 ++
 .../safety_mgt/module_safety_package_fdr.rst  |  63 ++++
 .../safety_mgt/module_safety_plan.rst         | 340 ++++++++++++++++++
 .../safety_mgt/module_safety_plan_fdr.rst     |  93 +++++
 .../module_verification_report.rst            |  81 +++++
 17 files changed, 1496 insertions(+), 11 deletions(-)
 create mode 100644 docs/module/log/architecture/index.rst
 create mode 100644 docs/module/log/component_classification.rst
 create mode 100644 docs/module/log/detailed_design/index.rst
 create mode 100644 docs/module/log/index.rst
 create mode 100644 docs/module/log/requirements/index.rst
 create mode 100644 docs/module/log/safety_analysis/dfa.rst
 create mode 100644 docs/module/log/safety_analysis/fmea.rst
 create mode 100644 docs/module_docs/index.rst
 create mode 100644 docs/module_docs/manual/index.rst
 create mode 100644 docs/module_docs/manual/safety_manual.rst
 create mode 100644 docs/module_docs/release/release_note.rst
 create mode 100644 docs/module_docs/safety_mgt/index.rst
 create mode 100644 docs/module_docs/safety_mgt/module_safety_package_fdr.rst
 create mode 100644 docs/module_docs/safety_mgt/module_safety_plan.rst
 create mode 100644 docs/module_docs/safety_mgt/module_safety_plan_fdr.rst
 create mode 100644 docs/module_docs/verification/module_verification_report.rst

diff --git a/docs/index.rst b/docs/index.rst
index 54a223a..e80e2eb 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -12,25 +12,22 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
-Base Libraries - Rust
-=============================
+Rust Base Libraries
+===================
 
-This documentation describes the Rust base libraries.
+.. toctree::
+   :maxdepth: 1
+   :glob:
+   :titlesonly:
 
-.. contents:: Table of Contents
-   :depth: 2
-   :local:
+   module_docs/index
+   module/*/index
 
 Overview
 --------
 
 Foundational Rust libraries providing common functionality for S-CORE modules.
 
-Requirements
-------------
-
-- TODO: add requirements once available.
-
 Project Layout
 --------------
 
diff --git a/docs/module/log/architecture/index.rst b/docs/module/log/architecture/index.rst
new file mode 100644
index 0000000..4b4fe2e
--- /dev/null
+++ b/docs/module/log/architecture/index.rst
@@ -0,0 +1,97 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _component_architecture_log:
+
+Component Architecture
+======================
+
+.. document:: Log Architecture
+   :id: doc__log_architecture
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__component_arch
+   :tags: log
+
+
+Overview
+--------
+
+Document describes Log component architecture.
+
+
+Description
+-----------
+
+TODO: description
+
+
+Rationale Behind Architecture Decomposition
+*******************************************
+
+TODO: decomposition rationale
+
+Static Architecture
+-------------------
+
+TODO: static architecture
+
+.. .. comp_arc_sta:: Log (Static View)
+..    :id: comp_arc_sta__log__static_view
+..    :security: YES
+..    :safety: QM
+..    :status: invalid
+..    :implements: logic_arc_int__log__interface_name
+..    :fulfils:
+..    :includes:
+
+..    .. uml:: _assets/TODO.puml
+
+
+Dynamic Architecture
+--------------------
+
+TODO: dynamic architecture
+
+.. .. comp_arc_dyn:: Dynamic View
+..    :id: comp_arc_dyn__log__dynamic_view
+..    :security: YES
+..    :safety: QM
+..    :status: invalid
+..    :fulfils: comp_req__log__some_title
+
+.. .. uml:: _assets/TODO.puml
+
+
+Interfaces
+----------
+
+TODO: put log interfaces.
+
+.. .. code-block:: rst
+
+..    .. real_arc_int:: mw_log
+..       :id: real_arc_int__log__interface
+..       :security: NO
+..       :safety: QM
+..       :fulfils:
+..       :language: rust
+
+..    .. uml:: _assets/TODO.puml
+
+Lower Level Components
+----------------------
+
+TODO: remove section if unused
diff --git a/docs/module/log/component_classification.rst b/docs/module/log/component_classification.rst
new file mode 100644
index 0000000..4580133
--- /dev/null
+++ b/docs/module/log/component_classification.rst
@@ -0,0 +1,188 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Component Classification
+========================
+
+
+.. document:: Log Component Classification
+   :id: doc__log_comp_class
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__sw_component_class
+   :tags: log
+
+
+| Classification of <component>
+|
+| <Link to OSS component source (e.g. in github) including the selected version>
+|
+| Additional documentation considered:
+| <list of documentation links>
+
+
+Step 1: Determine (P): the uncertainty of the Processes applied
+---------------------------------------------------------------
+
+| Apply the process measures to determine (P).
+| The result of a process measure shall have as outcome [HE, PE, NE]
+| - HE: High Evidence
+| - PE: Partly Evidence but Manageable
+| - NE: No Evidence
+
+.. list-table:: Determine (P)
+        :header-rows: 1
+
+        * - Id
+          - Indicator for applying process
+          - Result
+          - Rationale for result
+
+        * - 1
+          - Are rules, state-of-the art processes applied for the design, implementation and verification?
+          - <HE|PE|NE>
+          - <Rationale for result>
+
+        * - 2
+          - Are requirements available?
+          - <HE|PE|NE>
+          - <Rationale for result>
+
+        * - 3
+          - Are specifications for functionalities and properties available (architecture)?
+          - <HE|PE|NE>
+          - <Rationale for result>
+
+        * - 4
+          - Are design specifications available?
+          - <HE|PE|NE>
+          - <Rationale for result>
+
+        * - 5
+          - Are configuration specification and data available, if applicable?
+          - <HE|PE|NE>
+          - <Rationale for result>
+
+        * - 6
+          - Are verification measures including tests and reports available?
+          - <HE|PE|NE>
+          - <Rationale for result>
+
+
+| (P=1) shall be selected when none of the determined process measures indicate PE or NE.
+| (P=2) shall be selected when at least one of the determined process measures indicate PE or NE, but the gaps evaluated are acceptable, means
+|       the risk of systematic faults due to these gaps is sufficiently low or manageable by mitigating the gaps.
+| (P=3) in all other cases.
+
+<component name> is determined as P=<1|2|3>
+
+
+Step 2: Determine (C): the uncertainty of finding systematic faults based on the Complexity
+-------------------------------------------------------------------------------------------
+
+| Apply the complexity measures to determine (C).
+| The result of a complexity measure shall have as outcome [NH, HM, NM]
+| - NH: Not High
+| - HM: High but Manageable
+| - NM: high and Not Manageable
+|
+| **Complexity measure for programming language: <C++ or RUST>**
+
+<select the correct table below (table for C++ is TBD)>
+
+.. list-table:: Determine (C) for RUST
+    :header-rows: 1
+
+    * - Id
+      - Indicator for high Complexity
+      - Complexity measure Tool
+      - Result
+      - Number
+
+    * - 1
+      - High amount of Lines of Code
+      - Lines of Code (without comments) (generated code is excluded, e.g. ProtoCmpl)
+      - <NH|HM|NM>
+      - <Number>
+
+    * - 2
+      - Unsafe code used / total unsafe code
+      - Count:
+            * LoUC+N: lines of unsafe code with safety note
+            * LoUC  : lines of unsafe code, no safety note
+      - <NH|HM|NM>
+      - <Number>
+
+    * - 3
+      - | Test exists / Coverage (Function, Line)
+        | (maybe better: testability, but how to measure?)
+      - Existing Tests Coverage
+      - <NH|HM|NM>
+      - <Number>
+
+    * - 4
+      - High amount of public function interfaces
+      - Number of public function interfaces
+      - <NH|HM|NM>
+      - <RNumber>
+
+    * - 5
+      - High amount of function parameters
+      - Number of parameters
+      - <NH|HM|NM>
+      - <Number>
+
+
+| (C=1) shall be selected when none of the determined complexity measures indicate HM or NM.
+| (C=2) shall be selected when at least one of the determined complexity measures indicate HM or NM, but the gaps evaluated are acceptable, means
+|       the risk of systematic faults due to these gaps is sufficiently low in the context of the project or manageable by mitigating the gaps.
+| (C=3) in all other cases.
+|
+
+<component name> is determined as C=<1|2|3>
+
+
+Step 3: Determine (CLAS_OUT): the classification outcome
+--------------------------------------------------------
+
+| Select CLAS_OUT depending on the determined values of (C) and (P)
+
++-------+-----------------------+
+| ( C ) | ( P )                 |
++-------+-------+-------+-------+
+|       |  1    |  2    |  3    |
++=======+=======+=======+=======+
+| 1     |  Q    |  Q    | QR    |
++-------+-------+-------+-------+
+| 2     |  QR   | QR    | QR    |
++-------+-------+-------+-------+
+| 3     |  QR   | QR    | NQ    |
++-------+-------+-------+-------+
+
+<component name> is classified as CLAS_OUT=<Q|QR|NQ>
+
+
+Step 4: Document all results and rationale for choosing (P) and (C) and (CLAS_OUT)
+----------------------------------------------------------------------------------
+This document
+
+
+Step 5: Based on (CLAS_OUT) select the activities
+-------------------------------------------------
+
+| As soon as the change request containing this is in status "Accepted", the module safety plan for the component development is adapted based on the following: (select according to above result)
+| - Q: Follow the processes for qualification of software components in a safety context.
+| - QR: Follow the process for pre-existing software architectural elements
+| - NQ: Do no use this element in safety context
diff --git a/docs/module/log/detailed_design/index.rst b/docs/module/log/detailed_design/index.rst
new file mode 100644
index 0000000..63b16a9
--- /dev/null
+++ b/docs/module/log/detailed_design/index.rst
@@ -0,0 +1,72 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _component_detailed_design_log:
+
+Detailed Design
+###############
+
+.. document:: Log Detailed Design
+   :id: doc__log_detailed_design
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__sw_implementation
+   :tags: log
+
+
+Detailed Design for Component: Log
+==================================
+
+Description
+-----------
+
+| Design Decisions - For the documentation of the decision the :need:`gd_temp__change_decision_record` can be used.
+| Design Constraints
+
+Rationale Behind Decomposition into Units
+******************************************
+| mandatory: a motivation for the decomposition into one or more units.
+
+.. note:: Reason for split into multiple units could be-
+	    - Based on design principles like SOLID,DRY etc
+	    - Based on design pattern's etc.
+
+Static Diagrams for Unit Interactions
+-------------------------------------
+.. code-block:: rst
+
+   .. dd_sta:: <Title>
+      :id: dd_sta__<Feature>__<Title>
+      :security: <YES|NO>
+      :safety: QM
+      :status: <valid|invalid>
+      :implements: <link to component requirement id>
+      :satisfies: <link to component architecture id>
+
+        .. image:: <link to drawio image> or .. uml:: <link to plantuml>
+
+Dynamic Diagrams for Unit Interactions
+--------------------------------------
+.. code-block:: rst
+
+   .. dd_dyn:: <Title>
+      :id: dd_dyn__<Feature>__<Title>
+      :security: <YES|NO>
+      :safety: QM
+      :status: <valid|invalid>
+      :implements: <link to component requirement id>
+      :satisfies: <link to component architecture id>
+
+        .. image:: <link to drawio image> or .. uml:: <link to plantuml>
diff --git a/docs/module/log/index.rst b/docs/module/log/index.rst
new file mode 100644
index 0000000..07cd811
--- /dev/null
+++ b/docs/module/log/index.rst
@@ -0,0 +1,164 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _component_log:
+
+Log
+###
+
+
+.. document:: Log
+   :id: doc__log
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__cmpt_request
+   :tags: log
+
+
+Abstract
+========
+
+Log component provides a logging API.
+
+
+Motivation
+==========
+
+TODO: motivation
+
+
+
+Rationale
+=========
+
+TODO: rationale
+
+
+Specification
+=============
+
+[Describe the requirements, architecture of any new component.] or
+[Describe the change to requirements, architecture, implementation, documentation of any change request.]
+
+   .. note::
+      A CR shall specify the component requirements as part of our platform/project.
+      Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR).
+
+
+
+Backwards Compatibility
+=======================
+
+[Describe potential impact (especially including safety and security impacts) and severity on pre-existing platform/project elements.]
+
+
+Security Impact
+===============
+
+[How could a malicious user take advantage of this new/modified component?]
+
+   .. note::
+      If there are security concerns in relation to the CR, those concerns should be explicitly written out to make sure reviewers of the CR are aware of them.
+
+Which security requirements are affected or has to be changed?
+Could the new/modified component enable new threat scenarios?
+Could the new/modified component enable new attack paths?
+Could the new/modified component impact functional safety?
+If applicable, which additional security measures must be implemented to mitigate the risk?
+
+    .. note::
+     Use Security Software Critically Analysis, Vulnerability Analysis.
+     [Methods will be defined later in Process area Security Analysis]
+
+
+Safety Impact
+=============
+
+[How could the safety be impacted by the new/modified component?]
+
+   .. note::
+      If there are safety concerns in relation to the CR, those concerns should be explicitly written out to make sure reviewers of the CR are aware of them.
+
+Which safety requirements are affected or has to be changed?
+Could the new/modified component be a potential common cause or cascading failure initiator?
+If applicable, which additional safety measures must be implemented to mitigate the risk?
+
+    .. note::
+     Use Dependency Failure Analysis and/or Safety Software Critically Analysis.
+     [Methods will be defined later in Process area Safety Analysis]
+
+For new feature/component contributions:
+
+[What is the expected ASIL level?]
+[What is the expected classification of the contribution?]
+
+   .. note::
+      Use the component classification method here to classify your component, if it shall to be used in a safety context: :need:`gd_temp__component_classification`.
+
+License Impact
+==============
+
+[How could the copyright impacted by the license of the new contribution?]
+
+
+How to Teach This
+=================
+
+[How to teach users, new and experienced, how to apply the CR to their work.]
+
+   .. note::
+      For a CR that adds new functionality or changes behavior, it is helpful to include a section on how to teach users, new and experienced, how to apply the CR to their work.
+
+
+
+Rejected Ideas
+==============
+
+[Why certain ideas that were brought while discussing this CR were not ultimately pursued.]
+
+   .. note::
+      Throughout the discussion of a CR, various ideas will be proposed which are not accepted.
+      Those rejected ideas should be recorded along with the reasoning as to why they were rejected.
+      This both helps record the thought process behind the final version of the CR as well as preventing people from bringing up the same rejected idea again in subsequent discussions.
+      In a way this section can be thought of as a breakout section of the Rationale section that is focused specifically on why certain ideas were not ultimately pursued.
+
+
+
+Open Issues
+===========
+
+[Any points that are still being decided/discussed.]
+
+   .. note::
+       While a CR is in draft, ideas can come up which warrant further discussion.
+       Those ideas should be recorded so people know that they are being thought about but do not have a concrete resolution.
+       This helps make sure all issues required for the CR to be ready for consideration are complete and reduces people duplicating prior discussion.
+
+
+
+Footnotes
+=========
+
+[A collection of footnotes cited in the CR, and a place to list non-inline hyperlink targets.]
+
+.. toctree::
+   :hidden:
+
+   requirements/index.rst
+   architecture/index.rst
+   detailed_design/index.rst
+   safety_analysis/fmea.rst
+   safety_analysis/dfa.rst
+   component_classification.rst
diff --git a/docs/module/log/requirements/index.rst b/docs/module/log/requirements/index.rst
new file mode 100644
index 0000000..eb1c055
--- /dev/null
+++ b/docs/module/log/requirements/index.rst
@@ -0,0 +1,35 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _component_log_requirements:
+
+Requirements
+############
+
+.. document:: Log Requirements
+   :id: doc__log_requirements
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__requirements_comp
+   :tags: log
+
+.. needextend:: "log" in id
+   :+tags: log
+
+
+.. _component_log_requirements_aou:
+
+AoU Requirements
+################
diff --git a/docs/module/log/safety_analysis/dfa.rst b/docs/module/log/safety_analysis/dfa.rst
new file mode 100644
index 0000000..e13a24c
--- /dev/null
+++ b/docs/module/log/safety_analysis/dfa.rst
@@ -0,0 +1,51 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+
+DFA (Dependent Failure Analysis)
+================================
+
+.. document:: Log DFA
+   :id: doc__log_dfa
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__sw_component_dfa
+   :tags: log
+
+.. note:: Use the content of the document to describe e.g. why a fault model is not applicable for the diagram.
+
+
+Dependent Failure Initiators
+----------------------------
+
+.. code-block:: rst
+
+    .. comp_saf_dfa:: <Title>
+       :violates: <Component architecture>
+       :id: comp_saf_dfa__<Component>__<Element descriptor>
+       :failure_id: <ID from DFA failure initiators :need:`gd_guidl__dfa_failure_initiators`>
+       :failure_effect: "description of failure effect of the failure initiator on the element"
+       :mitigated_by: <ID from Component Requirement | ID from AoU Component Requirement>
+       :mitigation_issue: <ID from Issue Tracker>
+       :sufficient: <yes|no>
+       :status: <valid|invalid>
+
+.. note::   argument is inside the 'content'. Therefore content is mandatory
+
+.. attention::
+    The above directive must be updated according to your component DFA.
+
+    - The above "code-block" directive must be updated
+    - Fill in all the needed information in the <brackets>
diff --git a/docs/module/log/safety_analysis/fmea.rst b/docs/module/log/safety_analysis/fmea.rst
new file mode 100644
index 0000000..1acb07c
--- /dev/null
+++ b/docs/module/log/safety_analysis/fmea.rst
@@ -0,0 +1,51 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+
+FMEA (Failure Modes and Effects Analysis)
+=========================================
+
+.. document:: Log FMEA
+   :id: doc__log_fmea
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__sw_component_fmea
+   :tags: log
+
+.. note:: Use the content of the document to describe e.g. why a fault model is not applicable for the diagram.
+
+
+Failure Mode List
+-----------------
+
+.. code-block:: rst
+
+    .. comp_saf_fmea:: <Title>
+       :violates: <Component architecture>
+       :id: comp_saf_fmea__<Component>__<Element descriptor>
+       :fault_id: <ID from fault model :need:`gd_guidl__fault_models`>
+       :failure_effect: "description of failure effect of the fault model on the element"
+       :mitigated_by: <ID from Component Requirement | ID from AoU Component Requirement>
+       :mitigation_issue: <ID from Issue Tracker>
+       :sufficient: <yes|no>
+       :status: <valid|invalid>
+
+.. note::   argument is inside the 'content'. Therefore content is mandatory
+
+.. attention::
+    The above directive must be updated according to your component FMEA.
+
+    - The above "code-block" directive must be updated
+    - Fill in all the needed information in the <brackets>
diff --git a/docs/module_docs/index.rst b/docs/module_docs/index.rst
new file mode 100644
index 0000000..efc28da
--- /dev/null
+++ b/docs/module_docs/index.rst
@@ -0,0 +1,27 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+.. _module_documentation:
+
+Module Documents
+################
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   manual/index.rst
+   safety_mgt/index.rst
+   verification/module_verification_report.rst
+   release/release_note.rst
diff --git a/docs/module_docs/manual/index.rst b/docs/module_docs/manual/index.rst
new file mode 100644
index 0000000..08ba1a6
--- /dev/null
+++ b/docs/module_docs/manual/index.rst
@@ -0,0 +1,21 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2024 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Manuals
+#######
+
+.. toctree::
+   :titlesonly:
+
+   safety_manual
diff --git a/docs/module_docs/manual/safety_manual.rst b/docs/module_docs/manual/safety_manual.rst
new file mode 100644
index 0000000..2d9f90b
--- /dev/null
+++ b/docs/module_docs/manual/safety_manual.rst
@@ -0,0 +1,90 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Safety Manual
+=============
+
+.. document:: Rust Base Libraries Safety Manual
+   :id: doc__baselibs_rust_safety_manual
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__module_safety_manual
+   :tags: baselibs_rust
+
+Introduction/Scope
+------------------
+| This manual covers Rust Base Libraries module.
+
+Assumed Platform Safety Requirements
+------------------------------------
+| For the Rust Base Libraries the following safety related stakeholder requirements are assumed to define the top level functionality (purpose) of the Rust Base Libraries.
+| I.e. from these all the feature and component requirements implemented are derived.
+| <List here all the stakeholder requirements, with safety not equal to QM, the module's components requirements are derived from.>
+
+Assumptions of Use
+------------------
+
+Assumptions on the Environment
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+| Generally the assumption of the project platform SEooC is that it is integrated in a safe system, i.e. the POSIX OS it runs on is qualified and also the HW related failures are taken into account by the system integrator, if not otherwise stated in the module's safety concept.
+| <List here all the OS calls the project platform expects to be safe.>
+
+List of AoUs expected from the environment the module runs on:
+
+.. needtable::
+   :style: table
+   :columns: title;id;status
+   :colwidths: 25,25,25
+   :sort: title
+
+   results = []
+
+   for need in needs.filter_types(["aou_req"]):
+      if need and "environment" in need["tags"]:
+                results.append(need)
+
+Assumptions on the User
+^^^^^^^^^^^^^^^^^^^^^^^
+| As there is no assumption on which specific OS and HW is used, the integration testing of the stakeholder and feature requirements is expected to be performed by the user of the platform SEooC. Tests covering all stakeholder and feature requirements performed on a reference platform (tbd link to reference platform specification), reviewed and passed are included in the platform SEooC safety case.
+| Additionally the components of the platform may have additional specific assumptions how they are used. These are part of every module documentation: :ref:`module_documentation`. Assumptions from components to their users can be fulfilled in two ways:
+| 1. There are assumption which need to be fulfilled by all SW components, e.g. "every user of an IPC mechanism needs to make sure that he provides correct data (including appropriate ASIL level)" - in this case the AoU is marked as "platform".
+| 2. There are assumption which can be fulfilled by a safety mechanism realized by some other project platform component and are therefore not relevant for an user who uses the whole platform. But those are relevant if you chose to use the module SEooC stand-alone - in this case the AoU is marked as "module". An example would be the "JSON read" which requires "The user shall provide a string as input which is not corrupted due to HW or QM SW errors." - which is covered when using together with safe project platform persistency feature.
+
+List of AoUs on the user of the platform features or the module of this safety manual:
+
+.. needtable::
+   :style: table
+   :columns: title;id;status
+   :colwidths: 25,25,25
+   :sort: title
+
+   results = []
+
+   for need in needs.filter_types(["aou_req"]):
+      if need and "environment" not in need["tags"]:
+                results.append(need)
+
+Safety concept of the SEooC
+---------------------------
+| <Describe here the safety concept incl. which faults are taken care of, reactions of the implemented functions under anomalous operating conditions ... if this is not already documented sufficiently in the feature documentation "safety impact" section of all the features the module is used in.>
+
+Safety Anomalies
+----------------
+| Anomalies (bugs in ASIL SW, detected by testing or by users, which could not be fixed) known before release are documented in the platform/module release notes <add link to release note>.
+
+References
+----------
+| <link to the user manual>
+| <other links>
diff --git a/docs/module_docs/release/release_note.rst b/docs/module_docs/release/release_note.rst
new file mode 100644
index 0000000..b225a36
--- /dev/null
+++ b/docs/module_docs/release/release_note.rst
@@ -0,0 +1,92 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Release Note
+============
+
+.. document:: Rust Base Libraries Release Note
+   :id: doc__baselibs_rust_release_note
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__module_sw_release_note
+   :tags: baselibs_rust
+
+| Module Name: Rust Base Libraries
+| Release Tag: vX.Y.Z
+| Origin Release Tag: vU.V.W
+| Release Commit Hash: a1b2c3d4e5f6g7h8i9j0
+| Release Date: YYYY-MM-DD
+|
+| Overview
+| --------
+|
+| This document provides an overview of the changes, improvements, and bug fixes included in the software module release version vX.Y.Z
+|  as compared to the module's origin release (which is usually the previous release).
+|
+|  Disclaimer
+|  ----------
+|  This release note does not "release for production", as it does not come with a safety argumentation and a performed safety assessment.
+|  The work products compiled in the safety package are created with care according to a process satisfying standards, but the as the project,
+|  being a non-profit and open source organization, can not take over any liability for its content.
+|
+| New Features
+| ------------
+|
+| - **Feature 1**: Brief description of the new feature.
+| - **Feature 2**: Brief description of the new feature.
+| - **Feature 3**: Brief description of the new feature.
+|
+| Improvements
+| ------------
+|
+| - **Improvement 1**: Brief description of the improvement.
+| - **Improvement 2**: Brief description of the improvement.
+| - **Improvement 3**: Brief description of the improvement.
+|
+| Bug Fixes
+| ---------
+|
+| - **Bug 1**: Brief description of the bug fix.
+| - **Bug 2**: Brief description of the bug fix.
+| - **Bug 3**: Brief description of the bug fix.
+|
+| Compatibility
+| -------------
+|
+| - **Dependencies**: List any dependencies and their versions.
+|
+|  Performed Verification
+|  ----------------------
+|  This release note is based on the verification as documented in module verification report
+|  :need:`doc__baselibs_rust_verification_report`.
+|
+| Known Issues
+| ------------
+|
+| - **Issue 1**: Brief description of the known issue. Justification regarding safety impact.
+| - **Issue 2**: Brief description of the known issue. Justification regarding safety impact.
+| - **Issue 3**: Brief description of the known issue. Justification regarding safety impact.
+|
+| Upgrade Instructions
+| --------------------
+|
+| 1. **Step 1**: Description of the first step.
+| 2. **Step 2**: Description of the second step.
+| 3. **Step 3**: Description of the third step.
+|
+| Contact Information
+| -------------------
+|
+| For any questions or support, please contact the *Project lead* or raise an issue/discussion.
diff --git a/docs/module_docs/safety_mgt/index.rst b/docs/module_docs/safety_mgt/index.rst
new file mode 100644
index 0000000..04718ba
--- /dev/null
+++ b/docs/module_docs/safety_mgt/index.rst
@@ -0,0 +1,23 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2024 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Safety Management
+#################
+
+.. toctree::
+   :titlesonly:
+
+   module_safety_plan
+   module_safety_plan_fdr
+   module_safety_package_fdr
diff --git a/docs/module_docs/safety_mgt/module_safety_package_fdr.rst b/docs/module_docs/safety_mgt/module_safety_package_fdr.rst
new file mode 100644
index 0000000..c3479eb
--- /dev/null
+++ b/docs/module_docs/safety_mgt/module_safety_package_fdr.rst
@@ -0,0 +1,63 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Safety Package Formal Review Report
+===================================
+
+.. document:: Rust Base Libraries Safety Package Formal Review
+   :id: doc__baselibs_rust_safety_package_fdr
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__fdr_reports
+   :tags: baselibs_rust
+
+**1. Purpose**
+
+The purpose of this review checklist is to report status of the formal review for the safety package.
+
+**2. Checklist**
+
+.. list-table:: Safety Package Checklist
+        :header-rows: 1
+
+        * - Id
+          - Safety package activity
+          - Compliant to ISO 26262?
+          - Comment
+
+        * - 1
+          - Is a safety package provided which matches the safety plan (i.e. all planned work products referenced)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 2
+          - Is the argument how functional safety is achieved, provided in the safety package, plausible and sufficient?
+          - NO
+          - The argument is intentionally not provided by the project.
+
+        * - 3
+          - Are the referenced work products available?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 4
+          - Are the referenced work products in released state, including the process safety audit?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 5
+          - If safety related deviations from the process or safety concept are documented, are these argued understandably?
+          - [YES | NO ]
+          - <Rationale for result>
diff --git a/docs/module_docs/safety_mgt/module_safety_plan.rst b/docs/module_docs/safety_mgt/module_safety_plan.rst
new file mode 100644
index 0000000..54bd3de
--- /dev/null
+++ b/docs/module_docs/safety_mgt/module_safety_plan.rst
@@ -0,0 +1,340 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Module Safety Plan
+******************
+
+.. document:: Rust Base Libraries Safety Plan
+   :id: doc__baselibs_rust_safety_plan
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__module_safety_plan
+   :tags: baselibs_rust
+
+
+Functional Safety Management Context
+====================================
+
+This Safety Plan adds to the :need:`gd_guidl__saf_plan_definitions` all the module development relevant work products needed for ISO 26262 conformity.
+
+Functional Safety Management Scope
+==================================
+
+This Safety Plan's scope is a SW module of the SW platform :ref:`module_documentation`.
+The module consists of one or more SW components and will be qualified as a SEooC.
+
+Functional Safety Management Roles
+==================================
+
++---------------------------+--------------------------------------------------------+
+| Safety Manager            | <link to Module's Safety Manager assignment or name>   |
++---------------------------+--------------------------------------------------------+
+| Project Manager           | <link to Module's Project Manager assignment or name>  |
++---------------------------+--------------------------------------------------------+
+
+Tailoring
+=========
+
+Additional to the tailoring in the SW platform project as defined in the :need:`gd_guidl__saf_plan_definitions` we define here the additional tailoring on module level.
+
+- Excluded for this module are additionally the following work products (and their related requirements):
+  - <ISO 26262 reference>: <work product/requirement> - <Argumentation why it is not needed or replaced by another work product or activity.>
+
+Functional Safety Module Work products
+======================================
+
+One set of work products for the module and one set for each component of the module:
+
+Module Work products List
+-------------------------
+
+.. list-table:: Module Work products
+        :header-rows: 1
+
+        * - Work product Id
+          - Link to process
+          - Process status
+          - Link to issue
+          - Link to WP
+          - WP status
+
+        * - :need:`wp__module_safety_plan`
+          - :need:`gd_guidl__saf_plan_definitions`
+          - :ndf:`copy('status', need_id='gd_guidl__saf_plan_definitions')`
+          - <Link to issue>
+          - this document
+          - see above
+
+        * - :need:`wp__module_safety_package`
+          - :need:`gd_guidl__saf_package`
+          - :ndf:`copy('status', need_id='gd_guidl__saf_package')`
+          - <Link to issue>
+          - this document (including the linked documentation)
+          - see above (and below)
+
+        * - :need:`wp__fdr_reports` (module Safety Plan)
+          - :need:`gd_chklst__safety_plan`
+          - :ndf:`copy('status', need_id='gd_chklst__safety_plan')`
+          - <Link to issue>
+          - :need:`doc__baselibs_rust_safety_plan_fdr`
+          - :ndf:`copy('status', need_id='doc__baselibs_rust_safety_plan_fdr')`
+
+        * - :need:`wp__fdr_reports` (module Safety Package)
+          - :need:`gd_chklst__safety_package`
+          - :ndf:`copy('status', need_id='gd_chklst__safety_package')`
+          - <Link to issue>
+          - :need:`doc__baselibs_rust_safety_package_fdr`
+          - :ndf:`copy('status', need_id='doc__baselibs_rust_safety_package_fdr')`
+
+        * - :need:`wp__fdr_reports` (module's Safety Analyses & DFA)
+          - Safety Analysis FDR tbd
+          - <automated>
+          - <Link to issue>
+          - <Link to WP>
+          - <automated>
+
+        * - :need:`wp__audit_report`
+          - performed by external experts
+          - n/a
+          - <Link to issue>
+          - <Link to WP>
+          - <WP status (manual)>
+
+        * - :need:`wp__module_sw_build_config`
+          - :need:`gd_temp__software_development_plan`
+          - `copy('status', need_id='gd_temp__software_development_plan')`
+          - <Link to issue>
+          - <Link to WP>
+          - <automated>
+
+        * - :need:`wp__module_safety_manual`
+          - :need:`gd_temp__safety_manual`
+          - :ndf:`copy('status', need_id='gd_temp__safety_manual')`
+          - <Link to issue>
+          - :need:`doc__baselibs_rust_safety_manual`
+          - :ndf:`copy('status', need_id='doc__baselibs_rust_safety_manual')`
+
+        * - :need:`wp__verification_module_ver_report`
+          - :need:`gd_temp__mod_ver_report`
+          - :ndf:`copy('status', need_id='gd_temp__mod_ver_report')`
+          - <Link to issue>
+          - :need:`doc__baselibs_rust_verification_report`
+          - :ndf:`copy('status', need_id='doc__baselibs_rust_verification_report')`
+
+        * - :need:`wp__module_sw_release_note`
+          - :need:`gd_temp__rel_mod_rel_note`
+          - :ndf:`copy('status', need_id='gd_temp__rel_mod_rel_note')`
+          - <Link to issue>
+          - :need:`doc__baselibs_rust_release_note`
+          - :ndf:`copy('status', need_id='doc__baselibs_rust_release_note')`
+
+Component <name> Work products List
+-----------------------------------
+
+.. list-table:: Component <name> Work products
+        :header-rows: 1
+
+        * - Work product Id
+          - Link to process
+          - Process status
+          - Link to issue
+          - Link to WP
+          - WP/doc status
+
+        * - :need:`wp__requirements_comp`
+          - :need:`gd_temp__req_comp_req`
+          - :ndf:`copy('status', need_id='gd_temp__req_comp_req')`
+          - <Link to issue>
+          - :need:`doc__log_requirements`
+          - doc :ndf:`copy('status', need_id='doc__log_requirements')` & WP below
+
+        * - :need:`wp__requirements_comp_aou`
+          - :need:`gd_temp__req_aou_req`
+          - :ndf:`copy('status', need_id='gd_temp__req_aou_req')`
+          - <Link to issue>
+          - :need:`doc__log_requirements`
+          - doc :ndf:`copy('status', need_id='doc__log_requirements')` & WP below
+
+        * - :need:`wp__requirements_inspect`
+          - :need:`gd_chklst__req_inspection`
+          - :ndf:`copy('status', need_id='gd_chklst__req_inspection')`
+          - n/a
+          - Checklist used in Pull Request Review
+          - n/a
+
+        * - :need:`wp__component_arch`
+          - :need:`gd_temp__arch_comp`
+          - :ndf:`copy('status', need_id='gd_temp__arch_comp')`
+          - <Link to issue>
+          - :need:`doc__log_architecture`
+          - doc :ndf:`copy('status', need_id='doc__log_architecture')` & WP below
+
+        * - :need:`wp__sw_arch_verification`
+          - :need:`gd_chklst__arch_inspection_checklist`
+          - :ndf:`copy('status', need_id='gd_chklst__arch_inspection_checklist')`
+          - n/a
+          - Checklist used in Pull Request Review
+          - n/a
+
+        * - :need:`wp__sw_component_fmea`
+          - :need:`gd_temp__comp_saf_fmea`
+          - :ndf:`copy('status', need_id='gd_temp__comp_saf_fmea')`
+          - <Link to issue>
+          - :need:`doc__log_fmea`
+          - doc :ndf:`copy('status', need_id='doc__log_fmea')` & WP below
+
+        * - :need:`wp__sw_component_dfa`
+          - :need:`gd_temp__comp_saf_dfa`
+          - :ndf:`copy('status', need_id='gd_temp__comp_saf_dfa')`
+          - <Link to issue>
+          - :need:`doc__log_dfa`
+          - doc :ndf:`copy('status', need_id='doc__log_dfa')` & WP below
+
+        * - :need:`wp__sw_implementation`
+          - :need:`gd_guidl__implementation`
+          - :ndf:`copy('status', need_id='gd_guidl__implementation')`
+          - <Link to issue>
+          - <Link to WP>
+          - <automated>
+
+        * - :need:`wp__verification_sw_unit_test`
+          - :need:`gd_guidl__verification_guide`
+          - :ndf:`copy('status', need_id='gd_guidl__verification_guide')`
+          - <Link to issue>
+          - <Link to WP>
+          - <automated>
+
+        * - :need:`wp__sw_implementation_inspection`
+          - :need:`gd_chklst__impl_inspection_checklist`
+          - :ndf:`copy('status', need_id='gd_chklst__impl_inspection_checklist')`
+          - n/a
+          - Checklist used in Pull Request Review
+          - n/a
+
+        * - :need:`wp__verification_comp_int_test`
+          - :need:`gd_guidl__verification_guide`
+          - :ndf:`copy('status', need_id='gd_guidl__verification_guide')`
+          - <Link to issue>
+          - <Link to WP>
+          - <automated>
+
+        * - :need:`wp__sw_component_class`
+          - :need:`gd_guidl__component_classification`
+          - :ndf:`copy('status', need_id='gd_guidl__component_classification')`
+          - <Link to issue>
+          - :need:`doc__log_comp_class`
+          - :ndf:`copy('status', need_id='doc__log_comp_class')`
+
+Note: In case the component is a new development, :need:`wp__sw_component_class` shall be removed from the above list (and also from the folders).
+In case an OSS element is used in the module, part 6 has to be filled out.
+
+OSS (sub-)component qualification plan
+======================================
+
+For the selected OSS component the following work products will be implemented (and why):
+
+If the OSS element is classified as a
+    - component, then the below table shall match the above, adding the reasoning for tailoring of work products according to the OSS component classification.
+    - lower level component, then no work products additional to the component’s will be planned and activities below are part of the component’s issues.
+
+.. list-table:: OSS (sub-)component <name> Work products
+        :header-rows: 1
+
+        * - Work product Id
+          - Link to issue
+          - Reasoning for tailoring
+
+        * - :need:`wp__requirements_comp`
+          - <Link to issue>
+          - Always needed (for Q and QR classification) and also improves process Id 2
+
+        * - :need:`wp__requirements_comp_aou`
+          - <Link to issue>
+          - Always needed (for Q and QR classification) and also improves process Id 5
+
+        * - :need:`wp__requirements_inspect`
+          - n/a
+          - Checklist used in Pull Request Review
+
+        * - :need:`wf__cr_mt_comparch`
+          - <Link to issue>
+          - <Reasoning for tailoring, needed for example in case of deficits in process Id 3&4 and complexity Ids 1&4>
+
+        * - :need:`wp__sw_component_fmea`
+          - <Link to issue>
+          - <Reasoning for tailoring, could help arguing too high cyclomatic complexity covered by safety mechanisms>
+
+        * - :need:`wp__sw_arch_verification`
+          - <Link to issue>
+          - <Reasoning for tailoring, needed if also wf__cr_mt_comparch is required>
+
+        * - :need:`wp__sw_implementation`
+          - n/a
+          - If source code is modified, this is not a OSS qualification any more.
+
+        * - :need:`wp__verification_sw_unit_test`
+          - <Link to issue>
+          - <Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 3>
+
+        * - :need:`wp__sw_implementation_inspection`
+          - <Link to issue>
+          - <Reasoning for tailoring, can improve deficits in process Id 6 and complexity Id 2>
+
+        * - :need:`wp__verification_comp_int_test`
+          - <Link to issue>
+          - Always needed (for Q and QR classification)
+
+        * - :need:`wp__sw_component_class`
+          - <Link to issue>
+          - Always needed as basis for tailoring.
+
+Work Product Status (for Safety Package)
+========================================
+
+Component Requirements Status
+-----------------------------
+
+.. needtable::
+   :filter: docname is not None and "log" in docname and "requirements" in docname
+   :style: table
+   :types: comp_req
+   :tags: log
+   :columns: id;status;tags
+   :colwidths: 25,25,25
+   :sort: title
+
+Component AoU Status
+--------------------
+
+.. needtable::
+   :filter: docname is not None and "log" in docname and "requirements" in docname
+   :style: table
+   :types: aou_req
+   :tags: log
+   :columns: id;status;tags
+   :colwidths: 25,25,25
+   :sort: title
+
+Component Architecture Status
+-----------------------------
+
+.. needtable::
+   :filter: docname is not None and "log" in docname and "requirements" in docname
+   :style: table
+   :types: comp_arc_sta; comp_arc_dyn
+   :tags: log
+   :columns: id;status;tags
+   :colwidths: 25,25,25
+   :sort: title
diff --git a/docs/module_docs/safety_mgt/module_safety_plan_fdr.rst b/docs/module_docs/safety_mgt/module_safety_plan_fdr.rst
new file mode 100644
index 0000000..fb53178
--- /dev/null
+++ b/docs/module_docs/safety_mgt/module_safety_plan_fdr.rst
@@ -0,0 +1,93 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Safety Plan Formal Review Report
+================================
+
+.. document:: Rust Base Libraries Safety Plan Formal Review
+   :id: doc__baselibs_rust_safety_plan_fdr
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__fdr_reports
+   :tags: baselibs_rust
+
+**1. Purpose**
+
+The purpose of this safety plan formal review checklist is to report status of the review for the safety plan.
+
+**2. Checklist**
+
+.. list-table:: Safety Plan Checklist
+        :header-rows: 1
+
+        * - Id
+          - Safety plan activity
+          - Compliant to ISO 26262?
+          - Comment
+
+        * - 1
+          - Is the rationale for the safety work products tailoring included?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 2
+          - Is impact analysis planned in case of re-use of SW (needed for every release following the first formal release)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 3
+          - Does the safety plan define all needed activities for safety management (incl. Confirmation review and Safety Audit)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 4
+          - Does the safety plan define all needed activities for System and SW development, integration and verification?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 5
+          - Does the safety plan define all needed activities for safety analysis and DFA?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 6
+          - Does the safety plan define all needed activities for supporting processes (incl. tool mgt)?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 7
+          - Does the safety plan document a responsible for all activities?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 8
+          - If OSS software components is used, is it planned to be qualified?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 9
+          - Is a safety manager and a project manager appointed for the project?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 10
+          - Is safety plan sufficiently linked to the project plan?
+          - [YES | NO ]
+          - <Rationale for result>
+
+        * - 11
+          - Is safety plan updated iteratively to show the progress?
+          - [YES | NO ]
+          - <Rationale for result>
diff --git a/docs/module_docs/verification/module_verification_report.rst b/docs/module_docs/verification/module_verification_report.rst
new file mode 100644
index 0000000..8701967
--- /dev/null
+++ b/docs/module_docs/verification/module_verification_report.rst
@@ -0,0 +1,81 @@
+..
+   # *******************************************************************************
+   # Copyright (c) 2025 Contributors to the Eclipse Foundation
+   #
+   # See the NOTICE file(s) distributed with this work for additional
+   # information regarding copyright ownership.
+   #
+   # This program and the accompanying materials are made available under the
+   # terms of the Apache License Version 2.0 which is available at
+   # https://www.apache.org/licenses/LICENSE-2.0
+   #
+   # SPDX-License-Identifier: Apache-2.0
+   # *******************************************************************************
+
+Verification Report
+===================
+
+.. document:: Rust Base Libraries Verification Report
+   :id: doc__baselibs_rust_verification_report
+   :status: draft
+   :safety: QM
+   :security: NO
+   :realizes: wp__verification_module_ver_report
+   :tags: baselibs_rust
+
+
+This verification report is based on the :need:`gd_temp__verification_plan`.
+It covers all the components of the above stated module.
+
+Verification Report contains:
+
+**1. Verification Coverage**
+
+**1.1. on Requirements**
+       - Lists of component requirements (incl. AoU satisfied by the component) tested by which test case, passed/failed and completeness verdict
+         (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)
+       - For external component Assumptions of Use: coverage by platform safety manual or feature/components incl. test case, passed/failed and completeness verdict
+       - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements.
+       - List of component requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export)
+
+**1.2. on Architecture**
+       - List of component architecture tags tested by which test case, passed/failed and completeness verdict
+         (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)
+       - This is split in a list of QM components tested and a separate list of tests for ASIL rated components.
+       - List of component architecture tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export)
+
+**1.3. on Detailed Design**
+       - List of detailed design tags tested by which test case, passed/failed and completeness verdict
+         (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)
+       - This is split in a list of QM components tested and a separate list of tests for ASIL rated components.
+       - List of detailed design tags (ASIL rated) linked to inspection checklist and verdict (derived from PR export)
+
+       - The lists may also contain other verification methods like "Analysis" - process tbd
+
+**2. DFA Report**
+       - List of the performed component DFA, pass/fail with open mitigations
+
+**3. Safety Analysis Report**
+       - List of the performed component Safety Analysis, pass/fail with open mitigations
+
+**4. Unit Verification Coverage**
+
+**4.1. Structural Coverage**
+       - List of the units with C0(line) and C1(branch) coverage absolute and percentage
+         (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)
+       - List includes a column for the safety rating of each unit.
+
+**4.2. Static Code Analysis**
+       - List of the units with compiler warning numbers and coding rule violation numbers
+         (this shall be generated by tools and accompanied by progress charts to be usable also for project steering)
+       - List includes a column for the safety rating of each unit.
+
+**4.3. Manual Code Inspection**
+       - List of components (ASIL rated) linked to inspection checklist and verdict (derived from PR export)
+
+**5. Software component qualification verification report**
+       - Contains the needed verification results if for some components a qualification of pre-developed SW is performed.
+
+**Note1:** The verification report is valid for the module version tagged together with the report
+
+**Note2:** All the above lists are generated automatically