ITISYOU_OS
PRE-ALPHA

System Releases

Early development builds are intended exclusively for VM environments. Releases are published only with verification evidence attached.

Physical-Hardware Warning

ITISYOU OS is an experimental, pre-alpha research kernel. It is developed and verified exclusively inside QEMU with project-generated disposable disk images. Do not install it on physical hardware, point it at a real disk, or expect it to preserve data. There are no production builds.

Version tags

EXPERIMENTAL VERIFIED

Each tag marks a commit whose full gate and CI run passed: evidence of a verified state. Since v0.8.1 a release can also carry a public download: boot images built by CI and published with their SHA-256 digests. Earlier tags have none. The latest release is v1.0.0; earlier images stay downloadable, unchanged.

Release tags with commit, date, CI run and summary
TagMilestoneCommitDateCI runDeliveredDownload
v1.0.0 V1.0 — Experimental Personal OS (VM-verified) 5593e50 2026-09-14 none — local build (GitHub CI pending) ITISYOU OS V1.0 — an experimental personal operating system for virtual machines, on top of everything through V0.10 and the V0.11 AI-native layer. The AI layer: a read-only system view, a diagnostic model trained at build time from synthetic scenarios and pinned by digest, a Ring 3 inference service, and a diagnostic agent that can only file proposals the kernel re-checks against its own facts and the console approves, with kernel execution, verification and rollback. V1.0 itself is reliability and security: IPC authority scoped to the channels a grant names; a Ring 3 syscall fuzzer (300,000 random syscalls across three capability sets, no crash or hang) and a decoder mutation fuzzer (48 untrusted-byte decoders, a million inputs each) that found and fixed real panics; long-use leak accounting; and a whole-attack-surface adversarial review — 37 findings, each verified by an independent refuter — that fixed every high-severity defect and 18 findings in all: unhandled CPU exceptions a Ring 3 program could turn into a kernel panic, a package launched outside its signing key’s scope, an ICMP responder a remote ping flood could recurse into the stack guard, and more; the remaining seven mediums are documented availability limits a capability holder or a hostile disk can impose on a single-user VM. Physical hardware is explicitly unsupported. VERIFICATION: built locally (pinned nightly-2026-08-01) and verified by the full local QEMU matrix, two-clean-build bit-for-bit reproducibility and UEFI+BIOS boot-tests; GitHub CI could not run (the repository is private with no Actions minutes), so this release is locally verified with CI to follow — see /download. Images + SHA-256
v0.10.0 V0.10 — Userspace System c936bc7 2026-09-13 34782271250 A userspace system on top of V0.9. Background programs keep running while the console is busy: bounded slices at audited safe points, with the kernel still non-preemptible. A process tree: only a parent collects its child, wait_nohang, sleep, orphans handed on, ps and kill. /sbin/init as pid 1 starts and supervises the services named in /etc/init.conf, reports them to a kernel-checked service table, and is restarted by the kernel if it dies. Program arguments, a Ring 3 shell that borrows the console’s input, filesystem space reclamation, and Ring 3 applications on the live desktop with click-to-focus and keys routed to the focused window. Fixed on the way: a denial of service in every earlier release (the kernel wrote through user pages the program could not write), guard pages for the syscall and kernel-task stacks, a mouse-packet framing bug, an interrupt-unsafe input queue, and a gui_present that checked existence instead of ownership. UEFI and BIOS boot images built by the release CI run on Linux, published with SHA-256. Images + SHA-256
v0.9.0 V0.9 — Transport, Interrupt Cutover & Trust f06673e 2026-09-13 34760629701 TCP from Ring 3 (connect and listen, with retransmission verified against the host’s own TCP stack), a DHCP client and IPv6 foundations; ACPI table discovery, the I/O APIC cutover that retires the 8259 PIC, and ACPI S5 power-off; a package-signing key hierarchy under an offline root, with scoped certificates and signed revocation; audit anchoring off the disk; guard pages under the kernel’s Ring 3 interrupt (RSP0) and double-fault stacks (not yet the syscall stack); and a fix for a kernel panic any program could trigger with a null pointer and a zero length. UEFI and BIOS boot images built by the release CI run on Linux, published with SHA-256. Images + SHA-256
v0.8.1 V0.8 — release-integrity closeout bf32b53 2026-09-13 34750316003 No new kernel function. Corrects v0.8.0, whose kernel reported 0.7.0-dev: the version is now consistent everywhere and a build gate fails on any future drift between the kernel, the status metadata and the requirement matrix. Stale public claims corrected; the site is verified in a real browser. First public download: reproducible, checksummed UEFI and BIOS boot images built by CI and boot-tested byte for byte. Images + SHA-256
v0.8.0 V0.8 — Networking, Authenticity & Hardening 84d6b24 2026-09-05 33988391309 e1000 + ARP/IPv4/ICMP/UDP/DNS with port-scoped Ring 3 sockets; Ed25519-signed packages; capability handles as the enforcement path; userspace filesystem writes; APIC/MSI-X; xHCI; persistent hash-chained audit; SMEP/SMAP/UMIP. Its kernel misreported its version (0.7.0-dev), corrected in v0.8.1. —
v0.7.0 V0.7 — System Platform 00b5eea 2026-09-03 33812762322 Capability model (default deny, no amplification), filesystem sandbox, service supervisor, ITPKG packages with SHA-256 integrity, atomic update/rollback/recovery across reboots, audit trail. —
v0.6.0 V0.6 — Hardware Expansion cccf5a7 2026-09-02 33635955858 Device/driver model, PCI BARs and capabilities, UHCI + USB HID keyboard, AC97 audio output, unified input. —
v0.5.0 V0.5 — Graphics + Input + Desktop 5be3c0c 2026-09-02 33628363046 Framebuffer graphics, ownership-isolated compositor, GUI syscalls, PS/2 keyboard and mouse, interactive desktop. —
v0.4.0 V0.4 — Preemption + Persistent Storage b1af235 2026-09-02 33619289190 Timer-driven preemption of Ring 3, NVMe write + flush, ITFS with crash-consistent superblocks and reboot persistence. —
v0.3.0 V0.3 — Process Isolation + Storage Foundation d83942b 2026-09-02 33609090873 Per-process address spaces, concurrent processes, spawn/wait, IPC, PCI enumeration, read-only NVMe. —
v0.2.0 V0.2 — Userspace Foundation ee8d57c 2026-09-02 33604047455 Ring 3 ELF64 programs, strict loader with W^X, syscall ABI, crash containment. —
v0.1.0 V0.1 — Kernel Foundation 5a4b008 2026-09-02 33599387686 Bootable x86_64 kernel: memory management, interrupts, scheduler, VFS/initramfs, shell, QEMU test harness. —

