Downloads
The audited SMP0 release
Bootable x86_64 ISO
Download ISOKernel ELF
Download kernel ELFThese website downloads are public. The corresponding GitHub release record and Forgejo release record require repository or network access. Only this audited pair is published; no diagnostic kernel or SMP1 image is substituted.
What ships
Compatibility and operations
- Linux ABI increments, offline package lifecycle and a bounded two-generation CPython service—not complete Alpine/OpenRC or CPython support.
- Account and credential lifecycle, enrolled identity, local elevation and audit.
- Bounded config-2 JSON/ISO9660 consumption and hostname/Ed25519-key application on a disposable guest—not production OpenStack qualification.
- Read-only FAT32, bounded copy/rename, HTTP service, scoped TLS/WebSocket consumers, scheduling and operator commands.
- Integration regressions, private-anonymous discard reclamation and AHCI timeout ownership quarantine, with remaining parity gaps recorded explicitly.
Qualification
Bounded post-GC remediation: PASS
The completed four-hour workload soak established the original memory-growth failure. Targeted remediation then used unchanged Node 18.20.8 and app code with --max-old-space-size=16 --optimize-for-size, which implies a 1 MiB semi-space.
The full one-hour target observed six natural-major-GC checkpoints and all twelve representative workload waves. Its post-GC free-memory range was 495 pages, within the 512-page bound. All 19 corrected target criteria passed, including eligibility, coverage, memory floor, task bound, safety, progress and provenance.
The reviewed v2 gate separates these jobs: the four-hour gate evaluates sustained loss; the short remediation gate requires a bounded post-GC footprint. OLS remains visible as a diagnostic (677.97 pages/hour), not a second short-run veto. A negative control at 520 pages still fails.
- Fresh source and independent clean builds, provenance and release-relevant HIGH-queue checks passed.
- Host accounting: 702 passes, zero failures/errors and 12 named Windows-only skips.
- Compiler warnings: 178 against the retained ceiling of 184, with no new warning identities.
- Build-bundle QEMU boot was separately measured. Unaffected workload checks and genuine deterministic recovery evidence were retained through explicit source equivalence.
Preserved history and limits
The original failures remain in the record
The original four-hour and target-v1 failures were not overwritten. The non-live legacy verifier exited 1 with JG5 FAIL, explicitly skipped JG4 NOT-RUN, and a derivative manifest-schema provenance-bound failure. The corrected qualification is recorded separately; this is not an all-green legacy manifest.
This finite evidence does not prove indefinite memory stability, absence of every leak, a global 19 MiB memory quota, or a four-hour optimized-profile soak. Supported SMP, mount/namespaces, a general live VMA registry, global commitment/OOM policy, complete POSIX parity and production-security certification remain outside the release scope. Existing Xylem limitations remain: no new consensus, partition-safety or generalized-placement claim is made.
Boot safely
Use a disposable VM
qemu-system-x86_64 -cdrom jeferust-1.2.0.iso -m 1024
The ISO is a live boot medium, not an installer. Hyper-V Generation 1 is also used by the release path. Any attached writable disk can be modified: use disposable copies, never irreplaceable data. Do not attach the C++ JefeOS NTFS examples disk as JefeRust's first disk; an unrecognized first disk may be formatted.
Historical releases remain available: JefeRust 1.1.0 · JefeRust 1.0.0. Temporary qualification infrastructure was cleaned up; publication does not deploy the OS to the development bot.