Engineered for
Certainty.

Phase 1: Substrate + Core (Layers 1-2)

Establishing the foundational hardware primitives and capability mechanisms. This phase is entirely devoid of user policy.

• +
  kozo-substrate-x86_64 — Start with one architecture to validate the substrate.
• +
  kozo-core-mem — Physical allocator and kernel heap management.
• +
  kozo-core-cap — The core capability handle system.
• +
  kozo-core-int — Deterministic interrupt routing.

Phase 2: Essential System Modules (Layer 3)

Bringing the operating system to life with the minimal drivers and scheduling required to execute sequential and concurrent workloads.

• +
  kozo-driver — Serial/UART for debugging, scaling up to NVMe.
• +
  kozo-fs — Simple in-memory FS first, expanding to the ext-family later.
• +
  kozo-sched — Cooperative scheduler initially, transitioning to preemptive.

Phase 3: Linux Compatibility (Layers 3-4)

Ensuring KOZO is immediately useful by providing a compatibility layer capable of running statically compiled Linux binaries.

• +
  kozo-linux-abi — Basic syscall translation (read, write, exit).
• +
  kozo-linux-compat — Dedicated ELF loader.
• +
  busybox — Run static BusyBox as the initial proof of concept.

Phase 4: Platform Hardening

Enforcing strict boundaries and isolation policies across the environment to guarantee true zero-trust execution.

• +
  kozo-platform-proc — Strict process isolation.
• +
  kozo-vm — Container and jail deployment.
• +
  kozo-security — Role-Based Access Control (RBAC) and policy enforcement.

Phase 5: GUI (Layer 5)

The final layer. The graphics subsystem is implemented last, as a modern, tear-free graphical environment requires absolutely stable driver and IPC foundations to function deterministically.