UEFI firmware
Loads BOOTX64.EFI from the system partition. No real mode, no MBR, no CSM.
Architecture
The kernel manages only the critical resources. Drivers, the file system, networking and the graphical compositor are user processes that talk through IPC and hold only the capabilities they were given.
Boot
AriCodeOS starts directly in UEFI. Its own loader, AriBoot, reads the A/B slot state, collects the framebuffer, the ACPI tables and the memory map, verifies the kernel and the initrd and hands over a versioned BootInfo structure before leaving the firmware behind.
Loads BOOTX64.EFI from the system partition. No real mode, no MBR, no CSM.
Chooses the slot, gets GOP, ACPI and the memory map, verifies kernel and initrd, builds the physical map and calls ExitBootServices.
Installs GDT, TSS and IDT, takes over memory, calibrates the APIC timer, starts the other CPUs and enables the IOMMU.
The first user process: device manager, capability broker and service supervisor.
Storage, file service, network, input and compositor, each in its own address space.
The shell and the applications, launched by the broker with the capabilities in their manifest.
Kernel
Only the mechanisms that cannot be delegated. Policy, protocols and devices stay outside.
User space
A driver failure is not a kernel failure: a driver can be killed and restarted without a kernel panic.
Reads each application's manifest and hands out only the handles requested; supervises services and restarts them with growing backoff.
virtio-blk, virtio-net, virtio-input, xHCI with USB HID and mass storage, Realtek r8169. Each gets only its MMIO region, its interrupt and authorised DMA buffers.
A file service over IPC: a private directory per application, CRC32 on every block, copy-on-write replace of files up to 16 MiB, a table in two copies and end-to-end flush (AriFS v2).
A shared network core with DHCP, ARP, ICMP, UDP, TCP and DNS, an HTTP and HTTPS (TLS 1.3) client and an SSH server.
Owns the framebuffer. Applications draw into their own buffers, two per window so no frame is shown half drawn, and receive input only when their window has focus. With the desktop profile, it draws the window frames, the bar, the dock and the programs’ menus itself, so a program cannot paint over them or pass for another.
Interactive shell on the serial port, PS/2, USB or virtio keyboards: ps, mem, cpus, services, net, ping, http, run, diag and more.
Applications
A native program is a static ring 3 ELF built with the SDK. Applications built outside the source tree are packaged, signed with Ed25519 and installed in AriFS by a trusted installer that replaces them atomically, chunk by chunk.
Portable programs are WebAssembly modules run by an in-house interpreter. Each module is validated before it runs, declares its own manifest and sees only the Capability API — deliberately not WASI.
Compatibility
Linux compatibility is planned as an isolated personality server in user space, starting with static ELF binaries and a small set of system calls — enough to run programs built by the AriCode compiler without touching the kernel. Windows software, if it ever comes, would run in a virtual machine.