From b43a263b93ae44f4e12f1151ac376e79b889b361 Mon Sep 17 00:00:00 2001
From: "google-labs-jules[bot]"
 <161369871+google-labs-jules[bot]@users.noreply.github.com>
Date: Sat, 27 Jun 2026 05:21:32 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=A8=20Palette:=20Enhance=20documentati?=
 =?UTF-8?q?on=20UX=20and=20accessibility?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Added semantic node shapes to the architecture diagram (stadiums for workloads, hexagons for specialized schedulers/pinning).
- Added an explicit title to the Mermaid diagram for better context and accessibility.
- Applied dashed borders to architectural subgraphs to delineate layers clearly.
- Updated the Genesis Conductor Engine link with the official URL and an accessibility title.
- Recorded semantic diagram patterns 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..e4e7ea1 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-06-27 - Semantic Mermaid Diagrams
+**Learning:** Using semantic node shapes (stadiums for workloads, hexagons for specialized processes) in Mermaid diagrams provides immediate cognitive cues about the nature of system components. Adding explicit titles and dashed subgraph borders further enhances accessibility and visual delineation between architectural layers.
+
+**Action:** Standardize on stadiums `([ ... ])` for cloud-native workloads and hexagons `{{ ... }}` for specialized schedulers or hardware interfaces. Use `--- title: [Text] ---` for diagram titles and `stroke-dasharray: 5 5` for layer borders.
diff --git a/README.md b/README.md
index 81bb976..cc0a98b 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]
+        Workloads([AI Workloads])
+        K8s([Kubernetes Cluster])
     end
 
     subgraph Orchestration [Orchestration Layer]
         Arbiter((Arbiter Core))
-        QS[Quantum Scheduler]
+        QS{{Quantum Scheduler}}
     end
 
     subgraph Infrastructure [Infrastructure Layer]
+        VP{{aSHARD VRAM Pinning}}
         BM[Bare Metal Hardware]
         GPU[GPU Resources]
     end
 
+    Workloads --> K8s
     K8s <--> Arbiter
     Arbiter <--> QS
-    Arbiter <--> BM
+    Arbiter <--> VP
+    VP <--> 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