CI runs are GitHub Actions runs in the project repository (https://github.com/leelaravind/itisyou-os); the evidence is summarized in the requirement matrix. The commit column is the commit the listed CI run built; from v0.8.1 on that is the release’s content commit, and the tag sits on the status-stamp commit that follows it.

What a release contains

Since v0.8.1 a release publishes the boot images its CI run built and booted — never a local rebuild — under /downloads/<tag>/. Earlier tags carry no images.

  • itisyou-os-<version>-x86_64-uefi.img — UEFI boot image (raw disk, GPT with an EFI system partition)
  • itisyou-os-<version>-x86_64-bios.img — BIOS boot image (raw disk, MBR)
  • SHA256SUMS.txt — the SHA-256 of both images, in the format sha256sum -c checks
  • on /download — the release commit, the CI run that built the images, where they were booted, reproducibility, known limitations

Release rules

  1. EVIDENCE FIRST

    A release is cut only from a commit whose full verification gate (build, host tests, the complete QEMU matrix, website, secret scan) passed locally and in CI — and the evidence ships with it.

  2. CHECKSUMS ALWAYS

    Every artifact is listed in a SHA-256 manifest generated by the same build that produced it. Verify before booting.

  3. VIRTUAL MACHINES ONLY

    Artifacts are disk images for virtual machines (QEMU is the tested environment). They are not installers, and no release targets physical hardware.

  4. VERSION MEANS VERSION

    The kernel, the status metadata, the requirement matrix and the tag must name the same version — the build fails otherwise (added after v0.8.0 shipped a kernel reporting 0.7.0-dev).

  5. NO SILENT REPLACEMENT

    Published artifacts are immutable; a fix means a new version, never an overwritten file.

Current build status Changelog