🎨 Palette: [UX improvement] Enhanced architecture diagram and link accessibility

[Igor Holt (igor-holt)]

💡 What:

• Refined the Mermaid architecture diagram with semantic shapes (stadium for workloads/K8s, hexagons for specialized components) and dashed subgraph borders.
• Added a descriptive title to the Mermaid diagram.
• Updated the "Context" section to include an accessible link to the Genesis Conductor Engine website with a title attribute.
• Added a title attribute to the MIT License link for improved accessibility and tooltips.
• Updated the Palette journal with new learnings about semantic node shapes.

🎯 Why:

• Improves the Developer Experience (DX) by making the architecture more intuitive and scannable.
• Enhances accessibility for users with screen readers by providing descriptive link titles.
• Fixes a visual omission in the architecture overview by including the "aSHARD VRAM Pinning" component.

♿ Accessibility:

• Added descriptive title attributes to the Genesis Conductor Engine and MIT License links.
• Added an accessible title to the Mermaid architecture diagram.
• Used semantic node shapes that provide visual cues for different types of system components.

---

PR created automatically by Jules for task 18139128687447766123 started by Igor Holt (@igor-holt)

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[claude]

⚠️ Code review skipped — your organization's overage spend limit has been reached.

Code review is billed via overage credits. To resume reviews, an organization admin can raise the monthly limit at claude.ai/admin-settings/claude-code.

Once credits are available, push a new commit or reopen this pull request to trigger a review.

[gemini-code-assist]

Code Review

This pull request updates the project documentation, adding a new entry to .Jules/palette.md about semantic node shapes and applying these guidelines to the architecture diagram in README.md. It also adds external links to the context and license sections. The reviewer suggests reintroducing the GPU Resources node to the infrastructure layer in the diagram to clarify the relationship with the new VRAM Pinning component.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

While the new diagram is a great improvement with semantic shapes and the new VRAM component, removing GPU Resources makes it unclear what the 'VRAM Pinning' is acting upon. Since VRAM is part of a GPU, it would be clearer to show the GPU resources explicitly in the infrastructure layer.

Consider reintroducing GPU Resources and adjusting the connections to show that VRAM pinning acts on GPUs, which are part of the Bare Metal Hardware.

---
title: Arbiter Hybrid Scheduling Architecture
---
graph TD
    subgraph CloudNative [Cloud Native Layer]
        Workloads([AI Workloads])
        K8s([Kubernetes Cluster])
    end

    subgraph Orchestration [Orchestration Layer]
        Arbiter((Arbiter Core))
        QS{{Quantum Scheduler}}
    end

    subgraph Infrastructure [Infrastructure Layer]
        VRAM{{aSHARD VRAM Pinning}}
        BM[Bare Metal Hardware]
        GPU[GPU Resources]
    end

    Workloads --> K8s
    K8s <--> Arbiter
    Arbiter <--> QS
    Arbiter <--> VRAM
    VRAM <--> GPU
    GPU --- BM

    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