Skip to content
← All projects
Omni System Hub OS / In Development

Your computer. More freedom to make it yours.

An operating-system project exploring familiar applications, isolated responsibilities, and a desktop that can recover when one part goes wrong.

Explore how it works ↓
OMNI / CONCEPT
Your workspacePersonality & everyday toolsIndependent componentsKeep responsibilities separateSystem supervisionObserve · contain · recover
Architecture sketch / not a product screenshot

Explore the project

Read the project notes and follow the source material for more detail.

Explore the concept

Interactive architecture console and multi-runtime matrix visualizer demonstrating Go PID 1 orchestration, wlroots Wayland compositing, and declarative constraint solving.

The design, in more detail

Definition

An experimental operating system architecture combining a Go-based PID 1 supervisor, wlroots Wayland compositor, and multi-runtime bridges (Wine, Waydroid) with declarative constraint solving.

The problem

Modern computing is fractured into corporate walled gardens. Developers and operators must maintain multiple physical machines or run sluggish, memory-hogging virtual machines just to run platform-specific software. Furthermore, traditional OS supervisors rely on naive polling loops (PIDs, CPU ticks) that fail to detect semantic UI deadlocks or window pipeline freezes.

The approach

Omni OS replaces the passive best-effort model with a Declarative Constraint-Solver Reasoning Engine. Subsystems publish immutable, generation-tracked evidence snapshots to /run/omni/evidence/. An event-driven solver continuously verifies abstract semantic contracts (display boundaries, session preservation, viewport fit), diagnosing root causes and executing surgical capability graph repairs before escalating to restarts.

How it works

  1. Sovereign Exokernel Init: Custom-hardened Linux kernel boots into a compiled Go orchestrator as PID 1, managing daemons, watchdogs, and capability graphs.
  2. Custom wlroots Compositor: Low-latency C Wayland compositor managing hardware-accelerated surface presentation across X11, Wayland, and runtime emulators.
  3. Multi-Runtime Execution Matrix: Natively bridges Win32 (Wine 9.0 Pro), Android (Waydroid container), and Darwin (Darling Mach-O) directly to Wayland surfaces without hypervisors.
  4. Declarative Constraint-Solver Engine: Eliminates polling loops; evaluates semantic obligations from immutable JSON snapshots in /run/omni/evidence/ upon filesystem commit.
  5. Tiered Glass UI Shell: Primary Glassmorphic desktop surface engineered in Tauri + React, paired with an automated fallback to a Tier 3 native Skia/Softbuffer renderer.

Project notes

Init PID 1
Compiled Go Exokernel
Unified Runtimes
Win32 · Android · Darwin · Linux
Compositor
Custom C wlroots
Supervisor
Declarative Constraint Solver
Development history & next steps
2024

Exokernel Conception

Prototyped Go-based PID 1 init daemon and low-latency C wlroots Wayland surface binding.

2025

Multi-Runtime Unification

Integrated Wine, Waydroid, and Darling IPC sockets into unified glassmorphic compositor.

2026

Constraint-Solver Migration

Replaced passive process monitoring with declarative semantic contract reasoning engine.

What comes next

Finalizing automated hardware profiling via Vanguard sentinel and releasing reproducible live ISO USB flashing builds.

Source material & related links

Follow the available source material and related sites for this project.

Interactive architecture illustration ↗

A guided illustration of the proposed supervisor and component relationships.

Explore the architecture illustration →My public GitHub projects →

Topics: Operating System · Bare-Metal · Go · Wayland · wlroots · Constraint Solver · Rust

Keep reading

What makes computer infrastructure dependable? →Teaching software to look for broken rules →