Frames Kernel
Processes, memory, scheduling, interrupts, syscalls, SMP and kernel-owned runtime state form the independent core.
A clean-stack computing platform.
Compatibility lives at the edge. Frames itself is built around an independent kernel, Nexus-native development, Frames-owned userspace and explicit platform contracts.
Nexus
Native compiler/toolchain, kernel profile, ABI contracts and FEX application builds.
Frames Services
Storage, networking, recovery, update, security and hardware-facing system services.
Native FEX software
A Frames-native executable and application model rather than inheriting another OS runtime as the base.
VFS + HelixFS direction
VFS foundations are active today. HelixFS is the planned native storage architecture and remains future work until its write path is independently proven.
Frames Lab
Future first-party development, testing, profiling, snapshots and isolated compatibility environments.
SECURITY BY BOUNDARY
Dangerous capabilities stay off until they are earned.
Frames 0.9.32 now has an externally certified bounded write/integrity path on a dedicated sacrificial QEMU NVMe target. The boot/system volume remains read-only, and physical-machine promotion plus physical persistent-media writes are not implied by VM success. Those capabilities retain separate gates.
Boot NVMe read-onlySacrificial Write Gate 1 PASSFail-closed promotionRecovery invariantsExplicit trust domainsEvidence artifacts
Frames development rule:
Implementation is not certification. Certification is not physical-hardware promotion. Each boundary has to be earned independently.
Implementation is not certification. Certification is not physical-hardware promotion. Each boundary has to be earned independently.