Version: 0.2.x
Language: Dust Programming Language (DPL)
The XDV kernel is the x64 kernel component for XDV OS. It provides the K-Domain runtime and defines hardware-gated Q-Domain and Phi-Domain service surfaces.
The repository currently contains two kernel runtime entry profiles:
sector/xdv_kernel/src/kernel.ds
Dust kernel entry (kernel_start) and core runtime boot sequence.sector/xdv_kernel/src/kernel_runtime_shell.asm
bare-metal runtime shell profile (US keyboard layout, command buffer, dispatcher, and console command execution path used in VM bring-up flows).
K-Domain: classical x64 execution path (active on supported hardware).Q-Domain: hardware-gated quantum domain interfaces.Phi-Domain: hardware-gated phase-native interfaces.
When Q/Phi hardware is not present, domain probes and operations are expected to report domain-not-available behavior.
The workspace defines 13 sectors:
xdv_bootxdv_memoryxdv_cpuxdv_driversxdv_kernelxdv_dalxdv_qdomainxdv_phidomainxdv_cdsxdv_umfxdv_hypervisorxdv_sdbmxdv_odt
Each sector contains src/*.ds and sector tests (*_tests.ds).
Validate all sector source directories:
dust check sector/xdv_boot/src
dust check sector/xdv_memory/src
dust check sector/xdv_cpu/src
dust check sector/xdv_drivers/src
dust check sector/xdv_kernel/src
dust check sector/xdv_dal/src
dust check sector/xdv_qdomain/src
dust check sector/xdv_phidomain/src
dust check sector/xdv_cds/src
dust check sector/xdv_umf/src
dust check sector/xdv_hypervisor/src
dust check sector/xdv_sdbm/src
dust check sector/xdv_odt/srcxdv-bootis responsible for loadingkernel.binand transferring control.xdv-osimage build composesboot.bin+kernel.bininto the xdvfs image.- kernel runtime output should be validated in VirtualBox against the expected boot contract chain.
docs/README.mddocs/boot_runtime_flow.mddocs/sector_reference.mdspec/XDV-Kernel-v0.2-Specification.mdxdv-kernel_white_paper.mdCHANGELOG.md
Copyright (c) 2026 Dust LLC. See LICENSE.