From 6943ce83c156d5f3fc6e8a0305c1700348443ad8 Mon Sep 17 00:00:00 2001
From: Valery Lavrov <valery.lavrov@bmw.de>
Date: Tue, 3 Feb 2026 15:02:54 +0100
Subject: [PATCH] bmw score::time arch concept

---
 docs/conf.py                                  |   2 +-
 docs/index.rst                                |  39 +-
 docs/time/_assets/app/app_class.puml          |  44 +
 docs/time/_assets/app/app_init_seq.puml       |  71 ++
 docs/time/_assets/app/app_workflow_seq.puml   |  69 ++
 .../time/_assets/ctrlflow/ctrlflow_class.puml |  58 ++
 .../_assets/ctrlflow/ctrlflow_init_seq.puml   |  63 ++
 .../ctrlflow/ctrlflow_workflow_seq.puml       |  86 ++
 docs/time/_assets/dd_class.puml               | 135 +++
 docs/time/_assets/dd_data_control_flow.puml   |  98 ++
 docs/time/_assets/dd_deployment.puml          |  25 +
 .../abs_time/abs_time_data_control_flow.puml  |  58 ++
 .../abs_time/abs_time_deployment.puml         |  57 +
 .../examples/qvt/qvt_data_control_flow.puml   | 144 +++
 .../_assets/examples/qvt/qvt_deployment.puml  |  38 +
 docs/time/_assets/ipc/ipc_class.puml          |  63 ++
 docs/time/_assets/ipc/ipc_init_seq.puml       |  49 +
 docs/time/_assets/ipc/ipc_publish_seq.puml    |  41 +
 docs/time/_assets/ipc/ipc_receive_seq.puml    |  29 +
 .../_assets/msg_broker/msg_broker_class.puml  |  54 +
 .../msg_broker/msg_broker_init_seq.puml       |  66 ++
 .../msg_broker/msg_broker_workflow_seq.puml   |  38 +
 docs/time/_assets/mw/mw_class.puml            |  37 +
 docs/time/_assets/mw/mw_time_receive_seq.puml |  41 +
 .../mw/mw_time_receive_simple_seq.puml        |  33 +
 .../ptp_machine/ptp_machine_class.puml        |  64 ++
 .../ptp_machine_get_new_data_seq.puml         |  55 +
 .../ptp_machine/ptp_machine_init_seq.puml     |  79 ++
 docs/time/_assets/sad_deployment.puml         |  39 +
 docs/time/_assets/ver_machine/ver_class.puml  |  73 ++
 .../_assets/ver_machine/ver_init_seq.puml     |  66 ++
 .../ver_machine/ver_verification_seq.puml     |  57 +
 docs/time/index.rst                           | 983 ++++++++++++++++++
 33 files changed, 2839 insertions(+), 15 deletions(-)
 create mode 100644 docs/time/_assets/app/app_class.puml
 create mode 100644 docs/time/_assets/app/app_init_seq.puml
 create mode 100644 docs/time/_assets/app/app_workflow_seq.puml
 create mode 100644 docs/time/_assets/ctrlflow/ctrlflow_class.puml
 create mode 100644 docs/time/_assets/ctrlflow/ctrlflow_init_seq.puml
 create mode 100644 docs/time/_assets/ctrlflow/ctrlflow_workflow_seq.puml
 create mode 100644 docs/time/_assets/dd_class.puml
 create mode 100644 docs/time/_assets/dd_data_control_flow.puml
 create mode 100644 docs/time/_assets/dd_deployment.puml
 create mode 100644 docs/time/_assets/examples/abs_time/abs_time_data_control_flow.puml
 create mode 100644 docs/time/_assets/examples/abs_time/abs_time_deployment.puml
 create mode 100644 docs/time/_assets/examples/qvt/qvt_data_control_flow.puml
 create mode 100644 docs/time/_assets/examples/qvt/qvt_deployment.puml
 create mode 100644 docs/time/_assets/ipc/ipc_class.puml
 create mode 100644 docs/time/_assets/ipc/ipc_init_seq.puml
 create mode 100644 docs/time/_assets/ipc/ipc_publish_seq.puml
 create mode 100644 docs/time/_assets/ipc/ipc_receive_seq.puml
 create mode 100644 docs/time/_assets/msg_broker/msg_broker_class.puml
 create mode 100644 docs/time/_assets/msg_broker/msg_broker_init_seq.puml
 create mode 100644 docs/time/_assets/msg_broker/msg_broker_workflow_seq.puml
 create mode 100644 docs/time/_assets/mw/mw_class.puml
 create mode 100644 docs/time/_assets/mw/mw_time_receive_seq.puml
 create mode 100644 docs/time/_assets/mw/mw_time_receive_simple_seq.puml
 create mode 100644 docs/time/_assets/ptp_machine/ptp_machine_class.puml
 create mode 100644 docs/time/_assets/ptp_machine/ptp_machine_get_new_data_seq.puml
 create mode 100644 docs/time/_assets/ptp_machine/ptp_machine_init_seq.puml
 create mode 100644 docs/time/_assets/sad_deployment.puml
 create mode 100644 docs/time/_assets/ver_machine/ver_class.puml
 create mode 100644 docs/time/_assets/ver_machine/ver_init_seq.puml
 create mode 100644 docs/time/_assets/ver_machine/ver_verification_seq.puml
 create mode 100644 docs/time/index.rst

diff --git a/docs/conf.py b/docs/conf.py
index cf13475..2a47361 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -20,7 +20,7 @@
 # -- Project information -----------------------------------------------------
 # https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
 
-project = "Module Template Project"
+project = "S-CORE Time"
 project_url = "https://eclipse-score.github.io/module_template/"
 project_prefix = "MODULE_TEMPLATE_"
 author = "S-CORE"
diff --git a/docs/index.rst b/docs/index.rst
index f8e53da..14bf088 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -12,10 +12,10 @@
    # SPDX-License-Identifier: Apache-2.0
    # *******************************************************************************
 
-Module Template Documentation
-=============================
+TimeDaemon Documentation
+========================
 
-This documentation describes the structure, usage and configuration of the Bazel-based C++/Rust module template.
+This documentation describes the **TimeDaemon** and the **score::time** module.
 
 .. contents:: Table of Contents
    :depth: 2
@@ -24,20 +24,25 @@ This documentation describes the structure, usage and configuration of the Bazel
 Overview
 --------
 
-This repository provides a standardized setup for projects using **C++** or **Rust** and **Bazel** as a build system.
-It integrates best practices for build, test, CI/CD and documentation.
+**TimeDaemon** is a non-AUTOSAR adaptive process designed to provide synchronized vehicle time to client applications.
+It supports multiple time bases including **in-vehicle synchronized time** (PTP - Precision Time Protocol) and
+**external synchronized time** (absolute time base). The daemon retrieves time information from the respective time sources,
+verifies and validates the timepoints, and distributes this time information across multiple clients through efficient IPC mechanisms.
 
-Requirements
-------------
+The main responsibilities of TimeDaemon include:
 
-.. stkh_req:: Example Functional Requirement
-   :id: stkh_req__docgen_enabled__example
-   :status: valid
-   :safety: QM
-   :security: YES
-   :reqtype: Functional
-   :rationale: Ensure documentation builds are possible for all modules
+- **Providing current Vehicle time** to different applications
+- **Setting synchronization qualifiers** (e.g., Synchronized, Timeout, etc.)
+- **Providing diagnostic information** for system monitoring
+- **Supporting additional verification mechanisms** such as QualifiedVehicleTime (QVT) for safety-critical applications
 
+For a detailed concept and architectural design, please refer to the :doc:`TimeDaemon Concept Documentation <time/index>`.
+
+.. toctree::
+   :maxdepth: 2
+   :caption: Contents:
+
+   time/index
 
 Project Layout
 --------------
@@ -65,6 +70,12 @@ To run tests:
 
    bazel test //tests/...
 
+To build the documentation:
+
+.. code-block:: bash
+
+   bazel run //:docs
+
 Configuration
 -------------
 
