List view
### Milestone 0.2.0 The **0.2.0** milestone validates the extensibility of the system and the maturity of its development ecosystem. While 0.1.0 proved the kernel architecture, 0.2.0 focuses on expanding hardware abstractions and establishing the primitives required for complex user-space compositions. This stage requires the implementation of high-throughput subsystems for **network interfaces** and **graphics adapters**. These implementations must strictly adhere to the zero-copy architecture, ensuring that framebuffers and packet streams are handled via memory ownership transfer rather than kernel buffering. The security model is finalized through the completion of the **capability-based permission system** and the introduction of **Stateless Library Injection (SLI)**. This mechanism replaces traditional dynamic linking by allowing the runtime mapping of immutable code dependencies into process address spaces, enforcing strict versioning and dependency isolation. Additionally, this milestone establishes the software supply chain infrastructure. This includes cryptographic **package authentication**, remote dependency resolution, and version management protocols. Finally, the release of the **Distribution Development Kit (DDK)** validates the system's modularity. This tooling must enable the reproducible construction of custom system images, supporting configurations ranging from general-purpose environments to single-process sovereign appliances.
Due by August 6, 2026### Milestone 0.1.0 The **0.1.0** milestone validates the structural integrity of the kernel and its ability to operate autonomously. This stage is reached when the system successfully boots, manages memory resources, and orchestrates capabilities. The validation criteria focus on the stability of the core subsystems. The physical memory allocator (WHBA) and the virtual memory manager must demonstrate correct operation alongside the asynchronous scheduler within a symmetric multi-processing (SMP) environment. This ensures that resource distribution across multiple processor cores occurs without critical contention or coherency errors. Inter-process communication is a central validation point. The zero-copy signaling mechanism is required to successfully mediate all control flow between the kernel, the embedded storage drivers, and user-space processes. This confirms the viability of the memory ownership transfer model as the primary method of data exchange. Finally, the system must demonstrate user-space sovereignty by loading, executing, and cleanly terminating an independent process linked against the native runtime. The boot sequence is considered complete only when the kernel autonomously initializes the hardware, mounts the root file system via embedded drivers, and successfully transfers control to the initial user process.
Due by February 1, 2026