TCP/IP, written in Lux, running in ring zero.
Fifty-four content-addressed bytecode modules, verified and JIT-compiled in the kernel, answering a real host TCP client.
Network stack / 6 minField notes from building Yggdrasil—a BEAM-like operating system where isolated processes, message passing, and supervision reach all the way down to the hardware.
Implementation reports, design notes, and one evolving argument for treating the operating system as a runtime.
The kernel is not a container for applications. It is the runtime. A technical argument for building an operating system around tiny, isolated, supervised processes.
Read White Paper 001 / 14 min ↗RedMagic became the system library. Lux became a portable frontend. Now Yggdrasil exposes compilation and execution as an ordinary process-owned service.
Read Field Note 012 / 12 min ↗A Lux process encoded the GPU protocol, owned the framebuffer, and animated this band. Yggdrasil moved opaque buffers—and stayed out of the way.
Read the M11 build report / 10 min ↗Garbage collection, proper tail calls, Lux-owned ports, and a GPU transport—the plan for long-running device drivers outside the kernel.
Read the M11 plan / 11 min ↗Per-CPU worlds, copied heap fragments, work stealing, and the five concurrency bugs that turned an SMP boot into a multicore operating system.
Read Field Note 009 / 8 min ↗Fifty-four content-addressed bytecode modules, verified and JIT-compiled in the kernel, answering a real host TCP client.
Network stack / 6 minTwo module versions, explicit migration, and a purge path that knows when old code is truly gone.
Code loading / 5 minCranelift without std, hand-rolled relocation, RX publication, and an interpreter waiting underneath.