diff --git a/docs/time/_assets/app/app_class.puml b/docs/time/_assets/app/app_class.puml
new file mode 100644
index 0000000..fd26989
--- /dev/null
+++ b/docs/time/_assets/app/app_class.puml
@@ -0,0 +1,44 @@
+@startuml application_class_diagram
+
+title Application: Class Diagram
+
+legend top left
+    |= Color         |= Description              |
+    | <#LightCyan>   | TimeDaemon members        |
+    | <#PaleTurquoise> | MessageBroker           |
+    | <#Wheat>       | PtpMachine                |
+    | <#LightBlue>   | ControlFlowDivider        |
+    | <#Lavender>    | VerificationMachine       |
+    | <#LightPink>   | IPC components            |
+endlegend
+
+class "TimeDaemon" as vtd_app #LightCyan {
+    +std::int32_t Initialize(const ApplicationContext& context) override
+    +std::int32_t Run(amp::stop_token& token) override
+}
+
+class "TimebaseHandler" as tb_handler #LightCyan{
+    +void Initialize()
+    +void RunOnce(stop_token&)
+    +void Stop()
+}
+note right
+    There might be multiple TimebaseHandlers
+    based on amount of supported time bases.
+end note
+
+class "MessageBroker" as msg_broker #PaleTurquoise
+class "PtpMachine" as ptp_machine #Wheat
+class "VerificationMachine" as ver_machine #Lavender
+class "ControlFlowDivider" as cf_divider #LightBlue
+class "IpcPublisher" as ipc_publisher #LightPink
+
+vtd_app *-- "1..*" tb_handler : owns
+
+tb_handler *-- msg_broker : owns
+tb_handler *-- ptp_machine : owns
+tb_handler *-- ver_machine : owns
+tb_handler *-- cf_divider : owns
+tb_handler *-- ipc_publisher : owns
+
+@enduml
diff --git a/docs/time/_assets/app/app_init_seq.puml b/docs/time/_assets/app/app_init_seq.puml
new file mode 100644
index 0000000..ca56235
--- /dev/null
+++ b/docs/time/_assets/app/app_init_seq.puml
@@ -0,0 +1,71 @@
+@startuml app_init_seq_diagram
+
+title Application: Initialization Sequence
+
+hide footbox
+autoactivate on
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description           |
+    |<#LightCyan>   | TimeDaemon members     |
+    |<#LightGreen>  | Middleware components  |
+    |<#Beige>       | SW components          |
+endlegend
+
+participant "LifecycleManager" as lcm #LightGreen
+participant "TimeDaemon" as vtd_app #LightCyan
+participant "TimebaseHandler" as tb_handler #LightCyan
+participant "Components" as components #Beige
+
+== TimeDaemon Construction ==
+
+lcm -> vtd_app ** : Construct TimeDaemon()
+activate vtd_app
+vtd_app -> tb_handler ** : create TimebaseHandler()
+activate tb_handler
+
+tb_handler -> components ** : create all components
+note right of components
+    TimebaseHandler creates:
+    - MessageBroker
+    - PtpMachine
+    - VerificationMachine
+    - ControlFlowDivider
+    - IPCPublisher
+end note
+
+tb_handler --> vtd_app : TimebaseHandler instance
+deactivate tb_handler
+vtd_app --> lcm : TimeDaemon instance
+deactivate vtd_app
+
+== Initialization Phase ==
+
+lcm -> vtd_app : Initialize(context)
+activate vtd_app
+
+vtd_app -> tb_handler : Initialize()
+activate tb_handler
+
+tb_handler -> tb_handler : Setup MessageBroker\nsubscriptions
+note right
+    Connect components via topics:
+    - input_ptp_data
+    - raw_ptp_data
+    - validated_ptp_data
+end note
+
+tb_handler --> vtd_app
+deactivate tb_handler
+
+vtd_app --> lcm
+deactivate vtd_app
+
+note right of tb_handler
+    All components created and connected,
+    but not yet started
+end note
+
+@enduml
diff --git a/docs/time/_assets/app/app_workflow_seq.puml b/docs/time/_assets/app/app_workflow_seq.puml
new file mode 100644
index 0000000..78c9b92
--- /dev/null
+++ b/docs/time/_assets/app/app_workflow_seq.puml
@@ -0,0 +1,69 @@
+@startuml app_init_seq_diagram
+
+title Application: Initialization Sequence
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightCyan>   | TimeDaemon members            |
+    |<#Wheat>       | PtpMachine                    |
+    |<#LightBlue>   | ControlFlowDivider            |
+    |<#LightGreen>  | Middleware components         |
+endlegend
+
+participant "LifecycleManager" as lcm #LightGreen
+participant "Application" as vtd_app #LightCyan
+participant "TimeBaseHandler" as tb_handler #LightCyan
+participant "PtpMachine" as ptp_machine #Wheat
+participant "ControlFlowDivider" as cf_divider #LightBlue
+
+== Execution Phase ==
+
+lcm -> vtd_app : Run(stopToken)
+activate vtd_app
+
+vtd_app -> tb_handler : RunOnce(stopToken)
+activate tb_handler
+tb_handler -> ptp_machine : start()
+activate ptp_machine
+ptp_machine --> tb_handler
+deactivate ptp_machine
+tb_handler -> cf_divider : start()
+activate cf_divider
+cf_divider --> tb_handler
+deactivate cf_divider
+tb_handler --> vtd_app
+deactivate tb_handler
+
+note over vtd_app: Monitor stop token\nfor termination request
+vtd_app -> vtd_app: wait until stopToken is triggered
+
+vtd_app --> lcm : return when stopped
+deactivate vtd_app
+
+== Shutdown Phase ==
+
+lcm -> vtd_app : (stop token triggered)
+activate vtd_app
+vtd_app -> tb_handler : Stop()
+activate tb_handler
+tb_handler -> cf_divider : stop(stop token triggered)
+activate cf_divider
+cf_divider -> cf_divider: join activities
+cf_divider --> tb_handler
+deactivate cf_divider
+
+tb_handler -> ptp_machine : stop(stop token triggered)
+activate ptp_machine
+ptp_machine -> ptp_machine: join activities
+ptp_machine --> tb_handler
+deactivate ptp_machine
+tb_handler --> vtd_app
+deactivate tb_handler
+vtd_app --> lcm
+deactivate vtd_app
+
+@enduml
diff --git a/docs/time/_assets/ctrlflow/ctrlflow_class.puml b/docs/time/_assets/ctrlflow/ctrlflow_class.puml
new file mode 100644
index 0000000..01d701a
--- /dev/null
+++ b/docs/time/_assets/ctrlflow/ctrlflow_class.puml
@@ -0,0 +1,58 @@
+@startuml control_flow_divider_class_diagram
+
+title ControlFlowDivider: Class Diagram
+
+legend top left
+    |= Color         |= Description                    |
+    | <#Beige>       | Base classes                    |
+    | <#LightBlue>   | ControlFlowDivider              |
+endlegend
+
+class "PtpTimeInfo" as time_info #Beige {
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+}
+
+abstract class "BaseMachine" as base_machine #Beige {
+    +GetName(): string
+    +Init(): bool
+}
+
+abstract class "ProactiveMachine" as proactive_machine #Beige {
+    +Start(): void
+    +Stop(): void
+}
+
+abstract class "EventDrivenMachine" as event_machine #Beige {
+    +NotifyEvent(): void
+    #OnEvent(): void
+    #OnTimeout(): void
+}
+
+abstract class "Consumer<T>" as consumer #Beige {
+    +OnMessage(data: T): void
+}
+
+abstract class "Producer<T>" as producer #Beige {
+    +SetPublishCallback(callback): void
+    #Publish(data: T): void
+}
+
+class "ControlFlowDivider<DataType, BufferSize>" as cfd #LightBlue {
+    -data_buffer_: circular_buffer<DataType, BufferSize>
+    +OnMessage(data: DataType): void
+    +SetPublishCallback(callback): void
+    #OnEvent(): void
+    #OnTimeout(): void
+}
+
+base_machine <|-- proactive_machine
+proactive_machine <|-- event_machine
+event_machine <|-- cfd
+consumer <|.. cfd
+producer <|.. cfd
+
+cfd --> time_info : processes
+
+@enduml
diff --git a/docs/time/_assets/ctrlflow/ctrlflow_init_seq.puml b/docs/time/_assets/ctrlflow/ctrlflow_init_seq.puml
new file mode 100644
index 0000000..fac9a77
--- /dev/null
+++ b/docs/time/_assets/ctrlflow/ctrlflow_init_seq.puml
@@ -0,0 +1,63 @@
+@startuml ctrlflow_init_seq_diagram
+
+title ControlFlowDivider: Initialization Sequence
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightCyan>   | TimeDaemon members            |
+    |<#PaleTurquoise> | MessageBroker               |
+    |<#LightBlue>   | ControlFlowDivider            |
+endlegend
+
+participant "TimeBaseHandler" as tb_handler #LightCyan
+participant "ControlFlowDivider" as cfd #LightBlue
+participant "MessageBroker" as broker #PaleTurquoise
+
+== ControlFlowDivider Construction ==
+
+tb_handler -> cfd ** : create(name, timeout)
+activate tb_handler
+activate cfd
+cfd -> cfd : Initialize()
+note right
+    Initialize buffer and
+    event-driven thread
+end note
+deactivate cfd
+deactivate tb_handler
+
+== Setup Connections ==
+
+tb_handler -> cfd : SetPublishCallback(broker::publish)
+activate tb_handler
+activate cfd
+cfd --> tb_handler
+deactivate cfd
+deactivate tb_handler
+
+tb_handler -> broker : Subscribe("validated_ptp_data", cfd::OnMessage)
+activate tb_handler
+activate broker
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+== Start Processing ==
+
+tb_handler -> cfd : Start()
+activate tb_handler
+activate cfd
+cfd -> cfd : Start thread
+note right
+    Start event-driven thread
+    waiting for data or timeout
+end note
+cfd --> tb_handler
+deactivate cfd
+deactivate tb_handler
+
+@enduml
diff --git a/docs/time/_assets/ctrlflow/ctrlflow_workflow_seq.puml b/docs/time/_assets/ctrlflow/ctrlflow_workflow_seq.puml
new file mode 100644
index 0000000..715eaec
--- /dev/null
+++ b/docs/time/_assets/ctrlflow/ctrlflow_workflow_seq.puml
@@ -0,0 +1,86 @@
+@startuml control_flow_divider_workflow
+
+title ControlFlowDivider: Main Workflow
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightCyan>   | TimeDaemon members            |
+    |<#PaleTurquoise> | MessageBroker               |
+    |<#LightBlue>   | ControlFlowDivider            |
+    |<#Lavender>    | VerificationMachine           |
+    |<#LightPink>   | IPC components                |
+endlegend
+
+participant "VerificationMachine" as vm #Lavender
+participant "MessageBroker" as broker #PaleTurquoise
+participant "ControlFlowDivider" as cfd #LightBlue
+participant "IPCPublisher" as ipc #LightPink
+
+== Data Arrival ==
+
+vm -> broker : publish("validated_ptp_data", data)
+activate vm
+activate broker
+broker -> cfd : OnMessage(data)
+activate cfd
+
+cfd -> cfd : Buffer data and\nnotify event thread
+note right
+    Data queued in
+    circular buffer
+end note
+
+cfd --> broker
+deactivate cfd
+broker --> vm
+deactivate broker
+deactivate vm
+
+== Event Processing ==
+
+loop process all buffered data
+    cfd -> cfd : OnEvent()
+    activate cfd
+    note right of cfd
+        Process all available data:
+        - Pop from buffer
+        - Store as last_data_
+        - Publish to subscribers
+    end note
+
+    cfd -> broker : publish_callback_(data)
+    activate broker
+    broker -> ipc : notify subscribers in separate thread
+    activate ipc
+    ipc --> broker
+    deactivate ipc
+    broker --> cfd
+    deactivate broker
+    deactivate cfd
+end
+
+== Timeout Handling ==
+
+alt if no new data arrives
+    cfd -> cfd : OnTimeout()
+    activate cfd
+    cfd -> broker : publish_callback_(last_data_)
+    activate broker
+    note right of cfd
+        Republish last known data
+        to maintain timing consistency
+    end note
+    broker -> ipc : notify subscribers in separate thread
+    activate ipc
+    ipc --> broker
+    deactivate ipc
+    broker --> cfd
+    deactivate broker
+    deactivate cfd
+end
+
+@enduml
diff --git a/docs/time/_assets/dd_class.puml b/docs/time/_assets/dd_class.puml
new file mode 100644
index 0000000..32005eb
--- /dev/null
+++ b/docs/time/_assets/dd_class.puml
@@ -0,0 +1,135 @@
+@startuml dd_class_diagram
+
+title TimeDaemon: Class Diagram Overview
+
+legend top left
+    | <#LightCyan>      | TimeDaemon members            |
+    | <#Wheat>          | PtpMachine                    |
+    | <#LightBlue>      | ControlFlowDivider            |
+    | <#Lavender>       | VerificationMachine           |
+    | <#LightPink>      | IPC components                |
+    | <#Beige>          | Base classes                  |
+endlegend
+
+class "PtpTimeInfo" as time_info #Beige {
+    Time information data structure
+    ...
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+}
+
+class "TimeBaseHandler" as tb_handler #LightCyan {
+    Main handler managing all components
+    ...
+    +Initialize(): void
+    +RunOnce(): void
+}
+
+class "MessageBroker<T>" as msg_broker #PaleTurquoise {
+    Central communication hub
+    ...
+    +AddSubscriber(topic, subscriber): void
+    +AddProducer(topic, producer): void
+    -Publish(topic, data): void
+}
+
+abstract class "BaseMachine" as base_machine #Beige {
+    Base class for all machines
+    ...
+    +GetName(): string
+    +Init(): bool
+}
+
+abstract class "Consumer<T>" as consumer #Beige {
+    Consumer interface
+    ...
+    +OnMessage(data: T): void
+}
+
+abstract class "Producer<T>" as producer #Beige {
+    Producer interface
+    ...
+    +SetPublishCallback(callback): void
+}
+
+abstract class "ProactiveMachine" as proactive_machine #Beige {
+    Machine with own execution thread
+    ...
+    +Start(): void
+    +Stop(): void
+}
+
+abstract class "ReactiveMachine" as reactive_machine #Beige {
+    Machine reacting to events
+}
+
+class "PTPMachine" as ptp_machine #Wheat {
+    Retrieves PTP time information
+    ...
+    +Init(): bool
+    #PeriodicTask(): void
+}
+
+class "ControlFlowDivider<T>" as control_flow_divider #LightBlue {
+    Decouples data flow timing
+    ...
+    +OnMessage(data): void
+    #OnEvent(): void
+    #OnTimeout(): void
+}
+
+class "VerificationMachine<T>" as ver_machine #Lavender {
+    Validates and qualifies time data
+    ...
+    +OnMessage(data): void
+}
+
+class "IpcPublisher<T>" as ipc_publisher #LightPink {
+    Publishes time data via IPC
+    ...
+    +OnMessage(data): void
+}
+
+class "IpcReceiver<T>" as ipc_receiver #LightPink {
+    Receives time data via IPC
+    ...
+    +Receive(): optional<PtpTimeInfo>
+}
+
+class "score::time::svt" as mw_svt #LightGreen {
+    Middleware time API
+    ...
+    +Now(): TimeStatus
+}
+
+base_machine <|-- proactive_machine
+base_machine <|-- reactive_machine
+
+proactive_machine <|.. ptp_machine
+proactive_machine <|.. control_flow_divider
+reactive_machine <|.. ver_machine
+reactive_machine <|.. ipc_publisher
+
+consumer <|.. control_flow_divider
+consumer <|.. ver_machine
+consumer <|.. ipc_publisher
+
+producer <|.. ptp_machine
+producer <|.. control_flow_divider
+producer <|.. ver_machine
+
+ptp_machine --> msg_broker : produces to
+control_flow_divider --> msg_broker : consumes/produces
+ver_machine --> msg_broker : consumes/produces
+ipc_publisher --> msg_broker : consumes from
+
+mw_svt *-- ipc_receiver : uses
+
+tb_handler *-- msg_broker : contains
+tb_handler *-- ptp_machine : contains
+tb_handler *-- control_flow_divider : contains
+tb_handler *-- ver_machine : contains
+tb_handler *-- ipc_publisher : contains
+
+@enduml
diff --git a/docs/time/_assets/dd_data_control_flow.puml b/docs/time/_assets/dd_data_control_flow.puml
new file mode 100644
index 0000000..d67f324
--- /dev/null
+++ b/docs/time/_assets/dd_data_control_flow.puml
@@ -0,0 +1,98 @@
+@startuml dd_data_control_flow_diagram
+
+title TimeDaemon: Data and Control Flow
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                  |
+    |<#PaleTurquoise> | MessageBroker               |
+    |<#Wheat>       | PtpMachine                    |
+    |<#LightBlue>   | ControlFlowDivider            |
+    |<#Lavender>    | VerificationMachine           |
+    |<#LightPink>   | IPC components                |
+    |<#WhiteSmoke>  | Shared Memory                 |
+    |<#LightGreen>  | Middleware components         |
+    |<#LightSalmon> | Client Application            |
+endlegend
+
+box TimeDaemon #LightYellow
+    participant "PTPMachine" as ptp_machine #Wheat
+    participant "MessageBroker" as broker #PaleTurquoise
+    participant "ControlFlowDivider" as cf_divider #LightBlue
+    participant "VerificationMachine" as ver_machine #Lavender
+    participant "IpcPublisher" as ipc_publisher #LightPink
+end box
+
+participant "SharedMemory" as shared_memory #WhiteSmoke
+
+box Application #e6ffe6
+    participant "IpcReceiver" as ipc_receiver #LightPink
+    participant "score::time::svt" as mw_svt #LightGreen
+    participant "Application" as app #LightSalmon
+end box
+
+group PTP data retrieval (periodic)
+    ptp_machine -> ptp_machine : PeriodicTask()
+    activate ptp_machine
+    note right
+        Read PTP time from
+        PTP engine
+    end note
+    ptp_machine -> broker : publish_callback_(PtpTimeInfo)
+    activate broker
+    broker -> cf_divider : OnMessage(PtpTimeInfo)
+    activate cf_divider
+    cf_divider -> cf_divider : Buffer and notify with new event
+    cf_divider --> broker
+    deactivate cf_divider
+    broker --> ptp_machine
+    deactivate broker
+    deactivate ptp_machine
+end
+
+group Data processing (event-driven)
+    cf_divider -> cf_divider : OnEvent()
+    activate cf_divider
+    cf_divider -> broker : publish_callback_(PtpTimeInfo)
+    activate broker
+    broker -> ver_machine : OnMessage(PtpTimeInfo)
+    activate ver_machine
+    ver_machine -> ver_machine : Validate through pipeline
+    ver_machine -> broker : publish_callback_(PtpTimeInfo)
+    deactivate ver_machine
+
+    broker -> ipc_publisher : OnMessage(PtpTimeInfo)
+    activate ipc_publisher
+    ipc_publisher -> shared_memory : Write(PtpTimeInfo)
+    activate shared_memory
+    shared_memory --> ipc_publisher
+    deactivate shared_memory
+    ipc_publisher --> broker
+    deactivate ipc_publisher
+    broker --> cf_divider
+    deactivate broker
+    deactivate cf_divider
+end
+
+group Application request (on-demand)
+    app -> mw_svt : Now()
+    activate app
+    activate mw_svt
+    mw_svt -> ipc_receiver : Receive()
+    activate ipc_receiver
+    ipc_receiver -> shared_memory : Receive()
+    activate shared_memory
+    shared_memory --> ipc_receiver : PtpTimeInfo
+    deactivate shared_memory
+    ipc_receiver --> mw_svt : PtpTimeInfo
+    deactivate ipc_receiver
+    mw_svt -> mw_svt : Calculate current time
+    mw_svt --> app : Current Vehicle Time
+    deactivate mw_svt
+    deactivate app
+end
+
+@enduml
diff --git a/docs/time/_assets/dd_deployment.puml b/docs/time/_assets/dd_deployment.puml
new file mode 100644
index 0000000..e799559
--- /dev/null
+++ b/docs/time/_assets/dd_deployment.puml
@@ -0,0 +1,25 @@
+@startuml dd_deployment_diagram
+
+title Deployment view
+
+node "Application Layer" {
+    [Business logic] as app_bl
+    [mw::time::svt] <<library>> as mw
+}
+node "PTP Daemon" {
+    [ptpd] <<daemon>> as ptpd
+}
+node "VehicleTimeDaemon" {
+    [MessageBroker]  as msg_broker
+    [VerificationMachine]  as verification_machine
+    [PTP machine] as ptp_machine
+    [IPC] as ipc
+}
+
+ptpd -[#blue]-> ptp_machine : PTP time updates\n(via shmem and devctl)
+ptp_machine -[#green]-> verification_machine: Time information
+verification_machine -[#green]-> ipc: Time information
+ipc -[#green]-> mw: Time information
+mw-[#orange]-> app_bl : Now()
+
+@enduml
diff --git a/docs/time/_assets/examples/abs_time/abs_time_data_control_flow.puml b/docs/time/_assets/examples/abs_time/abs_time_data_control_flow.puml
new file mode 100644
index 0000000..9f05781
--- /dev/null
+++ b/docs/time/_assets/examples/abs_time/abs_time_data_control_flow.puml
@@ -0,0 +1,58 @@
+@startuml dd_data_control_flow_diagram
+
+title VehicleTimeDaemon: Multi-Timebase Data Flow
+
+hide footbox
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightBlue>   | PTP Pipeline                  |
+    |<#RosyBrown>   | Absolute Time Pipeline        |
+    |<#LightGreen>  | Middleware                    |
+    |<#LightSalmon> | Application                   |
+endlegend
+
+participant "ptpd" as ptpd #PeachPuff
+participant "SDat SOMEIP" as sdat_someip #PeachPuff
+
+box TimeDaemon: PTP Pipeline #LightCyan
+    participant "PTPMachine" as ptp_machine #LightBlue
+    participant "ControlFlow &\nVerification" as ptp_pipeline #LightBlue
+    participant "SharedMemory\nPTP" as shmem_ptp #WhiteSmoke
+end box
+
+box TimeDaemon: Absolute Time Pipeline #MistyRose
+    participant "AbsTimeMachine" as abs_machine #RosyBrown
+    participant "ControlFlow &\nVerification" as abs_pipeline #RosyBrown
+    participant "SharedMemory\nAbsTime" as shmem_abs #WhiteSmoke
+end box
+
+box Application #e6ffe6
+    participant "score::time::svt" as mw_svt #LightGreen
+    participant "score::time::abs" as mw_abs #LightGreen
+    participant "Application" as app #LightSalmon
+end box
+
+== PTP Time Flow ==
+
+ptpd -> ptp_machine : PTP data
+ptp_machine -> ptp_pipeline : Validate & process
+ptp_pipeline -> shmem_ptp : Write PtpTimeInfo
+
+app -> mw_svt : Now()
+mw_svt -> shmem_ptp : Read
+shmem_ptp --> mw_svt : PtpTimeInfo
+mw_svt --> app : Current Vehicle Time
+
+== Absolute Time Flow ==
+
+sdat_someip -> abs_machine : Absolute time data
+abs_machine -> abs_pipeline : Validate & process
+abs_pipeline -> shmem_abs : Write AbsTimeInfo
+
+app -> mw_abs : Now()
+mw_abs -> shmem_abs : Read
+shmem_abs --> mw_abs : AbsTimeInfo
+mw_abs --> app : Current Absolute Time
+
+@enduml
diff --git a/docs/time/_assets/examples/abs_time/abs_time_deployment.puml b/docs/time/_assets/examples/abs_time/abs_time_deployment.puml
new file mode 100644
index 0000000..ff5c38b
--- /dev/null
+++ b/docs/time/_assets/examples/abs_time/abs_time_deployment.puml
@@ -0,0 +1,57 @@
+@startuml dd_deployment_diagram
+
+title Deployment view
+
+node "Application Layer" {
+    [Business logic] as app_bl
+    [mw::time::svt] <<library>> as mw
+}
+
+node "Application Layer\n(Absolute Time)" {
+    [Business logic] as app_abs_bl
+    [mw::time::abs] <<library>> as mw_abs
+}
+
+node "PTP Daemon" {
+    [ptpd] <<daemon>> as ptpd
+}
+
+node "SDat SOMEIP" {
+    [Time provider] <<service>> as time_provider
+}
+
+node "TimeDaemon" {
+    [MessageBroker]  as msg_broker
+
+    package "PTP Pipeline" {
+        [PTP machine] as ptp_machine
+        [ControlFlowDivider PTP] as cf_ptp
+        [VerificationMachine PTP]  as verification_machine_ptp
+        [IPC_PTP] as ipc_ptp
+    }
+
+    package "Absolute Time Pipeline" {
+        [AbsoluteTimeMachine]  as abs_time_machine
+        [ControlFlowDivider AbsTime] as cf_abs
+        [VerificationMachine AbsTime]  as verification_machine_abs
+        [IPC_AbsTime] as ipc_abs
+    }
+}
+
+' PTP Pipeline
+ptpd -[#blue]-> ptp_machine : PTP time updates\n(via shmem and devctl)
+ptp_machine -[#green]-> cf_ptp : PTP data
+cf_ptp -[#green]-> verification_machine_ptp: PTP data
+verification_machine_ptp -[#green]-> ipc_ptp: Verified PTP time
+ipc_ptp -[#green]-> mw: PTP time information
+mw -[#orange]-> app_bl : Now()
+
+' Absolute Time Pipeline
+time_provider -[#blue]-> abs_time_machine : Absolute time\n(UTC/TAI/GPS)
+abs_time_machine -[#purple]-> cf_abs : Absolute time data
+cf_abs -[#purple]-> verification_machine_abs: Absolute time data
+verification_machine_abs -[#purple]-> ipc_abs: Verified absolute time
+ipc_abs -[#purple]-> mw_abs : Absolute time
+mw_abs -[#orange]-> app_abs_bl : Now()
+
+@enduml
diff --git a/docs/time/_assets/examples/qvt/qvt_data_control_flow.puml b/docs/time/_assets/examples/qvt/qvt_data_control_flow.puml
new file mode 100644
index 0000000..8e30bea
--- /dev/null
+++ b/docs/time/_assets/examples/qvt/qvt_data_control_flow.puml
@@ -0,0 +1,144 @@
+@startuml dd_data_control_flow_diagram
+
+title VehicleTimeDaemon: Data and Control Flow
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color           |= Description                           |
+    |<#PaleTurquoise>  | MessageBroker                          |
+    |<#Wheat>          | PTPMachine                             |
+    |<#LightBlue>      | ControlFlowDivider                     |
+    |<#Lavender>       | VerificationMachine                    |
+    |<#LightPink>      | IPC components                         |
+    |<#WhiteSmoke>     | Shared Memory                          |
+    |<#LightGreen>     | Middleware components                  |
+    |<#LightSalmon>    | Client Application                     |
+    |<#RosyBrown>      | QualifiedVehicleTime components        |
+    |<#PeachPuff>      | BSP/OS Components                      |
+endlegend
+
+participant "ptpd" as ptpd #PeachPuff
+
+box VehicleTimeDaemon #LightYellow
+    participant "libptpd" as libptpd #PeachPuff
+    participant "PTPMachine" as ptp_machine #Wheat
+    participant "MessageBroker" as broker #PaleTurquoise
+    participant "ControlFlowDivider" as cf_divider #LightBlue
+    participant "VerificationMachine" as ver_machine #Lavender
+    participant "QualifiedVehicleTime" as qvt_machine #RosyBrown
+    participant "IpcPublisher" as ipc_publisher #LightPink
+    participant "IpcPublisher\nQVT" as ipc_qvt_publisher #RosyBrown
+end box
+
+participant "SharedMemory" as shared_memory #WhiteSmoke
+participant "SharedMemory\nQVT" as shared_memory_qvt #WhiteSmoke
+
+box Application #e6ffe6
+    participant "IpcReceiver" as ipc_receiver #LightPink
+    participant "IpcReceiver\nQVT" as ipc_qvt_receiver #RosyBrown
+    participant "score::time::svt" as mw_svt #LightGreen
+    participant "score::time::qvt" as mw_qvt #RosyBrown
+    participant "Application" as app #LightSalmon
+end box
+
+group PTP handling thread scope
+    ptp_machine -> libptpd: receive()
+    activate ptp_machine
+    activate libptpd
+    libptpd -> ptpd: devctl
+    activate ptpd
+    ptpd --> libptpd: TimeInfo
+    deactivate ptpd
+    libptpd --> ptp_machine: TimeInfo
+    deactivate libptpd
+    ptp_machine -> broker: publish_callback_(PtpTimeInfo)
+    activate broker
+    broker -> cf_divider: OnMessage(PtpTimeInfo)
+    activate cf_divider
+    cf_divider -> cf_divider: Buffer and notify with new event
+    cf_divider --> broker
+    deactivate cf_divider
+    broker --> ptp_machine
+    deactivate broker
+    deactivate ptp_machine
+end
+
+group TimeInfo handling thread scope
+    cf_divider -> cf_divider: OnEvent()
+    activate cf_divider
+    cf_divider -> broker: publish_callback_(PtpTimeInfo)
+    activate broker
+    broker -> ver_machine: OnMessage(PtpTimeInfo)
+    activate ver_machine
+    ver_machine -> ver_machine: Validate through pipeline
+    ver_machine -> broker: publish_callback_(PtpTimeInfo)
+    deactivate ver_machine
+
+    broker -> qvt_machine: OnMessage(PtpTimeInfo)
+    activate qvt_machine
+    qvt_machine -> qvt_machine: Qualify PTP data
+    qvt_machine -> broker: publish_callback_(PtpTimeInfo & QvtInfo)
+    deactivate qvt_machine
+
+    broker -> ipc_publisher: OnMessage(PtpTimeInfo)
+    activate ipc_publisher
+    ipc_publisher -> shared_memory: Write(PtpTimeInfo)
+    activate shared_memory
+    shared_memory --> ipc_publisher
+    deactivate shared_memory
+    ipc_publisher --> broker
+    deactivate ipc_publisher
+
+    broker -> ipc_qvt_publisher: OnMessage(QvtInfo)
+    activate ipc_qvt_publisher
+    ipc_qvt_publisher -> shared_memory_qvt: Write(QvtInfo)
+    activate shared_memory_qvt
+    shared_memory_qvt --> ipc_qvt_publisher
+    deactivate shared_memory_qvt
+    ipc_qvt_publisher --> broker
+    deactivate ipc_qvt_publisher
+
+    broker --> cf_divider
+    deactivate broker
+    deactivate cf_divider
+end
+
+group Application use case thread scope
+    app -> mw_svt: Now()
+    activate app
+    activate mw_svt
+    mw_svt -> ipc_receiver: Receive()
+    activate ipc_receiver
+    ipc_receiver -> shared_memory: Receive()
+    activate shared_memory
+    shared_memory --> ipc_receiver: PtpTimeInfo
+    deactivate shared_memory
+    ipc_receiver --> mw_svt: PtpTimeInfo
+    deactivate ipc_receiver
+    mw_svt -> mw_svt: Calculate current time
+    mw_svt --> app: Current Vehicle Time
+    deactivate mw_svt
+    deactivate app
+end
+
+group Diagnostic use case thread scope
+    app -> mw_qvt: GetCurrentData()
+    activate app
+    activate mw_qvt
+    mw_qvt -> ipc_qvt_receiver: Receive()
+    activate ipc_qvt_receiver
+    ipc_qvt_receiver -> shared_memory_qvt: Receive()
+    activate shared_memory_qvt
+    shared_memory_qvt --> ipc_qvt_receiver: QvtInfo
+    deactivate shared_memory_qvt
+    ipc_qvt_receiver --> mw_qvt: QvtInfo
+    deactivate ipc_qvt_receiver
+    mw_qvt --> app: Current QvtInfo
+    deactivate mw_qvt
+    deactivate app
+end
+
+@enduml
diff --git a/docs/time/_assets/examples/qvt/qvt_deployment.puml b/docs/time/_assets/examples/qvt/qvt_deployment.puml
new file mode 100644
index 0000000..897853d
--- /dev/null
+++ b/docs/time/_assets/examples/qvt/qvt_deployment.puml
@@ -0,0 +1,38 @@
+@startuml dd_deployment_diagram
+
+title Deployment view
+
+node "Application Layer" {
+    [Business logic] as app_bl
+    [mw::time::svt] <<library>> as mw
+}
+
+node "Application Layer\n(Diagnostics)" {
+    [Business logic] as app_diag_bl
+    [mw::time::qvt] <<library>> as mw_qvt
+}
+
+node "PTP Daemon" {
+    [ptpd] <<daemon>> as ptpd
+}
+
+node "TimeDaemon" {
+    [MessageBroker]  as msg_broker
+    [VerificationMachine]  as verification_machine
+    [QualifiedVehicleTime]  as qvt_machine
+    [PTP machine] as ptp_machine
+    [IPC] as ipc
+    [IPC_QVT] as ipc_qvt
+}
+
+ptpd -[#blue]-> ptp_machine : PTP time updates\n(via shmem and devctl)
+ptp_machine -[#green]-> verification_machine: Time information
+verification_machine -[#green]-> qvt_machine: Time information
+qvt_machine -[#green]-> ipc: Time information
+qvt_machine -[#green]-> ipc_qvt: Diag-related information\nfor DTC and communication\nto central validator
+ipc_qvt -[#green]-> mw_qvt : Now()
+mw_qvt -[#orange]-> app_diag_bl : Now()
+ipc -[#green]-> mw: Time information
+mw -[#orange]-> app_bl : Now()
+
+@enduml
diff --git a/docs/time/_assets/ipc/ipc_class.puml b/docs/time/_assets/ipc/ipc_class.puml
new file mode 100644
index 0000000..868b347
--- /dev/null
+++ b/docs/time/_assets/ipc/ipc_class.puml
@@ -0,0 +1,63 @@
+@startuml ipc_class_diagram
+
+title IPC: Class Diagram
+
+legend top left
+    |= Color         |= Description                    |
+    | <#Beige>       | Base classes                    |
+    | <#LightPink>   | IPC components                  |
+endlegend
+
+class "PtpTimeInfo" as time_info #Beige {
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+}
+
+abstract class "BaseMachine" as base_machine #Beige {
+    +GetName(): string
+    +Init(): bool
+}
+
+abstract class "ReactiveMachine" as reactive_machine #Beige {
+}
+
+abstract class "Consumer<T>" as consumer #Beige {
+    +OnMessage(data: T): void
+}
+
+abstract class "Receiver<T>" as receiver #Beige {
+    +Init(): bool
+    +Receive(): optional<T>
+}
+
+class "PublisherImpl<DataType>" as publisher_impl #LightPink {
+    -shm_handler_: SharedMemoryHandler<DataType>
+    +OnMessage(data: DataType): void
+    +Init(): bool
+}
+
+class "ReceiverImpl<DataType>" as receiver_impl #LightPink {
+    -shm_handler_: SharedMemoryHandler<DataType>
+    +Init(): bool
+    +Receive(): optional<DataType>
+}
+
+class "SharedMemoryHandler<T>" as shm_handler #LightCyan {
+    +Init(): bool
+    +Send(data: T): void
+    +Receive(): optional<T>
+}
+
+base_machine <|-- reactive_machine
+reactive_machine <|-- publisher_impl
+consumer <|.. publisher_impl
+receiver <|-- receiver_impl
+
+publisher_impl --> shm_handler : uses
+receiver_impl --> shm_handler : uses
+
+publisher_impl --> time_info : processes
+receiver_impl --> time_info : processes
+
+@enduml
diff --git a/docs/time/_assets/ipc/ipc_init_seq.puml b/docs/time/_assets/ipc/ipc_init_seq.puml
new file mode 100644
index 0000000..1376bb1
--- /dev/null
+++ b/docs/time/_assets/ipc/ipc_init_seq.puml
@@ -0,0 +1,49 @@
+@startuml ipc_init_seq_diagram
+
+title IPC Machine: Initialization
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+autoactivate on
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightCyan>   | TimeDaemon members            |
+    |<#LightPink>   | IPC components                |
+    |<#WhiteSmoke>  | Shared Memory                 |
+    |<#LightSalmon> | Client Application            |
+    |<#LightGreen>  | Middleware components         |
+endlegend
+
+box VehicleTimeDaemon #LightYellow
+    participant "Application" as app #LightCyan
+    participant "MessageBroker" as broker #LightCyan
+    participant "IPCMachine:publisher" as ipc_publisher #LightPink
+end box
+
+participant "shmem" as shared_memory #WhiteSmoke
+
+box Application #e6ffe6
+    participant "IPCMachine:receiver" as ipc_receiver #LightPink
+    participant "mw::time::svt" as mw #LightGreen
+    participant "Business logic" as client_app #LightSalmon
+end box
+
+app -> ipc_publisher: create()
+ipc_publisher -> shared_memory**: create
+shared_memory --> ipc_publisher: success
+ipc_publisher --> app : ipc_publisher object
+app -> broker : subscribe("verified_ptp_data", ipc_publisher::onNewData)
+broker --> app
+
+client_app -> mw: create()
+mw -> ipc_receiver: create()
+loop while try_open returns false
+    ipc_receiver -> shared_memory: try_open()
+    shared_memory --> ipc_receiver: success or fail
+end
+ipc_receiver --> mw
+mw --> client_app
+
+@enduml
diff --git a/docs/time/_assets/ipc/ipc_publish_seq.puml b/docs/time/_assets/ipc/ipc_publish_seq.puml
new file mode 100644
index 0000000..1f442fe
--- /dev/null
+++ b/docs/time/_assets/ipc/ipc_publish_seq.puml
@@ -0,0 +1,41 @@
+@startuml ipc_publish_seq_diagram
+
+title IPC Machine: Publishing new TimeInfo data
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+autoactivate on
+
+legend top left
+    |= Color     |= Description                  |
+    |<#LightCyan>| TimeDaemon members            |
+    |<#LightPink>| IPC components                |
+    |<#WhiteSmoke>| Shared Memory                |
+endlegend
+
+box VehicleTimeDaemon #LightYellow
+    participant "MessageBroker" as broker #LightCyan
+    participant "IPCMachine:publisher" as ipc_publisher #LightPink
+end box
+
+participant "shmem" as shared_memory #WhiteSmoke
+
+broker -> ipc_publisher: newTimeData(TimeInfo)
+alt if the data was updated
+    ipc_publisher -> ipc_publisher: serialize data
+    ipc_publisher -> shared_memory: store(TimeInfo)
+    note right
+        All data, which is needed by the Apps, like
+        1. current Vehicle time
+        2. local time
+        3. status
+        4. sync/fup and pdelay frames content
+        5. rate and so on
+        shall be stored here
+    end note
+    shared_memory --> ipc_publisher: success
+end
+ipc_publisher --> broker
+
+@enduml
diff --git a/docs/time/_assets/ipc/ipc_receive_seq.puml b/docs/time/_assets/ipc/ipc_receive_seq.puml
new file mode 100644
index 0000000..bcb935e
--- /dev/null
+++ b/docs/time/_assets/ipc/ipc_receive_seq.puml
@@ -0,0 +1,29 @@
+@startuml ipc_receive_seq_diagram
+
+title IPC Machine: Receiving new TimeInfo data
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+autoactivate on
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightPink>   | IPC components                |
+    |<#WhiteSmoke>  | Shared Memory                 |
+    |<#LightSalmon> | Client Application            |
+endlegend
+
+box mw::time::svt #e6ffe6
+    participant "Business logic" as mw_worker #LightSalmon
+    participant "IPCMachine:receiver" as ipc_receiver #LightPink
+end box
+
+participant "shmem" as shared_memory #WhiteSmoke
+
+mw_worker -> ipc_receiver: receive()
+ipc_receiver -> shared_memory: read()
+shared_memory --> ipc_receiver: TimeInfo
+ipc_receiver --> mw_worker: TimeInfo
+
+@enduml
diff --git a/docs/time/_assets/msg_broker/msg_broker_class.puml b/docs/time/_assets/msg_broker/msg_broker_class.puml
new file mode 100644
index 0000000..516ba85
--- /dev/null
+++ b/docs/time/_assets/msg_broker/msg_broker_class.puml
@@ -0,0 +1,54 @@
+@startuml message_broker_class_diagram
+
+title MessageBroker: Class Diagram
+
+legend top left
+    |= Color         |= Description                    |
+    | <#Beige>       | Base classes                    |
+    | <#PaleTurquoise> | MessageBroker                 |
+endlegend
+
+class "PtpTimeInfo" as time_info #Beige {
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+}
+
+class "Topic" as topic #Beige {
+    -name_: string
+    +Name(): string
+}
+
+abstract class "Consumer<T>" as consumer #Beige {
+    +OnMessage(data: T): void
+}
+
+abstract class "Producer<T>" as producer #Beige {
+    +SetPublishCallback(callback): void
+}
+
+class "Subscription<T>" as subscription #PaleTurquoise {
+    +callback_: function<void(const T&)>
+}
+
+class "MessageBroker<T>" as msg_broker #PaleTurquoise {
+    +AddSubscriber(topic, subscriber): void
+    +AddProducer(topic, producer): void
+    -Subscribe(topic, subscription): void
+    -Publish(topic, data): void
+    -OnNewData(topic, data): void
+}
+
+msg_broker "1" *-- "*" subscription : contains
+msg_broker --> topic : uses
+msg_broker ..> consumer : registers
+msg_broker ..> producer : registers
+subscription --> time_info : delivers
+
+note right of msg_broker
+    MessageBroker
+    manages topic-based
+    publish-subscribe pattern
+end note
+
+@enduml
diff --git a/docs/time/_assets/msg_broker/msg_broker_init_seq.puml b/docs/time/_assets/msg_broker/msg_broker_init_seq.puml
new file mode 100644
index 0000000..ac401cd
--- /dev/null
+++ b/docs/time/_assets/msg_broker/msg_broker_init_seq.puml
@@ -0,0 +1,66 @@
+@startuml message_broker_initialization_sequence_diagram
+
+title MessageBroker: Initialization Sequence
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightCyan>   | TimeDaemon members            |
+    |<#PaleTurquoise> | MessageBroker               |
+    |<#Beige>       | Base classes                  |
+endlegend
+
+participant "TimeBaseHandler" as tb_handler #LightCyan
+participant "MessageBroker" as broker #PaleTurquoise
+participant "Producer" as producer #Beige
+
+== MessageBroker Construction ==
+
+tb_handler -> broker ** : create()
+activate tb_handler
+activate broker
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+== Setup Subscriptions ==
+
+tb_handler -> broker : AddSubscriber(topic, Consumer*)
+activate tb_handler
+activate broker
+broker -> broker : Store subscription
+note right
+    Register Consumer to receive
+    messages on topic.
+    All sw components, who are interested
+    in "particular" topic should be
+    registered here.
+end note
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+== Setup Producers ==
+
+tb_handler -> broker : AddProducer("topic, Producer*)
+activate tb_handler
+activate broker
+broker -> producer : SetPublishCallback(broker::OnNewData)
+activate producer
+note right
+    Register Producer to callback
+    to publish to topic
+    All sw components, who are contributing
+    in "particular" topic should be
+    registered here.
+end note
+producer --> broker
+deactivate producer
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+@enduml
diff --git a/docs/time/_assets/msg_broker/msg_broker_workflow_seq.puml b/docs/time/_assets/msg_broker/msg_broker_workflow_seq.puml
new file mode 100644
index 0000000..8ab97dc
--- /dev/null
+++ b/docs/time/_assets/msg_broker/msg_broker_workflow_seq.puml
@@ -0,0 +1,38 @@
+@startuml message_broker_workflow_sequence_diagram
+
+title Message Broker: Workflow Diagram
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color          |= Description                  |
+    |<#PaleTurquoise> | MessageBroker               |
+    |<#Beige>         | Base classes                  |
+endlegend
+
+box VehicleTimeDaemon #LightYellow
+    participant "Producer<T>" as machine_pub #Beige
+    participant "MessageBroker" as msg_broker #PaleTurquoise
+    participant "Consumer<T>" as machine_sub #Beige
+end box
+
+
+machine_pub -> msg_broker : publish(topic, PTPTimeInfo)
+activate msg_broker
+
+msg_broker -> msg_broker: search for subscribers\non provided <topic>
+
+loop for all found subscribers
+    msg_broker -> machine_sub: callback(PTPTimeInfo)
+    activate machine_sub
+    note right machine_sub: Process PTPTimeInfo data
+    machine_sub -> msg_broker:
+    deactivate machine_sub
+end
+msg_broker --> machine_pub
+
+deactivate msg_broker
+
+@enduml
diff --git a/docs/time/_assets/mw/mw_class.puml b/docs/time/_assets/mw/mw_class.puml
new file mode 100644
index 0000000..ce11777
--- /dev/null
+++ b/docs/time/_assets/mw/mw_class.puml
@@ -0,0 +1,37 @@
+@startuml mw_time_svt_class_diagram
+
+title mw::time::svt: Class Diagram
+
+legend top left
+    |= Color            |= Description                     |
+    | <#LightGreen>     | Middleware components            |
+    | <#LightPink>      | IPC components                   |
+endlegend
+
+
+class "TimeInfo" as time_info #Beige {
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+    +sync_fup_data: int
+    +pdelay_data: int
+}
+
+class "TimeStatus" as time_status #LightGreen {
+    +ptp: uint64
+    +status: int
+}
+
+class "IPCMachine:receiver" as ipc_machine_receiver #LightPink {
+    +receive(): TimeInfo
+}
+
+class "score::time::svt" as mw_svt #LightGreen {
+    +Now(): TimeStatus
+}
+
+ipc_machine_receiver --> time_info : processes
+mw_svt *-- ipc_machine_receiver : contains
+mw_svt --> time_status : provides
+
+@enduml
diff --git a/docs/time/_assets/mw/mw_time_receive_seq.puml b/docs/time/_assets/mw/mw_time_receive_seq.puml
new file mode 100644
index 0000000..01ca54b
--- /dev/null
+++ b/docs/time/_assets/mw/mw_time_receive_seq.puml
@@ -0,0 +1,41 @@
+@startuml mw_time_receive_seq_diagram
+
+title mw::time::svt: Providing new Vehicle Time to Applications
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+autoactivate on
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightPink>   | IPC components                |
+    |<#LightSalmon> | Client Application            |
+    |<#LightGreen>  | Middleware components         |
+endlegend
+
+box Application #e6ffe6
+    participant "Business logic" as app #LightSalmon
+    participant "score::time::svt" as mw_svt #LightGreen
+    participant "shared_buffer" as mw_buffer #LightGreen
+    participant "worker\nthread" as mw_worker #LightGreen
+    participant "IPCMachine:receiver" as ipc_receiver #LightPink
+end box
+
+loop each 50 msec
+    mw_worker -> ipc_receiver: receive()
+    ipc_receiver --> mw_worker: TimeInfo
+    mw_worker --> mw_buffer: store TimeInfo
+end
+
+app -> mw_svt: Now()
+mw_svt -> mw_buffer: read()
+mw_buffer --> mw_svt: TimeInfo
+mw_svt -> mw_svt: handleNewData()
+note right
+    Adjusts the ptp time with current local time
+    and provides the current time to the application.
+end note
+mw_svt --> app: Current Vehicle Time
+
+@enduml
diff --git a/docs/time/_assets/mw/mw_time_receive_simple_seq.puml b/docs/time/_assets/mw/mw_time_receive_simple_seq.puml
new file mode 100644
index 0000000..ca27df7
--- /dev/null
+++ b/docs/time/_assets/mw/mw_time_receive_simple_seq.puml
@@ -0,0 +1,33 @@
+@startuml mw_time_receive_simple_seq_diagram
+
+title mw::time::svt: Providing new Vehicle Time to Applications (simplified)
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+autoactivate on
+
+legend top left
+    |= Color        |= Description                  |
+    |<#LightPink>   | IPC components                |
+    |<#LightSalmon> | Client Application            |
+    |<#LightGreen>  | Middleware components         |
+endlegend
+
+box Application #e6ffe6
+    participant "Business logic" as app #LightSalmon
+    participant "score::time::svt" as mw_svt #LightGreen
+    participant "IPCMachine:receiver" as ipc_receiver #LightPink
+end box
+
+app -> mw_svt: Now()
+mw_svt -> ipc_receiver: receive()
+ipc_receiver --> mw_svt: TimeInfo
+mw_svt -> mw_svt: handleNewData()
+note right
+    Adjusts the ptp time with current local time
+    and provides the current time to the application.
+end note
+mw_svt --> app: Current Vehicle Time
+
+@enduml
diff --git a/docs/time/_assets/ptp_machine/ptp_machine_class.puml b/docs/time/_assets/ptp_machine/ptp_machine_class.puml
new file mode 100644
index 0000000..49b3f2c
--- /dev/null
+++ b/docs/time/_assets/ptp_machine/ptp_machine_class.puml
@@ -0,0 +1,64 @@
+@startuml ptp_machine_class_diagram
+
+title PTPMachine: Class Diagram
+
+legend top left
+    |= Color            |= Description                 |
+    | <#Beige>          | Base classes                 |
+    | <#Wheat>          | PtpMachine                   |
+endlegend
+
+class "PtpTimeInfo" as time_info #Beige {
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+}
+
+abstract class "BaseMachine" as base_machine #Beige {
+    +GetName(): string
+    +Init(): bool
+}
+
+abstract class "ProactiveMachine" as proactive_machine #Beige {
+    +Start(): void
+    +Stop(): void
+}
+
+abstract class "PeriodicMachine" as periodic_machine #Beige {
+    #PeriodicTask(): void
+}
+
+abstract class "Producer<T>" as producer #Beige {
+    +SetPublishCallback(callback): void
+    #Publish(data: T): void
+}
+
+class "PTPMachine<PTPEngine>" as ptp_machine #Wheat {
+    -engine_impl_: PTPEngine*
+    -publish_callback_: function
+    +Init(): bool
+    +SetPublishCallback(callback): void
+    #PeriodicTask(): void
+}
+
+class "GPTPEngine" as gptp_engine #Wheat {
+    +Initialize(): bool
+    +Deinitialize(): void
+    +ReadPTPSnapshot(): PtpTimeInfo
+}
+
+base_machine <|-- proactive_machine
+proactive_machine <|-- periodic_machine
+periodic_machine <|-- ptp_machine
+producer <|.. ptp_machine
+
+ptp_machine *-- gptp_engine : uses
+
+ptp_machine --> time_info : produces
+
+note right of gptp_engine
+    Wrapps the platfrom specific
+    GPTP stack interaction logic
+end note
+
+@enduml
diff --git a/docs/time/_assets/ptp_machine/ptp_machine_get_new_data_seq.puml b/docs/time/_assets/ptp_machine/ptp_machine_get_new_data_seq.puml
new file mode 100644
index 0000000..64e48d0
--- /dev/null
+++ b/docs/time/_assets/ptp_machine/ptp_machine_get_new_data_seq.puml
@@ -0,0 +1,55 @@
+@startuml ptp_machine_data_publishing
+
+title PTPMachine: Periodic Data Publishing Workflow
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color           |= Description         |
+    | <#PaleTurquoise> | MessageBroker        |
+    | <#Wheat>         | PtpMachine           |
+    | <#LightBlue>     | ControlFlowDivider   |
+endlegend
+
+participant "PtpMachine" as ptp_machine #Wheat
+participant "PtpEngine" as engine #Wheat
+participant "MessageBroker" as broker #PaleTurquoise
+participant "ControlFlowDivider" as cfd #LightBlue
+
+loop periodic (e.g., every 50ms)
+    activate ptp_machine
+    ptp_machine -> ptp_machine : PeriodicTask()
+
+    ptp_machine -> engine : ReadPTPSnapshot()
+    activate engine
+    note right of engine
+        Retrieve current PTP data:
+        - PTP time
+        - Synchronization status
+        - Additional metadata
+    end note
+    engine --> ptp_machine : PtpTimeInfo
+    deactivate engine
+
+    ptp_machine -> ptp_machine : Publish(data)
+    ptp_machine -> broker : publish_callback_(data)
+    activate broker
+    note right
+        Invoke registered callback
+        to publish via MessageBroker
+    end note
+
+    broker -> broker : OnNewData("in_ptp_data", data)
+    broker -> cfd : subscription.callback_(data)
+    activate cfd
+    cfd -> cfd : OnMessage(data)
+    cfd --> broker
+    deactivate cfd
+    broker --> ptp_machine
+    deactivate broker
+    deactivate ptp_machine
+end
+
+@enduml
diff --git a/docs/time/_assets/ptp_machine/ptp_machine_init_seq.puml b/docs/time/_assets/ptp_machine/ptp_machine_init_seq.puml
new file mode 100644
index 0000000..619602f
--- /dev/null
+++ b/docs/time/_assets/ptp_machine/ptp_machine_init_seq.puml
@@ -0,0 +1,79 @@
+@startuml ptp_machine_initialization
+
+title PTPMachine: Initialization Sequence
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                  |
+    | <#LightCyan>  | TimeDaemon members            |
+    | <#PaleTurquoise> | MessageBroker              |
+    | <#Wheat>      | PtpMachine                    |
+endlegend
+
+participant "TimeBaseHandler" as tb_handler #LightCyan
+participant "PTPMachine" as ptp_machine #Wheat
+participant "PTPEngine" as engine #Wheat
+participant "MessageBroker" as broker #PaleTurquoise
+
+== PTPMachine Construction ==
+
+tb_handler -> ptp_machine ** : create(name, interval)
+activate tb_handler
+activate ptp_machine
+ptp_machine -> engine ** : create PTP engine
+note right of engine
+    Initialize engine interface
+    for PTP stack communication
+end note
+ptp_machine --> tb_handler
+deactivate ptp_machine
+deactivate tb_handler
+
+== PTPMachine Initialization ==
+
+tb_handler -> ptp_machine : Init()
+activate tb_handler
+activate ptp_machine
+ptp_machine -> engine : Initialize()
+activate engine
+note right
+    Establish connection
+    to PTP daemon
+end note
+engine --> ptp_machine
+deactivate engine
+ptp_machine --> tb_handler
+deactivate ptp_machine
+deactivate tb_handler
+
+== Setup Producer ==
+
+tb_handler -> broker : AddProducer("in_ptp_data", ptp_machine)
+activate tb_handler
+activate broker
+broker -> ptp_machine : SetPublishCallback(broker::OnNewData)
+activate ptp_machine
+ptp_machine --> broker
+deactivate ptp_machine
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+== Start Periodic Operation ==
+
+tb_handler -> ptp_machine : Start()
+activate tb_handler
+activate ptp_machine
+ptp_machine -> ptp_machine : Start periodic thread
+note right
+    Begin periodic PTP
+    data retrieval
+end note
+ptp_machine --> tb_handler
+deactivate ptp_machine
+deactivate tb_handler
+
+@enduml
diff --git a/docs/time/_assets/sad_deployment.puml b/docs/time/_assets/sad_deployment.puml
new file mode 100644
index 0000000..ddaa1e7
--- /dev/null
+++ b/docs/time/_assets/sad_deployment.puml
@@ -0,0 +1,39 @@
+@startuml sad_deployment_diagram
+
+title Deployment view
+
+node "IPN1x" {
+    node "Application Layer" {
+        [Business logic] as app_bl
+        [mw::time::svt] <<library>> as mw
+    }
+    node "Diagnostic App Layer" {
+        [Diag jobs business logic] as diag_bl
+        [mw::time::svt::ext] <<library>> as mw_ext
+    }
+    node "PTP Daemon" {
+        [ptpd] <<daemon>> as ptpd
+    }
+    node "VehicleTimeDaemon" {
+        [VerificationMachine]  as verification_machine
+        [PTP machine] as ptp_machine
+    }
+    [EMAC] <<hw clock>> as hw_counter
+}
+node "Time Grand Master" {
+    [PTP Grandmaster Clock] <<device>> as ptp_gm
+}
+[DLT] <<records>> as dlt_records
+
+
+ptp_gm -[#purple]-> ptpd : PTP sync messages
+ptpd ..> hw_counter : Updates local hw timer
+ptpd -[#blue]-> ptp_machine : PTP time updates\n(via shmem and devctl)
+ptp_machine -[#green]-> verification_machine: Time information
+verification_machine -[#green]-> mw: Time information
+verification_machine -[#green]-> mw_ext: Time information
+verification_machine -[#green]-> dlt_records: Data for post analysis
+mw-[#orange]-> app_bl : Now()
+mw_ext-[#orange]-> diag_bl : Now(), Callbacks()
+
+@enduml
diff --git a/docs/time/_assets/ver_machine/ver_class.puml b/docs/time/_assets/ver_machine/ver_class.puml
new file mode 100644
index 0000000..299b6f4
--- /dev/null
+++ b/docs/time/_assets/ver_machine/ver_class.puml
@@ -0,0 +1,73 @@
+@startuml verification_machine_class_diagram
+
+title VerificationMachine: Class Diagram
+
+legend top left
+    |= Color         |= Description          |
+    | <#Beige>       | Base classes          |
+    | <#Lavender>    | VerificationMachine   |
+endlegend
+
+class "PtpTimeInfo" as time_info #Beige {
+    +ptp: uint64
+    +local_time: uint64
+    +status: int
+}
+
+abstract class "BaseMachine" as base_machine #Beige {
+    +GetName(): string
+    +Init(): bool
+}
+
+abstract class "ReactiveMachine" as reactive_machine #Beige {
+}
+
+abstract class "Consumer<T>" as consumer #Beige {
+    +OnMessage(data: T): void
+}
+
+abstract class "Producer<T>" as producer #Beige {
+    +SetPublishCallback(callback): void
+    #Publish(data: T): void
+}
+
+class "VerificationMachine<DataType>" as verification_machine #Lavender {
+    -pipeline_: vector<VerificationStage*>
+    -publish_callback_: function
+    +OnMessage(data: DataType): void
+    +SetPublishCallback(callback): void
+}
+
+abstract class "VerificationStage<DataType>" as verification_stage #Lavender {
+    -next_stage_: VerificationStage*
+    +Process(data: DataType): DataType
+    +SetNext(next: VerificationStage*): void
+    #DoValidation(data: DataType&): void
+}
+
+class "SynchronizationValidator" as sync_validator #Lavender {
+    #DoValidation(data: PtpTimeInfo&): void
+}
+
+class "TimeoutValidator" as timeout_validator #Lavender {
+    #DoValidation(data: PtpTimeInfo&): void
+}
+
+class "TimeJumpsValidator" as timejump_validator #Lavender {
+    #DoValidation(data: PtpTimeInfo&): void
+}
+
+base_machine <|-- reactive_machine
+reactive_machine <|-- verification_machine
+consumer <|.. verification_machine
+producer <|.. verification_machine
+
+verification_machine *-- verification_stage : pipeline
+verification_stage <|-- sync_validator
+verification_stage <|-- timeout_validator
+verification_stage <|-- timejump_validator
+verification_stage o-- verification_stage : next_stage_
+
+verification_machine --> time_info : processes
+
+@enduml
diff --git a/docs/time/_assets/ver_machine/ver_init_seq.puml b/docs/time/_assets/ver_machine/ver_init_seq.puml
new file mode 100644
index 0000000..9e4a0bc
--- /dev/null
+++ b/docs/time/_assets/ver_machine/ver_init_seq.puml
@@ -0,0 +1,66 @@
+@startuml verification_machine_init_sequence_diagram
+
+title VerificationMachine: Initialization Sequence
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color          |= Description           |
+    |<#LightCyan>     | TimeDaemon members     |
+    |<#PaleTurquoise> | MessageBroker          |
+    |<#Lavender>      | VerificationMachine    |
+endlegend
+
+participant "TimeBaseHandler" as tb_handler #LightCyan
+participant "VerificationMachine" as verif_machine #Lavender
+participant "Validators" as validators #Lavender
+participant "MessageBroker" as broker #PaleTurquoise
+
+== VerificationMachine Construction ==
+
+tb_handler -> verif_machine ** : create(name, validator_factories...)
+activate tb_handler
+activate verif_machine
+
+verif_machine -> validators ** : Create validator pipeline
+note right of validators
+    Chain of Responsibility:
+    - SynchronizationValidator
+    - TimeoutValidator
+    - TimeJumpsValidator
+end note
+
+verif_machine -> verif_machine : SetupPipeline()
+note right
+    Link validators in chain:
+    stage1.SetNext(stage2)
+    stage2.SetNext(stage3)
+end note
+
+verif_machine --> tb_handler : SvtVerificationMachine*
+deactivate verif_machine
+deactivate tb_handler
+
+== Setup Connections ==
+
+tb_handler -> broker : AddSubscriber("raw_ptp_data", verif_machine)
+activate tb_handler
+activate broker
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+tb_handler -> broker : AddProducer("validated_ptp_data", verif_machine)
+activate tb_handler
+activate broker
+broker -> verif_machine : SetPublishCallback(broker::OnNewData)
+activate verif_machine
+verif_machine --> broker
+deactivate verif_machine
+broker --> tb_handler
+deactivate broker
+deactivate tb_handler
+
+@enduml
diff --git a/docs/time/_assets/ver_machine/ver_verification_seq.puml b/docs/time/_assets/ver_machine/ver_verification_seq.puml
new file mode 100644
index 0000000..09f5c4b
--- /dev/null
+++ b/docs/time/_assets/ver_machine/ver_verification_seq.puml
@@ -0,0 +1,57 @@
+@startuml verification_machine_verification_sequence_diagram
+
+title VerificationMachine: Validation Workflow
+
+hide footbox
+
+autonumber "<font color=red><b>[00]"
+
+legend top left
+    |= Color        |= Description                   |
+    |<#PaleTurquoise> | MessageBroker                |
+    |<#LightBlue>   | ControlFlowDivider             |
+    |<#Lavender>    | VerificationMachine            |
+    |<#LightPink>   | IPC components                 |
+endlegend
+
+participant "ControlFlowDivider" as cfd #LightBlue
+participant "MessageBroker" as broker #PaleTurquoise
+participant "VerificationMachine" as verif_machine #Lavender
+participant "Validator Pipeline" as pipeline #Lavender
+participant "IPCPublisher" as ipc #LightPink
+
+cfd -> broker : publish("raw_ptp_data", data)
+activate broker
+broker -> verif_machine : OnMessage(data)
+activate verif_machine
+
+verif_machine -> pipeline : Process(data)
+activate pipeline
+note right of pipeline
+    Chain of Responsibility:
+    Each validator processes data
+    and passes to next stage:
+    1. SynchronizationValidator
+    2. TimeoutValidator
+    3. TimeJumpsValidator
+end note
+
+pipeline -> pipeline : Stage 1: DoValidation(data)
+pipeline -> pipeline : Stage 2: DoValidation(data)
+pipeline -> pipeline : Stage 3: DoValidation(data)
+
+pipeline --> verif_machine : validated data
+deactivate pipeline
+
+verif_machine -> verif_machine : Publish(data)
+verif_machine -> broker : publish_callback_(data)
+deactivate verif_machine
+broker -> broker : OnNewData("validated_ptp_data", data)
+broker -> ipc : subscription.callback_(data)
+activate ipc
+ipc --> broker
+deactivate ipc
+broker --> cfd
+deactivate broker
+
+@enduml
diff --git a/docs/time/index.rst b/docs/time/index.rst
new file mode 100644
index 0000000..1f47e89
--- /dev/null
+++ b/docs/time/index.rst
@@ -0,0 +1,983 @@
+Concept for TimeDaemon
+======================
+
+.. contents:: Table of Contents
+   :depth: 3
+   :local:
+
+TimeDaemon concept
+------------------
+
+Use Cases
+~~~~~~~~~
+
+TimeDaemon is the non Autosar adaptive process who is intended to get the Vehicle Time from the ptp slave daemon (ptpd or any other), verify and validate the timepoints and distribute time information across the clients.
+
+More precisely we can specify the following use cases for the time daemon:
+
+1. Providing current Vehicle time to different applications
+2. Setting the synchronization qualifier (aka Synchronized, Timeout, so on)
+3. Providing needed information for diagnostics
+4. Providing needed information for addition verification, ex SafeCarTime
+
+The raw architectural diagram is represented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/sad_deployment.puml
+   :alt: Raw architectural diagram
+
+.. raw:: html
+
+   </div>
+
+Components decomposition
+~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The design consists of several sw components:
+
+1. `Application <#application-sw-component>`_
+2. `Message Broker <#message-broker-sw-component>`_
+3. `ControlFlowDivider <#controlflowdivider-sw-component>`_
+4. `PTP Machine <#ptp-machine-sw-component>`_
+5. `Verification Machine <#verification-machine-sw-component>`_
+6. `IPC Machine <#ipc-machine-sw-component>`_
+7. `score::time::svt <#score-time-synchronizedvehicletime-sw-component>`_
+
+Deployment view
+~~~~~~~~~~~~~~~
+
+The design deployment is represented on the following diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/dd_deployment.puml
+   :alt: Deployment View
+
+.. raw:: html
+
+   </div>
+
+Class view
+~~~~~~~~~~
+
+Main classes and components are presented on this diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/dd_class.puml
+   :alt: Class View
+   :width: 100%
+   :align: center
+
+.. raw:: html
+
+   </div>
+
+Data and control flow
+~~~~~~~~~~~~~~~~~~~~~
+
+The Data and Control flow are presented in the following diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/dd_data_control_flow.puml
+   :alt: Data and Control flow View
+
+.. raw:: html
+
+   </div>
+
+On this view you could see several "workers" scopes:
+
+1. PTP retrieving scope
+2. PTPTimeInfo handling scope
+3. PTPTimeInfo receiving on Application side scope
+
+Each control flow is implemented with the dedicated thread or process and is independent form another ones.
+
+Control flows
+^^^^^^^^^^^^^
+
+PTP retrieving scope
+''''''''''''''''''''
+
+This control flow is responsible for the:
+
+1. retrieve the latest information from the ptp stack and
+2. provide it to the ``PTPTimeInfo handling`` control flow
+
+PTPTimeInfo handling scope
+'''''''''''''''''''''''''''
+
+This control flow is responsible for the:
+
+1. Validate the time information, provided by the ``PTP retrieving`` workflow and
+2. publish it to the ``Applications`` via some IPC
+
+PTPTimeInfo receiving on Application side scope
+''''''''''''''''''''''''''''''''''''''''''''''''
+
+This control flow is responsible for the:
+
+1. Propagate the time information from the ``PTPTimeInfo handling`` to the business logic of the applications.
+
+Data types or events
+^^^^^^^^^^^^^^^^^^^^
+
+There are also several data types, which components are communicating to each other:
+
+Raw ptp data
+''''''''''''
+
+``raw_ptp_data`` is the data, which is provided by ``PTPMachine`` component and is just the raw data from ptp stack. is handled in the "PTP retrieving scope"
+
+Input ptp data
+''''''''''''''
+
+``input_ptp_data`` is the same data as `raw_ptp_data <#raw-ptp-data>`_ but which is handled already in "PTPTimeInfo handling scope"
+
+Verified ptp data
+'''''''''''''''''
+
+``verified_ptp_data`` is the `input_ptp_data <#input-ptp-data>`_ which was verified according to the business logic and updated accordingly. This data should be published to the Applications.
+
+SW Components decomposition
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Application SW component
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The ``Application`` component is the main entry point for the ``TimeDaemon``. It is responsible for orchestrating the overall lifecycle and initialization of all daemon components.
+
+The ``TimebaseHandler`` component is an timebase-specific logic implementation. There might be several handlers available in the ``Application`` per amount of timebases supported. This separation allows for different timebase implementations while maintaining a consistent application structure.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``Application`` has the following requirements:
+
+- The ``Application`` shall implement the ``Initialize()`` method to create and initialize all daemon components
+- The ``Application`` shall implement the ``Run()`` method to start all components and wait for termination
+- The ``Application`` shall connect components to the ``MessageBroker`` by setting up all required subscriptions during initialization stage
+- The ``Application`` shall support extension for different timebases.
+
+Class view
+''''''''''
+
+The Class Diagram is presented below:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/app/app_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+Initialization flow
+'''''''''''''''''''
+
+During initialization, the ``Application`` uses the ``MachineFactory`` to create, configure and subscribe all components in a specific order:
+
+- Create the ``MessageBroker`` first, as other components depend on it
+- Create ProactiveMachines (``PtpMachine``, ``ControlFlowDivider``) that drive system behavior
+
+  - Initialize each component
+  - Set up MessageBroker subscriptions to component notifications
+  - Set up component subscriptions to MessageBroker topics
+
+- Create ReactiveMachines (``VerificationMachine``, ``IPCMachine``) that respond to events
+
+  - Initialize each component
+  - Set up MessageBroker subscriptions to component notifications
+  - Set up component subscriptions to MessageBroker topics
+
+The initialization workflow is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/app/app_init_seq.puml
+   :alt: Initialization workflow
+
+.. raw:: html
+
+   </div>
+
+Execution and shutdown flow
+''''''''''''''''''''''''''''
+
+During execution, the ``Application``:
+
+- Starts all ``ProactiveMachines`` in the correct order
+- Monitors the stop token for termination requests
+- When termination is requested, stops all ``ProactiveMachines`` in reverse order
+
+The execution and shutdown workflow is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/app/app_workflow_seq.puml
+   :alt: Execution workflow
+
+.. raw:: html
+
+   </div>
+
+Message Broker SW component
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The ``Message Broker`` component is the central communication hub that implements the Publish-Subscribe pattern within the ``TimeDaemon``. It enables decoupled communication between components by managing topics and distributing messages to interested subscribers.
+
+The component maintains a registry of topics and their subscribers, delivering messages to all registered subscribers when a component publishes to a topic. This decoupling allows components to evolve independently without direct dependencies on each other.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``Message Broker`` has the following requirements:
+
+- The ``Message Broker`` shall maintain a registry of topics and their subscribers
+- The ``Message Broker`` shall allow components to subscribe to topics of interest
+- The ``Message Broker`` shall distribute messages to all subscribers when a topic is published to
+
+Class view
+''''''''''
+
+The Class Diagram is presented below:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/msg_broker/msg_broker_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+Initialization flow
+'''''''''''''''''''
+
+During initialization, all machine objects, see ``BaseMachine``, the ``Application`` component needs to subscribe machines to ``Message Broker`` to the topics of interest.
+
+The initialization workflow is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/msg_broker/msg_broker_init_seq.puml
+   :alt: Initialization workflow
+
+.. raw:: html
+
+   </div>
+
+Message flow
+''''''''''''
+
+The message flow through the ``Message Broker`` is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/msg_broker/msg_broker_workflow_seq.puml
+   :alt: Message DiagramFlow
+
+.. raw:: html
+
+   </div>
+
+Concurrency aspects
+'''''''''''''''''''
+
+The ``Message Broker`` doesn't provide any synchronization between the publish-callback invoking processes.
+Moreover, the callback invoke will happened in the scope of the thread, where the ``publish`` method is called.
+To separate the control flows, the `ControlFlowDivider <#controlflowdivider-sw-component>`_ shall be used
+
+Scalability
+'''''''''''
+
+The ``Message Broker`` can be extended to support configuration-driven subscriptions, where topic relationships are defined in configuration files rather than hardcoded.
+
+ControlFlowDivider SW component
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The ``ControlFlowDivider`` component is responsible for separating control (execution) flows within the ``TimeDaemon`` and providing the execution control flow for the data processing. It contains dedicated threads where data is published to the ``Message Broker``, ensuring that blocking operations in one component do not affect the execution of other components and data missing is not affecting the data analysis in processing pipeline.
+
+This component acts as a crucial intermediary that maintains the responsiveness of the system by decoupling the execution contexts of different operations, particularly between the PTP data retrieval and the time data processing pipelines.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``ControlFlowDivider`` has the following requirements:
+
+- The ``ControlFlowDivider`` shall provide separate execution threads for different control flows
+- The ``ControlFlowDivider`` shall isolate components from execution time variations in other components
+- The ``ControlFlowDivider`` shall maintain consistent data publishing rates to the subscribers
+- - The ``ControlFlowDivider`` shall push the last received data to the subscribers if there is no new data for some time with the predefined rate, to avoid data missing in the processing pipeline
+- The ``ControlFlowDivider`` shall enable periodic processing of the pipeline through consistent event generation
+- The ``ControlFlowDivider`` shall buffer incoming data from fast producers
+
+Class view
+''''''''''
+
+The Class Diagram is presented below:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ctrlflow/ctrlflow_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+Initialization flow
+'''''''''''''''''''
+
+During initialization, the ``ControlFlowDivider`` performs the following steps:
+
+- Initialize internal data structures (queue, mutex, condition variable)
+- Create a worker thread to process data independently
+- Start the worker thread which enters a waiting state
+
+The initialization workflow is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ctrlflow/ctrlflow_init_seq.puml
+   :alt: Initialization workflow
+
+.. raw:: html
+
+   </div>
+
+Message flow
+''''''''''''
+
+When the ``ControlFlowDivider`` receives new data from the ``PTP Machine`` via the ``Message Broker``, it processes it through the following workflow:
+
+1. The ``Message Broker`` executes the onNewData callback and provides the new data
+2. The data is placed in a thread-safe queue and exists from the callback
+3. The worker thread wakes up, retrieves the data from the queue and
+4. The worker thread publishes the retrieved data to the `input_ptp_data <#input-ptp-data>`_ topic
+5. if there was no data for some timeout, the worker shall published the empty data to the `input_ptp_data <#input-ptp-data>`_ topic.
+
+This separation of control flows ensures that slow or blocking operations in the PTP stack communication do not affect the responsiveness of time data processing in the ``TimeDaemon``.
+
+The execution workflow is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ctrlflow/ctrlflow_workflow_seq.puml
+   :alt: Execution workflow
+
+.. raw:: html
+
+   </div>
+
+PTP Machine SW component
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The ``PTP Machine`` component shall retrieve all needed information from the ptp stack (ex ``ptpd``) and provide it to the ``Message Broker`` for routing.
+All communication with the ptp stack ight use ``devctl`` calls, which take some time, thus these calls shall be done in the dedicated thread.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``PTP Machine`` has the following requirements:
+
+- The ``PTP Machine`` shall retrieve the latest time information from the PTP stack (e.g., ``ptpd``)
+- The ``PTP Machine`` shall publish retrieved time information to the ``Message Broker`` using the defined topic
+- The ``PTP Machine`` shall format data according to the ``PTPTimeInfo`` structure required by downstream components
+- The ``PTP Machine`` shall retrieve time information at a consistent rate to maintain time synchronization
+- The ``PTP Machine`` shall maintain consistent publishing rates for time data even when experiencing delays in PTP stack communication.
+- The ``PTP Machine`` shall support exchangeability with different PTP stack implementations
+
+Class view
+''''''''''
+
+The Class Diagram is presented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ptp_machine/ptp_machine_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+As long as it wraps the particular communication with the ptp stack, the implementations should be easily exchangeable with another one in case of stack change.
+
+Component initialization
+'''''''''''''''''''''''''
+
+During initialization the ``PTP Machine`` shall initialize the ptp stack to be able to communicate with it.
+
+The initialization workflow is described below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ptp_machine/ptp_machine_init_seq.puml
+   :alt: Initialization workflow
+
+.. raw:: html
+
+   </div>
+
+Publish new data
+''''''''''''''''
+
+After ``PTP Machine`` collects new data from the ptp stack, the component shall publish it to the ``Message Broker`` as `raw-ptp-data <#raw-ptp-data>`_.
+
+The publish workflow is described below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ptp_machine/ptp_machine_get_new_data_seq.puml
+   :alt: Publish workflow
+
+.. raw:: html
+
+   </div>
+
+Verification Machine SW component
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The ``Verification Machine`` component is responsible for validating and qualifying the time information received from the ``PTP Machine``. It applies various validation rules to ensure the time data meets quality requirements before distribution to applications.
+
+The component implements a pipeline pattern where each stage performs a specific validation and adds appropriate qualifiers to the time data. This modular design allows for easy extension with additional validation steps.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``Verification Machine`` has the following requirements:
+
+- The ``Verification Machine`` shall validate and qualify time information received from the PTP Machine
+- The ``Verification Machine`` shall validate if the time base is synchronized state
+- The ``Verification Machine`` shall validate if the time base is in timeout state
+- The ``Verification Machine`` shall validate timestamp for time jumps based on local clock
+- The ``Verification Machine`` shall subscribe to the `input_ptp_data <#input-ptp-data>`_ topic via the ``Message Broker``
+- The ``Verification Machine`` shall publish verified time data to the ``Message Broker`` using the `verified-ptp-data <#verified-ptp-data>`_ topic
+- The ``Verification Machine`` shall support extensibility to add new validation stages in the pipeline
+
+Class view
+''''''''''
+
+The Class Diagram is presented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ver_machine/ver_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+Component initialization
+'''''''''''''''''''''''''
+
+During initialization, the ``Verification Machine`` performs the following steps:
+
+1. Set up the validation pipeline by creating and connecting validation stages
+
+The component shall be subscribed by the ``Application`` to the `input_ptp_data <#input-ptp-data>`_ topic of the ``MessageBroker``
+
+The initialization workflow is represented in the following sequence diagram:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ver_machine/ver_init_seq.puml
+   :alt: Initialization workflow
+
+.. raw:: html
+
+   </div>
+
+Data verification workflow
+'''''''''''''''''''''''''''
+
+When the ``Verification Machine`` receives new PTP data, it processes it through the validation pipeline:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ver_machine/ver_verification_seq.puml
+   :alt: Validation pipeline
+
+.. raw:: html
+
+   </div>
+
+IPC Machine SW component
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The ``IPC Machine`` component shall get the `verified-ptp-data <#verified-ptp-data>`_ from the ``Verification Machine`` and provide it to the ``score::time::svt`` through shared memory or other ipc mechanisms.
+
+The component provides two sub components: publisher and receiver to be deployed on the TimeDaemon and Application sides accordingly.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``IPC Machine`` has the following requirements:
+
+- The ``IPC Machine`` shall provide verified time data to the ``score::time::svt`` component through shared memory or other IPC mechanisms
+- The ``IPC Machine`` shall create and initialize the IPC
+- The ``IPC Machine`` shall support multiple client applications accessing the same time data
+- The ``IPC Machine`` shall subscribe to the `verified_ptp_data <#verified-ptp-data>`_ topic via the ``Message Broker``
+
+Class view
+''''''''''
+
+The Class Diagram is presented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ipc/ipc_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+Component initialization
+'''''''''''''''''''''''''
+
+Initialization is divided to two parts:
+
+1. Initialization on the TimeDaemon side
+2. Initialization on the Application side
+
+Important thing, the shared memory shall be created by the ``TimeDaemon``, which means the Application should wait until the ``shmem`` will be created and only then open, map and read it.
+
+The main workflow is described below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ipc/ipc_init_seq.puml
+   :alt: Main workflow
+
+.. raw:: html
+
+   </div>
+
+The component shall be subscribed during initialization by the ``Application`` on the `verified-ptp-data <#verified-ptp-data>`_ updates from the ``Message Broker``
+
+Publish new data
+''''''''''''''''
+
+When ``IPC Machine`` receives the new `verified-ptp-data <#verified-ptp-data>`_ from Message Broker, it shall serialize data and store it to the shared memory.
+
+As long as there are different use cases by using it, like:
+
+1. Get current Vehicle time
+2. Get data for diagnostics
+
+All ``PTPTimeInfo`` data (or almost all) shall be shared across applications.
+
+The publish workflow is described below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ipc/ipc_publish_seq.puml
+   :alt: Publish workflow
+
+.. raw:: html
+
+   </div>
+
+Receive data
+''''''''''''
+
+From Application side the receiver shall read the ``shared_memory`` and provide the data to the caller.
+
+The receive workflow is described below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/ipc/ipc_receive_seq.puml
+   :alt: Receive workflow
+
+.. raw:: html
+
+   </div>
+
+score::time::SynchronizedVehicleTime SW Component
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+``score::time::svt`` is the interface towards Applications, how they could get the access to the Vehicle Time.
+
+Component requirements
+''''''''''''''''''''''
+
+The ``score::time::svt`` has the following requirements:
+
+- The ``score::time::svt`` shall expose vehicle time amd it synchronization status to applications
+- The ``score::time::svt`` shall retrieve time data from ``IPC Machine`` receiver component
+- The ``score::time::svt`` shall adjust vehicle time with local clock to provide accurate timestamps
+- The ``score::time::svt`` shall support fast and low-latency time access via the ``Now()`` method
+
+Class view
+''''''''''
+
+The Class Diagram is presented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/mw/mw_class.puml
+   :alt: Class Diagram
+
+.. raw:: html
+
+   </div>
+
+Receive data
+''''''''''''
+
+In case of receiving data, the ``Application`` shall just call ``score::time::svt::Now()`` and it shall return the latest published Vehicle Time, which is already adjusted with local clock.
+
+To do so, in the ``score::time::svt`` there is a thread, who polls for new data the ``IPCMachine::receiver`` and put the data to the process-internal shared buffer (memory), from where it is being read on ``score::time::svt::Now()`` call.
+
+The main workflow is described below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/mw/mw_time_receive_seq.puml
+   :alt: Receive data workflow
+
+.. raw:: html
+
+   </div>
+
+This design guarantees very low latency of the executing the ``score::time::svt::Now()`` function but brings additional efforts for the thread, memory buffer, synchronizing and so on.
+
+Receive data (simplified)
+''''''''''''''''''''''''''
+
+As an alternative design, the receiving concept could be simplified and ``score::time::svt::Now()`` could directly invoke the ``IPCMachine::receiver`` call, adjust the ``Vehicle time`` and return it to the ``Application``.
+
+The design is represented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/mw/mw_time_receive_simple_seq.puml
+   :alt: Receive data (simplified) workflow
+
+.. raw:: html
+
+   </div>
+
+In this case, there will be no need for additional thread, shared buffer and synchronization, but the ``score::time::svt::Now()`` call will take longer. To decide which approach to use, additional tests shall be
+
+Deployment
+''''''''''
+
+The implementation of ``score::time::svt::details::timed`` could be placed in parallel to other implementations, like ``score::time::svt::details::mocked`` one and could be selected by Bazel select. Also it will ease the integration process.
+
+Logging configuration
+~~~~~~~~~~~~~~~~~~~~~
+
+The daemon should have the following logging contexts:
+
+.. list-table:: Logging Contexts
+   :header-rows: 1
+   :widths: 30 20 50
+
+   * - component
+     - App/Context ID
+     - Comments
+   * - TimeDaemon
+     - TDON
+     - **T**\ ime\ **D**\ aem\ **ON**
+   * - Application
+     - TDAP
+     - **T**\ ime\ **D**\ aemon **AP**\ plication
+   * - MessageBroker
+     - TDMB
+     - **T**\ ime\ **D**\ aemon **M**\ essage\ **B**\ roker
+   * - ControlFlowDivider
+     - TDCD
+     - **T**\ ime\ **D**\ aemon **C**\ ontrolFlow\ **D**\ ivider
+   * - PTPMachine
+     - TDPM
+     - **T**\ ime\ **D**\ aemon **P**\ TP\ **M**\ achine
+   * - VerificationMachine
+     - TDVM
+     - **T**\ ime\ **D**\ aemon **V**\ erification\ **M**\ achine
+   * - IPCMachine::receiver
+     - TDIR
+     - **T**\ ime\ **D**\ aemon **I**\ PCMachine::\ **R**\ eceiver
+   * - IPCMachine::publisher
+     - TDIP
+     - **T**\ ime\ **D**\ aemon **I**\ PCMachine::\ **P**\ ublisher
+
+Variability
+~~~~~~~~~~~
+
+Configuration files
+^^^^^^^^^^^^^^^^^^^
+
+The ``TimeDaemon`` uses structured configuration files to enable customization of its runtime behavior. These data could be configured:
+
+1. Component-specific Configuration:
+
+   a. Each component can have dedicated configuration sections
+   b. Parameters such as update rates, timeouts, and thresholds can be specified
+
+2. Topic Configuration:
+
+   a. Topics for the ``Message Broker`` can be defined in configuration
+   b. Publisher and subscriber relationships can be specified externally
+   c. Component roles (publisher/subscriber) can be assigned through configuration
+
+3. File Format and Structure: The configuration files use JSON format for readability and easy parsing:
+
+.. code-block:: json
+
+   {
+     "message_broker": {
+       "topics": [
+         {
+           "name": "raw_ptp_data",
+           "publishers": ["PtpMachine"],
+           "subscribers": ["ControlFlowDivider"]
+         },
+         {
+           "name": "input_ptp_data",
+           "publishers": ["ControlFlowDivider"],
+           "subscribers": ["VerificationMachine"]
+         },
+         {
+           "name": "verified_ptp_data",
+           "publishers": ["VerificationMachine"],
+           "subscribers": ["IPCMachine"]
+         }
+       ]
+     },
+     "ptp_machine": {
+       "update_interval_ms": 50,
+       "ptp_stack_type": "ptp",
+       "ptp_stack_parameters": {
+         "device": "/dev/ptp0"
+       }
+     },
+     "control_flow_divider": {
+       "timeout_ms": 500,
+       "publishing_rate_ms": 100
+     },
+     "verification_machine": {
+       "validation_stages": ["synchronization", "timejumps", "timeout"],
+       "timejumps_parameters": {
+         "max_backward_jump_ns": 100000
+       },
+       "timeout_parameters": {
+         "threshold_ns": 100000
+       }
+     },
+     "ipc_machine": {
+       "shared_memory_name": "vehicle_time",
+       "shared_memory_size": 4096
+     }
+   }
+
+Scalability
+^^^^^^^^^^^
+
+The ``TimeDaemon``'s architecture supports scalability in the following ways:
+
+Component Extensibility:
+''''''''''''''''''''''''
+
+1. New machine components can be added by implementing the ``BaseMachine`` interface
+2. Additional validation stages can be plugged into the ``VerificationMachine`` pipeline
+3. Alternative IPC mechanisms or communication with ptp stack can be implemented by alternative the ``IPCMachine`` or ``PTPMachine`` implementation
+
+Example based on Qualified Vehicle Time integration
+'''''''''''''''''''''''''''''''''''''''''''''''''''
+
+The ``Qualified Vehicle Time`` integration extends the standard ``TimeDaemon`` architecture with:
+
+1. A ``Qualified Vehicle Time`` component that performs additional time qualification and provide new topics: ``qualified_ptp_data`` and ``diagnostic_sct_data``
+2. A dedicated IPC channel for SCT diagnostic data
+3. A ``score::time::qvt`` library for diagnostic applications
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/examples/qvt/qvt_deployment.puml
+   :alt: Deployment view
+
+.. raw:: html
+
+   </div>
+
+The ``Qualified Vehicle Time`` component is integrated into the existing processing pipeline:
+
+1. It subscribes to the `verified_ptp_data <#verified-ptp-data>`_ topic from the ``VerificationMachine``
+2. It processes and qualifies the time data with additional QVT-specific checks
+3. It publishes two types of data:
+
+   a. Qualified time data to the standard IPC Machine towards clients interested in the qualified Vehicle Time
+   b. Diagnostic data to a dedicated QVT IPC channel towards Diagnostic and Central Validator notifications
+
+The extended data flow with Qualified Vehicle Time integration is shown below:
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/examples/qvt/qvt_data_control_flow.puml
+   :alt: Data flow
+
+.. raw:: html
+
+   </div>
+
+Example based on Absolute Time integration
+''''''''''''''''''''''''''''''''''''''''''
+
+Another example of the ``TimeDaemon`` extension is the integration of an ``Absolute Time`` source, such as GNSS, to provide absolute time information alongside the relative Vehicle Time from PTP.
+
+The ``Absolute Time`` integration extends the standard ``TimeDaemon`` architecture with:
+
+1. An ``SDatMachine`` component that retrieves absolute time from GNSS via SOMEIP or other sources and provide new topics: ``absolute_time_data``
+2. A dedicated verification stage in the ``VerificationMachine`` for Absolute Time qualification
+3. A dedicated IPC channel for Absolute Time data
+4. A ``score::time::abs`` library for applications requiring absolute time on Clients side.
+
+The way how it is integrated is presented below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/examples/abs_time/abs_time_deployment.puml
+   :alt: Data flow
+
+.. raw:: html
+
+   </div>
+
+
+The control and data flow with Absolute Time integration is shown below.
+
+.. raw:: html
+
+   <div style="overflow-x: auto; max-width: 100%;">
+
+.. uml:: _assets/examples/abs_time/abs_time_data_control_flow.puml
+   :alt: Data flow
+
+.. raw:: html
+
+   </div>
+
+Using in test environment
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Using in ITF
+^^^^^^^^^^^^
+
+Normal behavior is expected.
+
+Using in Component Tests on the host
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Overview
+''''''''
+
+The ``TimeDaemon`` can be utilized in the ``Component Tests`` environment to enable comprehensive testing of time-dependent components without relying on physical PTP hardware.
+This approach allows test cases to manipulate time values and synchronization states to validate application behavior under various timing conditions.
+
+For the Component tests the ``PtpMachine::PtpEngine`` library is the only one platform-dependent.
+Thus the ``TimeDaemon`` components remain largely unchanged except for the ``PTPMachine`` component, which is replaced with an test-specific implementation that can be controlled via test cases
+This component shall:
+
+1. simulate "normal" ``PTPMachine`` behavior
+2. have the communication channel to the test case and react on the manipulations
+
+Next steps: plugin system
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The ``TimeDaemon`` could be extended with a flexible plugin system that enables dynamic component loading, configuration, subscription and extension without requiring code changes or recompilation.
+
+Plugin Architecture
+^^^^^^^^^^^^^^^^^^^
+
+The plugin system is structured around the following key elements:
+
+1. ``Component Registry``: A central registry that maintains information about available component implementations
+2. ``Component Factory``: Creates component instances based on configuration
+3. ``Plugin Manager``: Loads and initializes plugins at runtime
+4. ``Configuration-Driven Assembly``: Components and their relationships defined in configuration files
+
+Component Creation Process
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+During ``TimeDaemon`` initialization:
+
+1. The ``Plugin Manager`` loads all specified plugins from configured directories or bazel targets
+2. Each plugin registers its component factories with the registry
+3. The ``Application`` reads the component configuration
+4. For each component in the configuration:
+
+   a. The appropriate factory is retrieved from the registry
+   b. The component is created with its specified parameters
+   c. Components are connected based on the ``MessageBroker`` topic configuration
+
+ASIL-B qualification
+~~~~~~~~~~~~~~~~~~~~~
+
+Clean separation of concerns allows ``score::time::svt`` as well as ``TimeDaemon`` to be qualified according to ASIL-B requirements following ISO 26262 standard.