Development
Trajectory.
Building a deterministic operating system requires disciplined pacing. Our development strategy prioritizes absolute stability at the substrate level before introducing user-space complexity.
Note on Sequencing: This roadmap represents our current engineering trajectory. Timelines are subject to strict quality gates and will be continually adjusted based on community feedback, architectural audits, and hardware validation results. We do not compromise the Single Layer Abstraction for speed.
Substrate & Core Integration
Layers 1 & 2
Establishing the absolute bottom of the stack. This quarter focuses entirely on bare-metal initialization, memory management, and validating the capability-based security model on a single target architecture.
- + Deliver kozo-substrate-x86_64.
- + Finalize kozo-core-mem physical allocation algorithms.
- + Lock down kozo-core-cap handle validation and kozo-core-int deterministic interrupt routing.
Essential Modules & Linux ABI
Layer 3
Bridging the gap between the isolated kernel and user-space utility. We will introduce the first cooperative task scheduling, basic driver support, and the initial Linux compatibility layer to run static binaries.
- + Deploy kozo-driver (Serial/UART debugging) and kozo-fs (in-memory VFS).
- + Implement basic kozo-sched for thread execution.
- + Ship kozo-linux-abi (read, write, exit) and kozo-linux-compat (ELF loader) to successfully execute a static BusyBox environment.
Platform Hardening & GUI
Layers 4 & 5
Securing the system for production workloads and building the user-facing graphical environment on top of a mature, battle-tested IPC foundation.
- + Enforce absolute process isolation via kozo-platform-proc.
- + Roll out kozo-vm (jails/containers) and kozo-security (RBAC policy engines).
- + Initiate Layer 5: A tear-free, deterministic graphical user interface leveraging the established capability subsystem.