Wyrmroot is an experimental Rust-first, capability-oriented operating-system project whose architecture is built around the Deepwyrm kernel.
Wyrmroot's architecture defines native operating-system interfaces first. Unix/POSIX and other compatibility environments belong as personalities layered above native Wyrmroot interfaces rather than foundations of the kernel ABI.
Native service protocols are required to be typed and versioned, and the platform is based on explicit delegation of authority. The base system is not founded on libc or POSIX.
The architecture keeps boot loading, executable loading, service management, package management, compatibility, graphics, and desktop policy as distinct responsibilities rather than one privileged subsystem.
UEFI firmware
|
Wyrmroot EFI loader
|
Deepwyrm
|
primordial Wyrmroot bootstrap
|
normal Wyrmroot userspace and services
This diagram describes durable component boundaries, not implementation or acceptance status.
Deepwyrm owns the native kernel ABI, kernel objects and rights, and low-level mechanisms. Wyrmroot owns the EFI loader, bootfs, userspace startup semantics above the primordial handoff, executable-loading policy, native service protocols, image assembly, and higher-level capability distribution.
Wyrmroot consumes generated Deepwyrm ABI definitions from an exact pinned Deepwyrm revision rather than duplicating kernel definitions. Linux-shaped control surfaces and compatibility APIs may be exposed by adapters where useful, but they are not foundational Wyrmroot interfaces. Multiple foreign APIs wanting similar behavior does not, by itself, justify a new native service or kernel primitive; compatibility is expected to compose existing mechanisms first and keep foreign policy in adapters.
- Deepwyrm provides the kernel.
- Glasswyrm is the intended native window-system and compositor foundation.
- Prismdrake Desktop Environment is the intended desktop environment.
- Architecture and plan index
- Platform conventions
- Wyrmroot as built
- Licensing policy and component map
- Validation records
- Security reviews
Architecture documents define design contracts. Validation and security evidence applies only to the revisions and artifacts each record names; it does not imply production, VM, or physical-hardware acceptance.
Development tasks run through one dispatcher, with the pinned toolchain:
tools/pinned-cargo xtask dev-boot [--smp] [--check] [--icount] [--deep-repository <path>] [--sdk <path>]
tools/pinned-cargo xtask product --output <fresh-directory> [--deep-repository <path>]
tools/pinned-cargo xtask test [all|fmt|clippy|unit|root]
dev-bootbuilds the product from the Wyrmroot and Deepwyrm working trees and boots it in local QEMU;--checkdrives the shell prompt and requires a clean power-off instead of an interactive session.--icountruns QEMU with-icount shift=0, so guest time counts instructions and the kernel's step report reads as guest instructions; it is a measurement mode, and--checkwaits four times as long under it.productbuilds the same product into a fresh directory: the ESP image plus the loader, kernel, bootstrap, native services, bootfs and firmware pair.testruns the host gate: formatting, warnings-denied Clippy, the workspace tests and the root Python suites.
product and dev-boot refuse a Deepwyrm checkout whose semantic ABI fingerprint is not the one pinned in toolchain/versions.toml, because userspace is compiled against the pinned ABI.
Wyrmroot currently uses a component-aware mix: the repository fallback and several existing foundations are GPL-2.0-or-later, while selected applications and tools are GPL-3.0-or-later. New wholly first-party project code defaults to GPL-3.0-or-later; GPLv2-compatible lanes are selected when actual provenance or combination requirements call for them. See LICENSING.md for the authoritative current map and provenance rules.