See the Bastion project page for the implementation status sidebar, component breakdown, and project log.
What exists
Bastion currently boots on real x86-64 hardware through UEFI. Current work includes a hand-written assembly machine core, VGA framebuffer, Ethernet driver, TCP/IPv4/ARP stack, TCP shell, live kernel push, DMA allocator, PCI, serial I/O, PS/2 keyboard input, ACPI integration, service execution, and a controlled language toolchain.
Bare-metal x86-64 kernel with UEFI boot, interrupt tables, context switching, syscall trampolines, and atomics.
Intel Ethernet path with ARP, IPv4, TCP, a guarded TCP shell, and live kernel push over the network.
Framebuffer, PCI, DMA allocation, serial, keyboard, ACPI, and USB-controller work are under active development.
Controlled process descriptions compile to native x86-64 ELF binaries for Linux and bare-metal execution.
Current direction
The direction is a small, inspectable system with explicit boundaries: boot, interrupts, drivers, network state, service behavior, and remote operation are kept visible rather than hidden behind a general-purpose operating environment.
Current limits
Bastion is still an active engineering system. It needs production hardening, external documentation, naming cleanup, and validation across more machines before it should be treated as deployable software.