From 06ce07d10757e6eb70f6a28d2a100c0c45d9e7c5 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Thu, 25 Jun 2026 05:12:02 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=A8=20Palette:=20[UX=20improvement]=20?=
 =?UTF-8?q?Enhance=20README=20architecture=20diagram=20and=20link=20access?=
 =?UTF-8?q?ibility?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Added explicit title to the Mermaid architecture diagram for better context.
- Implemented semantic node shapes (stadiums for workloads, hexagons for specialized components) to improve visual categorization and cognitive relief.
- Stylized subgraph borders with dashed lines to clearly delineate architectural layers.
- Added a descriptive title attribute to the Genesis Conductor Engine link for improved accessibility and tooltips.
- Documented the semantic shapes UX pattern in .Jules/palette.md.

Co-authored-by: igor-holt <125706350+igor-holt@users.noreply.github.com>
---
 .Jules/palette.md |  5 +++++
 README.md         | 18 ++++++++++++++----
 2 files changed, 19 insertions(+), 4 deletions(-)

diff --git a/.Jules/palette.md b/.Jules/palette.md
index 091d600..3aea4cb 100644
--- a/.Jules/palette.md
+++ b/.Jules/palette.md
@@ -11,3 +11,8 @@ This journal contains critical UX/accessibility learnings discovered during the
 **Learning:** In complex orchestration projects, Mermaid diagrams benefit significantly from visual hierarchy. Distinguishing the "Core" component using specific styling (different colors, thicker borders) provides immediate cognitive relief and helps users identify the primary system anchor within multiple layers.
 
 **Action:** Use Mermaid `style` definitions and distinct node shapes (like double circles `((...))`) for primary architectural components in infrastructure documentation.
+
+## 2026-05-22 - Semantic Shapes for Cognitive Relief
+**Learning:** Using semantic Mermaid shapes (stadiums `([ ... ])` for cloud-native workloads and hexagons `{{ ... }}` for specialized schedulers/hardware interfaces) provides significant cognitive relief. It allows users to instantly categorize components without reading their labels, making complex diagrams more intuitive.
+
+**Action:** Apply semantic node shapes in Mermaid diagrams to distinguish between standard workloads, core orchestrators, and specialized hardware or scheduling components.
diff --git a/README.md b/README.md
index 81bb976..61467d7 100644
--- a/README.md
+++ b/README.md
@@ -15,27 +15,37 @@ Dual nature—combining bare-metal virtualized hardware management (aSHARD VRAM
 ## 🏗️ Architecture
 
 ```mermaid
+---
+title: Arbiter Hybrid Scheduling Architecture
+---
 graph TD
     subgraph CloudNative [Cloud Native Layer]
-        K8s[Kubernetes Cluster]
+        AI([AI Workloads])
+        K8s([Kubernetes Cluster])
     end
 
     subgraph Orchestration [Orchestration Layer]
         Arbiter((Arbiter Core))
-        QS[Quantum Scheduler]
+        QS{{Quantum Scheduler}}
     end
 
     subgraph Infrastructure [Infrastructure Layer]
+        VRAM{{aSHARD VRAM Pinning}}
         BM[Bare Metal Hardware]
         GPU[GPU Resources]
     end
 
+    AI --> K8s
     K8s <--> Arbiter
     Arbiter <--> QS
-    Arbiter <--> BM
+    Arbiter <--> VRAM
+    VRAM <--> BM
     BM --- GPU
 
     style Arbiter fill:#f96,stroke-width:4px
+    style CloudNative stroke-dasharray: 5 5
+    style Orchestration stroke-dasharray: 5 5
+    style Infrastructure stroke-dasharray: 5 5
 ```
 
 ## 🚀 Key Features
@@ -47,7 +57,7 @@ graph TD
 
 ## 🧪 Context
 
-`arbiter` was created by **Igor Holt** (AI Architect) as part of the **Genesis Conductor Engine**. It serves as the resource orchestration layer for AI workloads, bridging low-level hardware management with cloud-native scheduling to ensure optimal utilization of specialized compute resources.
+`arbiter` was created by **Igor Holt** (AI Architect) as part of the [Genesis Conductor Engine](https://genesisconductor.io "Genesis Conductor Engine - Official Website"). It serves as the resource orchestration layer for AI workloads, bridging low-level hardware management with cloud-native scheduling to ensure optimal utilization of specialized compute resources.
 
 ## ⚖️ License