Alpha 0.1

Z-OS

The operating system IS signal chains.

Not "an OS that uses signal chains." The kernel, the desktop, the browser, the storage — they are all chains. One pattern from boot to browser. One image. Boots on any x86-64 UEFI hardware. Discovers what it has. Learns from experience. Gets better over time.

What makes Z-OS different

Everything is a chain

A chain is signal in, transform, signal out. Hardware discovery is a chain. Window management is a chain. File storage is a chain. The desktop panel is a chain. There is no second abstraction. This is the only one.

Δ

The OS discovers its own hardware

At boot, Z-OS scans every bus — PCIe, USB, NVMe, I2C — and builds a live map of what it has. Not from spec sheets. From what it actually finds. One image runs everywhere because the OS figures out where it woke up.

It learns from experience

Hardware performance is tracked over time. The OS remembers what worked, what degraded, what failed. It adapts. A fresh install and a six-month install behave differently — the older one knows more.

Z+

Z+ is the native language

Z+ describes connections, not procedures. There are no loops, no threads, no locks. The arrow operator (→) wires signals. Programs are graphs that resolve simultaneously. The entire language fits on an index card.

The Desktop

Z-OS ships with a full desktop environment. It feels familiar — panel at top, dock at bottom, windows that snap and tile — but underneath, every element is a signal chain.

Panel + Dock

Top panel for status, bottom dock for launchers. Both are chains emitting signals.

Snap / Tile

Drag windows to edges or corners. They snap into tiled layouts automatically.

Command Palette

One keystroke opens the palette. Search anything — apps, files, settings, chains.

Spring Physics

Windows, menus, and animations move with spring dynamics. Smooth, never jarring.

Sacred Corners

Screen corners are reserved for system actions. Designed to prevent accidental triggers.

First Boot Wizard

A guided walkthrough on first launch. Teaches the desktop through use, not docs. Passive education built in.

Signal Chains

A chain takes a signal in, transforms it, and passes it on. That is the universal pattern. The kernel uses it for interrupts. The desktop uses it for input events. Applications use it for business logic. There is no abstraction switch as you move between layers.

// a chain is always the same shape
keyboard gate(ctrl+space) command_palette
temperature gate(> 80C) throttle_core
mouse_drag knee(snap_edge, spring: 0.8) window_position
// same pattern. kernel to desktop to app.

Three Personas

Z-OS surfaces as three experiences. Same language, same chains, different starting points. The full power is always there — the curtain lifts as you go deeper.

Hardware Discovery

Z-OS does not use device trees or board support packages. At boot, it probes every bus and builds a live capability map. Plug something in, the signal graph extends. Remove it, the graph contracts. No configuration files. No driver databases.

Traditional OSZ-OS
Device treesAutomatic bus scanning
Board support packagesLive capability map
Platform-specific kernelsOne image, any hardware
Driver databasesSignal contract matching
Manual configurationBoot and it figures it out
Separate OS editionsOne OS that discovers what it is

Built-in Software

Browser

A native browser built on signal chains. Web content renders through the same chain pipeline as everything else.

Networking

TCP/IP, DNS, and HTTP built into the chain graph. Network connections are signals like everything else.

NVMe Storage

Direct NVMe driver with signal-aware storage. Read and write operations flow through chains with temporal awareness.

Installation

Z-OS boots from USB on any x86-64 UEFI machine, or runs in QEMU for development. The CN60 Chromebox is the primary bare-metal test target.

QEMU (recommended for first look)

git clone https://github.com/theBullfish/zeos.git
cd zeos
make run

USB Boot (bare metal)

make usb
sudo dd if=build/zeos.img of=/dev/sdX bs=4M status=progress

Tested on ASUS Chromebox CN60 and any x86-64 UEFI system.

ALPHA 0.1

Z-OS is real, working software — 32K+ lines of kernel C, 130+ source files, 32 Z+ programs. But it is alpha. Things break. APIs change. This is for developers, tinkerers, and people who want to watch an OS grow from the ground up. If you want stable, come back later. If you want to build the future, start here.