Skip to content
Open
Changes from all commits
Commits
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
34 changes: 32 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,44 @@
# ⚖️ arbiter

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
![Status: Experimental](https://img.shields.io/badge/Status-Experimental-orange)
[![License: MIT - Open source software license](https://img.shields.io/badge/License-MIT-yellow.svg "License: MIT")](https://opensource.org/licenses/MIT)

> [!CAUTION]
> This project is currently **Experimental**. It is not recommended for production use and is subject to significant architectural changes.

Dual nature—combining bare-metal virtualized hardware management (aSHARD VRAM pinning) with quantum-accelerated Kubernetes scheduling.

## 📖 Overview

`arbiter` is a specialized orchestration layer designed for high-performance computing environments. It bridges the gap between low-level hardware management and cloud-native scheduling, providing a unified interface for managing virtualized resources with precision.

### 🏗️ Architecture

```mermaid
graph TD
subgraph CloudNative [Cloud Native]
K8s[Kubernetes]
Workloads[AI Workloads]
end

subgraph Orchestration [Orchestration]
Arbiter((Arbiter Core))
Scheduler[Quantum Scheduler]
end

subgraph Infrastructure [Infrastructure]
BareMetal[Bare Metal]
VRAM[aSHARD VRAM Pinning]
end

Workloads --> K8s
K8s --> Arbiter
Arbiter --> Scheduler
Arbiter --> VRAM
VRAM --> BareMetal

style Arbiter fill:#f96,stroke:#333,stroke-width:4px
```
Comment on lines +16 to +40
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

While the Mermaid diagram significantly improves the visual architecture overview, it may not be fully accessible to users relying on screen readers. Since accessibility is a key goal of this PR, consider adding a brief text-based description or a nested list below the diagram to describe the relationships and flow. This ensures that the architectural information is available to all users, even if the diagram fails to render or for users with visual impairments.


## 🚀 Key Features

- 🏗️ **Infrastructure Awareness**: Directly manages bare-metal resources for maximum performance.
Expand Down