Boot
UEFI loader, ELF kernel, BootInfo, serial and framebuffer console, GDT, IDT and exceptions.
Roadmap
The master document fixed the plan before the first line of code. A phase only closes when its tests pass in QEMU; each version is tagged and audited.
The roadmap
UEFI loader, ELF kernel, BootInfo, serial and framebuffer console, GDT, IDT and exceptions.
Bitmap physical allocator, own page tables with W^X and guard pages, kernel heap.
APIC timer calibrated against the PIT, threads with guarded stacks, preemptive round-robin.
Ring 3, syscalls, per-process address spaces, handles, capabilities and IPC.
AriInit, a driver framework with IRQ, MMIO and DMA capabilities, PCIe enumeration.
virtio-blk in ring 3, a block service, AriFS and the arish shell.
virtio-net, IPv4, DHCP, DNS, UDP, TCP and an HTTP client, all in user space.
virtio-input, a compositor with windows and focus, the application SDK.
Manifests and a capability broker; an in-house WebAssembly interpreter.
In-house cryptography, signed images and A/B updates with rollback.
Application processors, IPIs and TLB shootdown; VT-d with one domain per driver.
USB image, PS/2 console, xHCI and USB storage, Realtek networking: first boot on a laptop.
After the roadmap
With every phase implemented, development follows a sequence of stages, each with its own branches, decisions and test scenarios.
Audits resolved with evidence and a single status table per capability.
A service supervisor with queryable state, and IPC calls with deadlines and correlation.
USB and virtio keyboards as console, and AriFS persistence across power cuts.
Full update cycles across boots, quotas, saturation tests and per-resource permissions.
Signed packages built outside the tree, a trusted installer and the WebAssembly profile.
Measurements, optimisations guided by them, real hardware and more devices.
Next