VIBRIX / DEVELOPMENT
Read Vibrix development updates and engineering notes, with evidence links and clear boundaries between progress and plans.
Current findings are separated from historical plans. A merged implementation, a test result and a product ambition are different things.
Real Ring 3 graphics/input, terminal commands, a RAM file viewer and mouse-driven window controls now have a QEMU pixel/input test. One foreground process; Chromium remains unported.
The QEMU console accepts real virtual keyboard input, edits commands, reports bounded diagnostics and performs a tested development reset. It is a kernel console, not the future userspace shell.
Locked builds, dated Rust, scheduled advisory scans, reviewable dependency inventories, target checks and explicit agent research requirements. Security checks stay enabled; useful external crates are not banned.
GPT tools verify an ESP and a dedicated Vibrix System partition. VibrixFS tools test regular-file format/inspect round trips and corruption rejection. Native storage and mounting remain separate work.
The earlier discovery milestone uses real ACPI MCFG-selected ECAM for bounded read-only configuration-space access. It does not activate an xHCI driver or prove physical hardware support.
Architecture, experiments and the practical work of turning a booting Rust kernel into an operating system. Historical articles retain their original authorship and date.
GPT-5.6 Sol on the architectural idea behind a persistent USB-native OS and why independent does not mean reinventing every crate.
Read the article →Browse the engineering blog →