Release state, open limits, Linux compatibility, and the underlying evidence. The long implementation ledger is still here, but it no longer has to be the first thing you read.
Release update September 15, 2026 · JefeOS 1.2.0 · JefeRust 1.2.0
JefeOS and JefeRust are separately released kernels. JefeRust 1.2.0 adds Linux ABI, account/credential, enrolled-identity and operator increments with bounded-memory remediation evidence; it does not claim complete POSIX parity or indefinite stability.
Qualification boundary: JefeRust 1.2.0 is accepted under the reviewed corrected composite policy. Its one-hour remediation target passes v2 with six natural-major checkpoints and twelve representative waves. The original v1 FAIL and non-live legacy-verifier FAIL/NOT-RUN outputs remain preserved. OLS is diagnostic; finite bounded evidence is not an indefinite-stability claim. Exact evidence and limits.
As of September 1: 121 shipped, 5 in progress, 4 planned. Formula: (shipped + 0.5 × in progress) / 130. This is a scoped editorial checklist, not a measure of overall OS completion.
These are dated, practical constraints that change how the capability list should be read. The live engineering queue remains the source for current issue state.
JEFEOS_SMP=0; Rust's SMP feature is also off by default. fork fails closed if SMP is enabled.sysinit → boot → default completes on the VM and real apk info works. The remaining boundary is physical-console input through getty to a verified /bin/login prompt.Each tier adds a harder workload boundary. Tier 4 includes a real Alpine rootfs and package operations. Tier 5 now completes OpenRC's boot sequence; physical-console getty-to-login proof remains.
Static binaries and basic process startup.
GreenFull libc startup, TLS canary, brk, signals, and thread ID setup.
GreenPT_INTERP, file-backed mmap, and real dynamic workloads.
GreenReal rootfs, dirfd-relative calls, and apk package install/run.
GreenOpenRC sysinit → boot → default completes and real apk info works. Physical-console getty-to-login proof remains.
The complete chronological record is collapsed underneath.
The diagnostic-accuracy release: signal path hardened, NTFS internal-index writes refused instead of orphaning subtrees, POSIX modes on NTFS, and a machine-scored manifest bound to an independent clean build, a QEMU boot proof, the 22-workload application gate with signed-boot join, and 5/5 fault-injection recovery.
The qualified Rust kernel shipped its bounded Xylem service, durable-authority, and stateless panic-recovery increment.
The Rust kernel completed its frozen 55-line parity contract and exact-revision release gates, with the disclosed bot-soak waiver and GUI runtime boundary.
Smoke and syscall suites now fail closed when VM transport is unavailable.
A real Node workload exposed a user/kernel boundary bug in getdents64; the fixed path is SMAP-safe and regression-tested.
Xylem workload supervision can snapshot, reap, and respawn a wedged process group without rebooting the VM.
Fault-survivable copy boundaries now cover the native INT 0x80 path as well as the Linux ABI.
Spawn/join, thread-local state, cross-thread events, and logging run on clone plus futex.
Expanded man pages and command suggestions reached both shell implementations.
Nothing was discarded. Open a ledger when you need the long-form evidence, then narrow it by text, state, kernel, or category.
JefeRust 1.0 proved its frozen 55-line baseline; 1.1 adds a bounded Xylem increment without claiming full current-C++ parity. This broader table includes other C++ work, so a difference is not automatically a JefeRust release failure. “Compiled; 1.0 untested” remains the historical GUI boundary.
| Feature | JefeOS C++ | JefeRust |
|---|