Skip to content

🎨 Palette: Documentation UX and Accessibility Enhancement #69

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Igor Holt (igor-holt) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

🎨 Palette: Documentation UX and Accessibility Enhancement #69

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,27 +15,37 @@ Dual nature—combining bare-metal virtualized hardware management (aSHARD VRAM
## 🏗️ Architecture

```mermaid
---
title: Arbiter System 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]
aSHARD{{aSHARD VRAM Pinning}}
BM[Bare Metal Hardware]
GPU[GPU Resources]
end

Workloads --> K8s
K8s <--> Arbiter
Arbiter <--> QS
Arbiter <--> BM
Arbiter <--> aSHARD
aSHARD <--> BM
BM --- GPU
Comment on lines +41 to 43

@gemini-code-assist gemini-code-assist Bot Jun 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Since aSHARD is specifically responsible for VRAM pinning, it should have a direct relationship/connection to the GPU (GPU Resources) node in the architecture diagram, rather than only connecting to BM (Bare Metal Hardware). This makes the diagram more semantically accurate regarding how VRAM pinning interacts with GPU resources.

Suggested change
Arbiter <--> aSHARD
aSHARD <--> BM
BM --- GPU
Arbiter <--> aSHARD
aSHARD <--> BM
aSHARD <--> GPU
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
Expand All @@ -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

Expand Down