From 5d6a7cf4687d9248beaa654fd1a6fe510e4a855d Mon Sep 17 00:00:00 2001
From: Patrick Balsiger <frupii@gmail.com>
Date: Fri, 22 Aug 2025 16:10:59 +0200
Subject: [PATCH] docs: fix wrong documentation

---
 docs/Architecture.md | 32 +++++++++++---------------------
 1 file changed, 11 insertions(+), 21 deletions(-)

diff --git a/docs/Architecture.md b/docs/Architecture.md
index 3eafbb9..e02d2ec 100644
--- a/docs/Architecture.md
+++ b/docs/Architecture.md
@@ -177,29 +177,19 @@ The system includes automatic WiFi fallback for robust operation:
 
 ## Data Flow
 
-### Discovery Flow
+### Node Discovery
+1. **UDP Broadcast**: Nodes broadcast discovery packets on port 4210
+2. **UDP Response**: Receiving nodes responds with hostname
+3. **Registration**: Discovered nodes are added to local cluster member list
 
-```
-Node A → UDP Broadcast → Node B
-Node B → HTTP Response → Node A
-Node A → Add to Cluster → Update Member List
-```
+### Health Monitoring
+1. **Periodic Checks**: Cluster manager polls member nodes every 1 second
+2. **Status Collection**: Each node returns resource usage and health metrics
 
-### Health Monitoring Flow
-
-```
-Cluster Manager → HTTP Request → Node Status
-Node → JSON Response → Resource Information
-Cluster Manager → Update Health → Fire Events
-```
-
-### Task Execution Flow
-
-```
-Task Scheduler → Check Intervals → Execute Tasks
-Task → Update Status → API Server
-API Server → JSON Response → Client
-```
+### Task Management
+1. **Scheduling**: TaskScheduler executes registered tasks at configured intervals
+2. **Execution**: Tasks run cooperatively, yielding control to other tasks
+3. **Monitoring**: Task status and results are exposed via REST API endpoints
 
 ## Performance Characteristics