Subsystems
JARVIS OS is built as a set of modular, independently maintained subsystems. Each component lives in its own repository under the jarvisos GitHub organization.
┌─────────────────────────────────────────────────────────┐
│ JARVIS OS │
│ │
│ ┌───────────┐ ┌──────────────┐ ┌───────────────┐ │
│ │ jarvis │──▶│ MCP Server │──▶│ System Tools │ │
│ │ core │ │ Registry │ │ (sudo-aware) │ │
│ └─────┬─────┘ └──────────────┘ └───────────────┘ │
│ │ │
│ ▼ │
│ ┌───────────┐ ┌──────────────┐ ┌───────────────┐ │
│ │ Ollama │ │ KDE Plasma │ │ Calamares │ │
│ │ (local) │ │ 6 / Wayland │ │ Installer │ │
│ └───────────┘ └──────────────┘ └───────────────┘ │
│ │
│ ┌─────────────────────────────────────────────────────┐│
│ │ Build Pipeline: 01 ▸ 02 ▸ 03 ▸ 04 ▸ 05 ▸ 06 ▸ 07 ││
│ └─────────────────────────────────────────────────────┘│
└─────────────────────────────────────────────────────────┘JARVIS OS Build System
The main build pipeline — seven modular scripts (01 through 07) that transform a base Arch Linux ISO into a bootable AI-native operating system. Each stage is isolated and reproducible.
Jarvis Core
The AI daemon and CLI. This is the `jarvis` command that users interact with — the bridge between the LLM and the operating system. Manages sessions, context, and tool dispatch.
MCP Servers
The Model Context Protocol orchestration layer and tool registry. Defines the tools the LLM can invoke, manages permissions, and handles the create/modify/delete lifecycle for system tools.
Calamares Config
The Calamares graphical installer configuration package. Enables one-click installation of JARVIS OS to physical hardware with automatic partitioning and post-install setup.
Repository structure
github.com/jarvisos/
├── jarvisos ← main build system (the 7 scripts)
├── jarvis-core ← AI daemon + CLI
├── mcp-servers ← MCP orchestration layer
├── calamares-config ← installer config
└── jarvisos.github.io ← this website