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](https://img.shields.io/badge/License-MIT-yellow.svg "License: MIT - Open source software license")](https://opensource.org/licenses/MIT)

> [!CAUTION]
> This project is currently **Experimental** and is not recommended for production use.

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

## πŸ—οΈ Context

Created by **Igor Holt** (AI Architect) as part of the **Genesis Conductor Engine**, `arbiter` serves as the resource orchestration layer for AI workloads within the infrastructure.
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

To maintain consistency with the rest of the documentation and improve readability, consider wrapping arbiter in backticks and splitting the sentence into two. This clearly identifies the project as a technical component and improves the flow of the context section.

Example:

Created by **Igor Holt** (AI Architect) as part of the **Genesis Conductor Engine**. `arbiter` serves as the resource orchestration layer for AI workloads within the infrastructure.


## πŸ“– 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.

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

subgraph Orchestration [Orchestration Layer]
Arbiter((Arbiter Core))
end

subgraph Infrastructure [Infrastructure Layer]
BareMetal[Bare-Metal Hardware]
VRAM[GPU / VRAM Resources]
end

Workloads --> K8s
K8s <--> Arbiter
Arbiter --> BareMetal
Arbiter --> VRAM

style Arbiter fill:#f96,stroke-width:4px
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

The hardcoded fill color #f96 (light orange) may have insufficient contrast against light-colored text or backgrounds in certain themes (such as GitHub's dark mode). To ensure the diagram is accessible to all users, consider using a theme-aware color or a standard Mermaid class instead of a hardcoded hex value.

```
Comment on lines +18 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

The addition of the Mermaid diagram is a significant visual improvement. However, to ensure the README remains accessible to users who rely on screen readers, consider providing a brief text-based summary of the architecture flow. This aligns with the accessibility goals mentioned in the PR description, as Mermaid SVG content is not always effectively parsed by assistive technologies.


## πŸš€ Key Features

- πŸ—οΈ **Infrastructure Awareness**: Directly manages bare-metal resources for maximum performance.
Expand Down