Deepwyrm is the Rust-first kernel project for Wyrmroot. Its architecture defines a small, native, capability-oriented substrate for operating-system services without adopting the Linux ABI or POSIX as its internal model.
Deepwyrm is designed around typed kernel objects, opaque process-local rights-bearing handles, and an explicit, schema-defined native ABI. Its architecture separates typed, rights-controlled kernel mechanisms from naming, service policy, compatibility behavior, and other higher-level userspace decisions.
Portable kernel code is written in Rust where practical. Architecture-specific, hardware-facing, assembly, C, and unsafe Rust code is kept behind narrow, documented boundaries. Subsystem boundaries are designed to support focused host-side and synthetic testing as well as full-system validation.
Compatibility environments may translate POSIX, Linux, Windows, or retro APIs onto the native object and handle model. Those environments are consumers of the kernel ABI rather than foundations of it. Compatibility needs may expose a genuinely missing privileged mechanism, but similarity across foreign APIs or generic naming does not by itself justify kernel growth; admitted Deepwyrm primitives remain personality-blind and policy-light.
Deepwyrm owns the native kernel ABI and kernel-side object semantics. Wyrmroot owns loader, platform, and userspace policy, including system-image construction.
Shared boot and ABI contracts are coordinated across both projects. Wyrmroot consumes generated ABI definitions from an exact Deepwyrm revision, allowing its policies and compatibility layers to evolve without becoming kernel foundations.
- Architecture and plan index
- Pre-phase-zero invariants
- DW0 implementation plan
- Native ABI schema and generated artifacts
- The kernel as built
- Licensing policy
- Contributing
Deepwyrm currently retains a GPL-2.0-or-later repository fallback and current component set. New wholly first-party project code defaults to GPL-3.0-or-later; GPLv2-compatible lanes are selected when actual source provenance or combination requirements call for them. See LICENSING.md for the current component state and workspace-aligned provenance rules.