VIBRIX / ROADMAP

From first boot to a portable OS.

Follow the Vibrix engineering milestones, scoped QEMU evidence and the work remaining before persistent USB operation.

03 / BUILD STATUS

From first boot
to real OS.

This snapshot is based on merged main and observed QEMU behavior. Partial foundations do not mean the whole milestone is complete.

✓

M0–M2 / BOOT PATH

Boot & handoff

UEFI → our loader → standalone higher-half kernel with BootInfo v3.

◌

M3 / FOUNDATIONS VERIFIED

Memory & exceptions

Frames, early heap, dynamic managed mappings/reclaim, guard pages and CPU fault probes; general user-process scheduling and SMP remain unfinished.

◌

Device discovery & interrupts

ACPI, PCI/BAR, bounded ECAM, driver binding and real single-vector MSI delivery on the isolated QEMU EDU device. MSI-X delivery and general hardware drivers remain separate.

✓

M4.5 / QEMU VERIFIED

Interactive kernel console

Real virtual keys, line editing, diagnostics, timer and a working vibrix> prompt.

◌

M5–M6 / NATIVE USERSPACE

Userspace CLI and desktop preview

Real Ring 3 ELF, syscalls, RAM files and a documented shell; opt-in graphical terminal and file viewer. Not a general process environment or browser.

M7–M9 / FUTURE

Persistent USB OS

Native USB storage and filesystem integration. GPT/VibrixFS host tools already have narrower test coverage.

Read the evidence-backed status snapshot → Full engineering roadmap →