Parity with a frozen target, not a moving one
The 1.0 contract is the 55-line feature inventory frozen at the C++
v1.0.0 tag. All 55 lines are implemented in JefeRust. Newer JefeOS
features—including its 1.1.x OpenStack and Xylem workload-supervision work—belong
to the separate C++ release lane and are not claimed here.
What ships
- A native Rust x86_64 kernel with its own scheduler, memory manager, drivers, filesystems, networking, cryptography, shell, and Linux/POSIX compatibility path.
- An experimental in-kernel framebuffer/window-manager implementation is compiled into the image. A functional GUI was not a 1.0 goal and this path was not exercised by the 1.0 runtime gates, so it is not presented as a supported desktop.
- Full read/write NTFS support across resident and non-resident data, fragmented allocation, directory-index growth and collapse, and bounded metadata mutation paths.
- Kernel support for selected native and Linux-compatible userspace, including the separately deployed Node-based Discord workload exercised on the golden image.
- A separate public examples bundle with 19 static native
INT 0x80ELF programs, two text fixtures, checksums, and a fail-closed SFTP installer. - A sanitized copy of that bot's generic userspace logic, supplied as a separate ZIP for inspection and experimentation; it is not embedded in the ISO.
The image and the proof share one identity
- Titan clean build: 11/11 release tests, 8/8 release-mutation checks, and 9/9 KVM/QEMU checks.
- Host policy gates: 533 passes plus 11 named policy skips out of 544 accounted tests; zero unaccounted failures.
- Independent runtime checks: Windows QEMU passed 9/9, and two consecutive Hyper-V runs each passed 219 tests with the same five named compatibility skips.
- Golden workload: separate operational Discord status captures reported the same image boot and bot PID as reported uptime advanced past seven hours; commands succeeded, and each captured status reported READY with matched heartbeat counters. The formal machine-readable two-hour collector gate remained
NOT-RUNand was explicitly waived by the release owner; these observations are not reported as a machine PASS.
This is a kernel release, not a Linux distribution
JefeRust runs selected native and Linux-ABI userspace, but does not claim complete Linux or POSIX compatibility, supported-default SMP, production hardening, or parity with current JefeOS master. The source repository remains private. The ISO is a runnable research release. A functional userspace GUI—including stable display/input interfaces, a compositor, application surfaces, and interactive runtime proof—is a formal 2.0 goal for both JefeRust and JefeOS.
Boot the kernel, run examples, or inspect the bot
JefeRust 1.0.0 ISO
⬇ Download the ISONative userspace examples
⬇ Download userspace examplesSanitized Node bot source
⬇ Download bot sourceZIP plus SFTP fits JefeFS; a host-authored VHD does not
JefeOS can distribute its examples on an NTFS VHD because Windows can author that filesystem. JefeRust uses JefeFS for its first data disk, automatically formats an unrecognized disk, and has no Windows JefeFS writer. Attaching the JefeOS examples VHD as JefeRust's first disk would therefore destroy its NTFS contents. The public JefeRust equivalent is a deterministic ZIP whose installer verifies the exact file set and checksums before uploading over SFTP.
The archive contains the same 19-program public examples allow-list used for JefeOS, built as
static x86_64 ELFs for JefeRust's native INT 0x80 ABI, plus two text fixtures.
It excludes bot code, credentials, private endpoints, runtime state, and mutable disks. A fresh
extraction of these exact ZIP bytes was installed on the exact release ISO in a disposable VM;
argvtest, cat, grep, wc, sort, and
sigtest passed, while hello returned its intentional exit code 42.
Sanitized and deliberately not turnkey
The archive contains no deployed token, channel or user IDs, private hosts, private model names,
state, logs, or installed dependencies. The copyright owner publishes this source for inspection
and direct use under its included UNLICENSED and private: true package
terms. No downstream redistribution, relicensing, sublicensing, or republication license is
granted. The package does not invent a different license, pins its sole dependency exactly to
ws 8.21.0, and requires operators to supply their own configuration and credentials.