Public release roadmap

Two kernels. Two release lanes.

JefeRust 1.0 has shipped against the frozen JefeOS 1.0 baseline. JefeOS 1.2 is advancing a separate reliability and cross-vessel failover program.

Status snapshot: August 15, 2026

How to read this roadmap: implemented features and releasable evidence are different states. A lane normally ships only when its mandatory gates pass against one exact source revision and its published artifacts. Any release-owner exception stays visible as a waiver and never becomes a fabricated PASS. Dates are deliberately not promised before the evidence exists.
Released · 1.0.0

JefeRust 1.0

The Rust kernel's target is feature parity with JefeOS 1.0.0, not with current JefeOS master.

Feature baseline

  • 55 of 55 frozen JefeOS 1.0 benchmark feature lines are implemented and the final blocking accept interruption parity defect is closed.
  • Full NTFS write parity landed, including allocation growth, fragmented runs, directory-index growth and shrink, and $MFT growth.
  • Real workload proof exists: the JefeRust Discord bot is running on JefeRust over its native networking and Linux-compatibility stack.

Release decision and evidence

  • No confirmed release-relevant HIGH defect remained at the exact release commit.
  • A clean, pinned Titan build produced the published ISO from 1273bcbabf63058b5087a2c3689272e1b711f1f5.
  • Independent QEMU and consecutive Hyper-V parity runs passed against that exact artifact.
  • Provenance, warning-floor, test-accounting, and claim true-up gates passed before publication.
  • The formal machine-readable two-hour bot-soak gate remained NOT-RUN and was explicitly waived by the release owner. 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. That evidence is not reported as a machine PASS.
Not a JefeRust 1.0 gate: JefeOS 1.1/1.2 features such as OpenStack guest support, Xylem workload supervision, cross-vessel failover, or enabled SMP. Read the release evidence and download the exact image.
1.2 development

JefeOS 1.2

The C++ kernel's next release is centered on trustworthy recovery, exact evidence, and surviving a whole-vessel failure.

Target progress

  • OpenStack-managed guest: proven in the nested-KVM lab. The image was uploaded through Glance, launched by Nova, and operated through Horizon using the conservative BIOS + IDE + E1000 profile. Its ISO 9660 config-drive applied hostname and SSH keys, then networking came up through DHCP.
  • Cross-vessel failover: foundations landed. Membership, failure detection, and a failover primitive exist; fencing, workload binding, and real panic-to-peer proof remain.
  • Diagnostic accuracy: active. Reboot-reason tracking is complete; exact build identity and the broader measured-vs-hypothesis audit remain.
  • Bot stability: acceptance active. The residual Node/libuv strand is measured outside the kernel wake path, but the exact release candidate must still pass the clean stability soak.

Mandatory release proof

  • No confirmed release-relevant HIGH defects.
  • One-command, machine-readable evidence from a clean pinned build.
  • Independent QEMU and Hyper-V boot/regression proof with exact artifact identity.
  • A four-hour production-equivalent bot soak with zero organic harvests, plus separate deterministic Xylem recovery proof.
  • Honest accounting, immutable provenance, current public claims, and enforced warning floors.
Release rule

Evidence closes a lane—not a percentage.

Both releases use the same discipline: a clean source revision, reproducible artifacts, exact build identity, independent runtime proof, fail-closed test accounting, and immutable checksums. A green-looking stale artifact, skipped suite, transport failure, or recovered organic crash does not count as a pass.

After 1.2

JefeOS 1.3

Make clean CI, cross-kernel conformance, warning reduction, Tier-5 workload truth, and self-service lab tooling the normal development loop.

Major boundary

JefeOS 2.0

Supported-default SMP, JSL-2 native containers, production-facing security contracts, stable external interfaces, and justified density work.

North star

Xylem

Continue from membership and local supervision toward fenced cross-vessel recovery, replicated service placement, and eventually stateful cells.