Skip to content

Roadmap

35 phases from first boot to real hardware

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

All 35 phases implemented

Phases 0–4 · 0.0.1–0.0.2

Boot

UEFI loader, ELF kernel, BootInfo, serial and framebuffer console, GDT, IDT and exceptions.

Phases 5–7 · 0.0.3

Memory

Bitmap physical allocator, own page tables with W^X and guard pages, kernel heap.

Phases 8–10 · 0.0.4

Time and threads

APIC timer calibrated against the PIT, threads with guarded stacks, preemptive round-robin.

Phases 11–14 · 0.0.5–0.0.6

Isolation

Ring 3, syscalls, per-process address spaces, handles, capabilities and IPC.

Phases 15–17 · 0.0.7

Init and devices

AriInit, a driver framework with IRQ, MMIO and DMA capabilities, PCIe enumeration.

Phases 18–21 · 0.0.8

Storage and shell

virtio-blk in ring 3, a block service, AriFS and the arish shell.

Phases 22–24 · 0.0.9–0.1

Network

virtio-net, IPv4, DHCP, DNS, UDP, TCP and an HTTP client, all in user space.

Phases 25–27 · 0.2

Input, GUI and SDK

virtio-input, a compositor with windows and focus, the application SDK.

Phases 28–29 · 0.3

Sandbox and WASM

Manifests and a capability broker; an in-house WebAssembly interpreter.

Phases 30–31 · 0.4

Trust

In-house cryptography, signed images and A/B updates with rollback.

Phases 32–33 · 0.5

SMP & IOMMU

Application processors, IPIs and TLB shootdown; VT-d with one domain per driver.

Phase 34 · 0.6–0.9

Real hardware

USB image, PS/2 console, xHCI and USB storage, Realtek networking: first boot on a laptop.

After the roadmap

From working to dependable

With every phase implemented, development follows a sequence of stages, each with its own branches, decisions and test scenarios.

Stage 0 · done

Consolidate

Audits resolved with evidence and a single status table per capability.

Stage 1 · done

Observable recovery

A service supervisor with queryable state, and IPC calls with deadlines and correlation.

Stage 2 · done

A useful session

USB and virtio keyboards as console, and AriFS persistence across power cuts.

Stage 3 · done

Limits and updates

Full update cycles across boots, quotas, saturation tests and per-resource permissions.

Stage 4 · done

External applications

Signed packages built outside the tree, a trusted installer and the WebAssembly profile.

Stage 5 · in progress

Optimisation and expansion

Measurements, optimisations guided by them, real hardware and more devices.

Next

Where it goes from here

  • Power management on the reference laptop: sleep states and battery
  • USB 2.0 hubs, split transactions and 64-bit addressing verified on the laptop, then more devices
  • The desktop’s polish: cached animations, 2x scale for dense screens, two-finger scrolling and brightness (ADR 0078, stage 4)
  • One path from programs to the hardware: after the HD 4000’s engine and compute, SPIR-V shaders, 3D and a game that uses it all, compared with Linux on the same laptop (ADR 0080)
  • Signed driver packages with three trust levels (ADR 0073)
  • Every subsystem compared with the established implementations before it changes deeply (ADR 0063)
  • Testers on more machines: hardware reports from the community
  • A Linux personality server for static ELF binaries, starting with AriCode programs
  • aarch64 and riscv64, once the architecture-specific code is fully isolated
  • In the long term, self-hosting: AriCodeOS building the next AriCodeOS