updated

README.md

@@ -8,27 +8,30 @@ without building a monitoring system from scratch.
 
 ## Architecture
 
-```
+```mermaid
-                         Internet
+flowchart TD
-                            |
+    Internet((🌍 Internet))
-                            v
+
-                  +-------------------+
+    subgraph GhaymahCloud ["☁️ Ghaymah Cloud Environment"]
-                  |   Ghaymah Cloud   |
+        direction LR
-                  +-------------------+
+        UK["🚀 Uptime Kuma<br/>(Port: 3001)"]
-                       |          |
+        DemoWeb["🌐 demo-web-server<br/>(NGINX :80)"]
-                       v          v
+    end
-            +------------------+   +------------------+
+
-            |  Uptime Kuma     |   |  demo-web-server |
+    Internet --> UK
-            |  (container)     |-->|  (nginx)          |
+    Internet --> DemoWeb
-            |  port 3001       |   |  port 80          |
+    
-            +------------------+   +------------------+
+    UK -- "HTTP Check<br/>(Every 60s)" --> DemoWeb
-                 |         |
+    UK -. "Alert on Down/Up" .-> Telegram{"📱 Telegram Channel"}
-          HTTP check     Alert on
+    UK -. "Exposes" .-> PublicPage(["📊 Public Status Page"])
-          every 60s       Down/Up
+    
-                 |         |
+    style Internet fill:#f9f9f9,stroke:#333,stroke-width:2px;
-                 v         v
+    style Telegram fill:#2CA5E0,stroke:#fff,stroke-width:2px,color:#fff;
-        Public Status   Telegram
+    style PublicPage fill:#4CAF50,stroke:#fff,stroke-width:2px,color:#fff;
-             Page
+    classDef cloud fill:#f0f8ff,stroke:#4a90e2,stroke-width:2px,stroke-dasharray: 5 5;
+    classDef container fill:#ffffff,stroke:#333333,stroke-width:1px,shadow:true;
+    class GhaymahCloud cloud;
+    class UK,DemoWeb container;
 ```
 
 ## What was deployed
@@ -104,6 +107,12 @@ token, chat ID) are intentionally redacted from that file.
    Telegram. Point it back at a healthy URL to see the Up recovery
    alert.
 
+## Security & Data Resilience
+
+- **Independent Health Tracking:** The Uptime Kuma stack functions as an independent observer. The persistence layer retains the complete outage and metrics history inside an isolated volume.
+- **Failover Alerts Validation:** Explicitly validated notification webhooks logic to verify immediate alerting upon HTTP failures and automatic recovery resolution (Up events).
+- **Persistent Storage Configuration:** Critical settings (like SQLite DB, configurations) are safely coupled to `/app/data` volume mount to circumvent ephemeral container cycles.
+
 ## Next steps (not yet done)
 
 - Put Uptime Kuma behind a custom domain / HTTPS via reverse proxy