Bastion: the x86-64 kernel is being rewritten out of Rust
The Bastion page has been rewritten to describe the current system. The work is narrower than the page used to claim, and more specific: the x86-64 kernel is being moved out of Rust and into Vulkgryph (.vg), subsystem by subsystem. Kernel Rust is down to about 6,400 lines from an August peak near 26,600, with scheduling, timer and interrupt sequencing, exception containment, paging, ACPI parsing, and the IOMMU path already across. Each boundary is qualified across five consecutive runs on real hardware, and the superseded Rust is deleted rather than left in place.
The page also now states the limits, because the useful claim is the one that is still false. Builds accept a natively compiled kernel object only when it is byte-identical to the output of the Rust reference compiler, and the reference is still used where that match is unavailable — so full self-hosting cannot be claimed yet. Native object staging across the whole kernel, the operator shells, C interoperability for ACPI, the wireless data path, and the trust anchor all remain open. There is no release date.
Two things named on the old page are gone. The portable bytecode runtime and the filesystem, process services, syscall ABI, and security core built around it were declared legacy in July 2026 and are deliberately out of scope; they may be revived and converted to .vg later. The controlled language previously called Substrate is now Vulkgryph.