Skip to content

Releases

AriCodeOS 0.19.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 21 Nov 01:22

AriCodeOS 0.19.0 (2026-11-21) is the version of a desktop worth the name (ADR 0078), of the first steps onto the reference laptop's GPU (ADR 0080, 0083, 0086), and of what a second laptop, a Tiger Lake Lenovo, taught. It covers ten ADRs (0078 to 0087) and incidents 0059 to 0066. The whole system passed its full test suite with 1 and with 4 CPUs, and the development build it comes from ran on the reference laptop, a 2013 ASUS with a Core i3-3217U.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.19.

What is new

  • The desktop (ADR 0078, 0079, 0081, 0085):
    • a toolkit of its own, with Inter and JetBrains Mono, menus, modal dialogs, a clipboard, a dark appearance and notices;
    • a bar with a clock, and a dock that offers the applications;
    • windows drawn in two buffers, so no frame is shown half drawn;
    • windows resized by their edges and corners, and full screen with F11 or a window's zoom circle;
    • the panel's own resolution when the firmware does not offer it.
  • The owner's remote screen: screenshot, from the console, an SSH session or the Terminal, prints the screen as a QOI image in Base64. Applications cannot ask for it, there is at most one copy every 2 s, and the screen says when a copy was taken.
  • USB plug and play on the xHCI (ADR 0087):
    • a keyboard or mouse plugged in while the system runs works without a reboot;
    • unplugged, it releases every key and button it held;
    • the boot stick is never put at risk by it.
  • One path to the hardware (ADR 0080):
    • threads in a process (ADR 0082) and memory for big programs (ADR 0084);
    • a software 3D renderer that draws in bands on every processor.
  • The HD 4000 GPU (Intel Ivy Bridge only):
    • its engine is driven by the kernel, with its clock and a heat brake (ADR 0083);
    • compute runs on its EUs, and their registers are cleared between clients (ADR 0086).
    • Other GPUs are left as the firmware set them.
  • Power-off (incident 0065):
    • it now runs as Linux and FreeBSD run it: on the boot CPU, with the GPEs disabled, in two writes, and with the FADT's extended blocks read;
    • if the power still stays on, the last line on the screen says why.
  • Diagnostics (incident 0064):
    • diag names the machine, its ACPI devices and its power-off registers;
    • diag places any DMA fault against the driver's own memory;
    • acpidump saves the DSDT, SSDTs and FADT, never MSDM, SLIC or serial numbers.
  • Measured on real hardware (docs/performance.md, run bench). On the reference laptop's Core i3-3217U:
    • two threads exchange 218 000 to 237 000 IPC messages a second;
    • a request to a service in another process takes 17 to 23 µs;
    • an empty system call takes 260 ns.
  • The heap is TLSF in the kernel and in programs (incident 0066). Large allocations no longer turn quadratic.
  • Certificates:
    • Mozilla's roots, from NSS master, are 112. Buypass Class 2 and 3, Certigna, and QuoVadis Root CA 1 G3 and 3 G3 left Mozilla's store.
    • The public suffix list is current.

Trying it

  • From 0.18.0: run update, upgrade and reboot. This index names the desktop profile for the first time, so update profile add desktop, then update and upgrade, installs the desktop's apps, on sticks with AriFS v2.
  • From 0.17.0 or earlier: these updaters refuse an index with a line they do not know, such as this one's profile line. Go to 0.18.0 first: run update add https://github.com/AriCodeLabs/AriCodeOS/releases/download/v0.18.0/, then update, upgrade and reboot, then remove that source again with update remove.
  • USB sticks. Decompress with xz -d first, write to a stick you can wipe, then boot a UEFI x86-64 machine with Secure Boot off (see docs/hardware.md).
    • aricodeos-0.19.0-usb.img.xz: the base system, with the text console.
    • aricodeos-0.19.0-desktop-usb.img.xz: the same system with the desktop profile installed. It boots into the desktop, and session shell goes back to the console.
    • For a Spanish keyboard, add kbd=es to aricodeos/cmdline.txt on the stick's EFI partition.
  • Container: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.19.0 boots the base stick in QEMU, with the ari> shell on your terminal (quit with Ctrl-A X).

Files

  • aricodeos-20.img, index, index.sig and the five *-6.aripkg packages: the public update source, signed with the release key (keys/release/).
  • aricodeos-0.19.0-usb.img.xz and aricodeos-0.19.0-desktop-usb.img.xz: the USB sticks.
  • THIRD-PARTY-NOTICES.txt: the licences of the crates.io crates and fonts the images include. It is on the sticks too.
  • SHA256SUMS: the checksums of all of the above.

Known limits

  • On the Tiger Lake Lenovo the new power-off has not been tried yet, and the cause of its xHCI's DMA fault waits for the next run.
  • External USB hubs on the xHCI, and a USB stick plugged in after boot, are not supported yet.
  • The kernel has no IPC fast path yet.
  • A PS/2 pointer that resets itself is set up again only at the next boot.
  • A program hung for good keeps its process until the desktop ends.

Authorship and acknowledgements

AriCodeOS is created by Edwin F. Veliz Jaramillo (lynxcraft), who conceived the system, its capability model, its architecture and its development method, directed every phase and tested it on real hardware. Code and documents were written with the help of AI coding assistants working under the author's direction; the design decisions and the responsibility for them are the author's (AUTHORS.md).

The author thanks the teams behind the AI technologies used to build AriCodeOS: Anthropic for Claude and Claude Code, OpenAI for Codex, and Google for Antigravity.

AriCodeOS 0.18.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 05 Nov 01:21

AriCodeOS 0.18.0 (2026-11-05) is the version of the optional desktop (ADR 0074). Every machine runs one base system, and the desktop is installed on top of it by the owner who wants it. The release covers six ADRs (0072 to 0077) and incident 0058. The whole system passed its full test suite, with 1 and with 4 CPUs, and ran on the reference laptop, a 2012 ASUS with a PS/2 keyboard and touchpad.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.18.

What is new

  • AriFS v2 (ADR 0072):

    • copy-on-write replace of files up to 16 MiB;
    • a table kept in two copies;
    • delete and rename;
    • a 64 MiB ARI0 on new sticks.

    Packages can be up to 8 MiB. Sticks written before 0.18 stay on v1.

  • Signed driver packages (ADR 0073): the design of three trust levels. It is not built yet.

  • Profiles and the desktop session (ADR 0074, phases A and B):

    • session desktop boots into the compositor and the launcher;
    • Ctrl+Alt+Backspace returns to the text console;
    • a signed index can name profiles, which update profile add follows.
  • The PS/2 keyboard and touchpad in the desktop (ADR 0075): a laptop needs no USB keyboard.

  • The desktop's applications (ADR 0074, phase C):

    • a launcher, a terminal, an editor and a file manager over the owner's folder home/, and settings;
    • each app has a capability of its own, granted only to that signed package.
  • Text beyond ASCII (ADR 0076):

    • the Spanish keyboard is the one Linux types, with dead accents, checked key by key against xkeyboard-config;
    • text is UTF-8 throughout, and the console font shows Latin-1 and €.
  • Windows can be closed (ADR 0077):

    • every window has a close box;
    • the editor asks before it discards changes;
    • a window whose program does not answer is marked "(not responding)" before its program's session is ended.
  • The pointer follows the hand (incident 0058): the compositor waits on every input device at once. It used to read them in turn, which left the touchpad behind on the laptop.

  • Certificates:

    • the eMudhra intermediates compromised in October are refused;
    • Mozilla's 117 roots are unchanged;
    • the public suffix list is current.

Trying it

  • From 0.17.0: run update, upgrade and reboot. A machine updated in place keeps AriFS v1 (ADR 0072), so it cannot take the desktop's apps.
  • From 0.16.x: update to 0.17.0 first; see its release notes.
  • USB sticks (decompress with xz -d first, write to a stick you can wipe, then boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md):
    • aricodeos-0.18.0-usb.img.xz: the base system, with the text console.
    • aricodeos-0.18.0-desktop-usb.img.xz: the same system with the desktop profile installed. It boots into the desktop, and session shell goes back to the console.
    • For a Spanish keyboard, add kbd=es to aricodeos/cmdline.txt on the stick's EFI partition.
  • The desktop from this source: this index carries the desktop's apps but no profile line. Updaters before 0.18 refuse an index with a line they do not know, so profiles reach the public source with 0.19, once machines run 0.18 or later. Until then, install the desktop from the desktop stick.

Files

  • aricodeos-19.img, index, index.sig and the five *-5.aripkg packages: the public update source, signed with the release key (keys/release/).
  • aricodeos-0.18.0-usb.img.xz and aricodeos-0.18.0-desktop-usb.img.xz: the USB sticks.
  • THIRD-PARTY-NOTICES.txt: the licences of the crates.io crates the images include. It is on the sticks too.
  • SHA256SUMS: the checksums of all of the above.

Known limits:

  • a PS/2 pointer that resets itself is set up again only at the next boot;
  • under the largest load, the 15-session tables of fsd and the network stack can fill;
  • a program hung for good keeps its process until the desktop ends.

Next: a desktop worth the name, with a toolkit of our own and a macOS-like style (ADR 0078 to come).

AriCodeOS 0.17.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 02 Nov 20:40

AriCodeOS 0.17.0 (2026-11-02) is the version of "compare, then reuse or improve" (ADR 0063). The owner gave "from scratch" its meaning: study the established implementations and their failures, measure ours against them on compatibility and on how fast the system runs, and keep the winner. Each subsystem was compared on its own branch, with its measurements in an ADR and an independent audit. The release covers nine ADRs (0063 to 0071) and six incidents (0052 to 0057). The whole system passed its full test suite (211 scenarios, with 1 and with 4 CPUs) and ran on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.17.

What is new

  • Downloads larger than the updater's memory stream into UPDATE and are verified there (ADR 0064). The 6 MiB limit is gone.

  • SIMD in user programs: the FPU and SSE state is saved on every switch (ADR 0065).

  • Cryptography (ADR 0066):

    • RustCrypto and the dalek crates replace this system's SHA-2, AES-GCM, ChaCha20-Poly1305, Ed25519 and X25519 everywhere, the kernel and AriBoot included.
    • Ours stay where they measured faster or are protocols: ECDSA and RSA verification, HMAC and HKDF, the kernel's generator and the OpenSSH cipher.
  • TLS and X.509: rustls and rustls-webpki, with this system's provider and policy (ADR 0067).

    • TLS 1.2's safe subset is on, and extended master secret is required.
    • The trust anchors are Mozilla's 117 TLS roots.
  • SSH:

    • The server stays this system's: sunset could not end a command properly.
    • It gains mlkem768x25519-sha256 and key re-exchange, and its send path costs 37 % less per byte (ADR 0068).
    • The echo of a key went from 31 to 10 ms in QEMU (ADR 0069).
  • TCP stays this system's: smoltcp's initial sequence numbers proved predictable from two observed ones. Its transmission was rebuilt (ADR 0070):

    • RFC 6298 timeouts, NewReno and SACK;
    • out-of-order data kept, window probes and delayed ACKs;
    • RFC 5961's checks against blind resets.

    The old one stalled at about 3 KB/s on any loss and believed blind resets (incident 0056). On the reference laptop, SSH output went from 0.12 to 1.15 MB/s on the same LAN (incident 0057).

  • WebAssembly: wasmi replaces this system's interpreter and runs 15 to 35 times faster inside AriCodeOS (ADR 0071).

    • Profile v2 accepts the stable features except SIMD, extended constants and multiple memories, within strict limits.
    • A finding of the audit was reported privately to the wasmi project.
  • Other fixes:

    • upgrade says why it fails after a new release replaced the source (incident 0052).
    • xtask refuses unknown options (incident 0053).
    • Console prints over 4 KiB are no longer dropped (incident 0054).
    • The ML-KEM frames fit sshd's stack budget (incident 0055).
  • Third-party notices: THIRD-PARTY-NOTICES.txt lists the 81 crates.io crates the images include, with their licences. It is attached here and is on the USB stick.

Trying it

  • From 0.16.1: run update, upgrade, reboot.
  • From 0.16.0: 0.16.0's updater cannot download this 6.8 MB image, so update through 0.16.1 first; its release notes explain the steps.
  • USB stick (aricodeos-0.17.0-usb.img.xz, attached; decompress it with xz -d first):
    • Write it to a stick you can wipe, then boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md.
    • Check it against SHA256SUMS.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.17.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

These still need decisions from the owner:

  • applications above 32 KiB (AriFS file size);
  • agents outside the trusted base (ADR 0041).

Each incident lists its accepted residuals under "What remains".

AriCodeOS 0.16.1

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 02 Nov 20:40

AriCodeOS 0.16.1 (2026-11-02) is the bridge from 0.16.0 to 0.17.0. The system image of 0.17.0 is 6.8 MB, and the updater of 0.16.0 downloads at most 6 MiB into memory, so a 0.16.0 machine cannot update to 0.17.0 directly. This hotfix gives 0.16.0 only the updater of 0.17 and changes nothing else.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.16.

What is new

  • Downloads go through UPDATE (ADR 0064): a system image is streamed into the UPDATE partition and verified there, so its size is no longer limited by the updater's memory. UPDATE is sealed only after the image verifies, and the copy into the slot is hashed again.
  • upgrade says why it fails after a newer release replaced the one the index named, instead of only "HTTP 404" (incident 0052).

The whole system passed its full test suite (205 scenarios, with 1 and with 4 CPUs) and the performance check with no regression.

Updating

  • From 0.16.0: run update, upgrade, reboot. That installs 0.16.1 (system 17). Then run update, upgrade, reboot again to reach 0.17.0 (system 18).

  • If 0.17.0 is already the latest release when a 0.16.0 machine updates, the first upgrade refuses the 6.8 MB image. Add this release's own source and update from it:

    update add https://github.com/AriCodeLabs/AriCodeOS/releases/download/v0.16.1/
    update
    upgrade
    reboot
    

    After that reboot, update remove N drops that source (update sources lists them), and the next update and upgrade reach 0.17.0.

  • USB stick (aricodeos-0.16.1-usb.img.xz, attached; decompress it with xz -d first): write it to a stick you can wipe, then boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. Check it against SHA256SUMS.

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/). THIRD-PARTY-NOTICES.txt lists the crates.io crates AriBoot and the kernel include, with their licences.

AriCodeOS 0.16.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 27 Oct 23:00

AriCodeOS 0.16.0 (2026-10-27) finishes the failure-pattern review that 0.15.0 started. That release fixed the review's 47 findings and left a few items as stated: two parts of the certificate finding and thirteen informational findings. This one closes them all. Each fix went through the same process: its own branch, an incident, a reproduction before the fix where possible, and an independent audit, repeated until the audit came back clean. Two of those audits found serious problems in a first version, and both were fixed before merging. The release covers eight incidents (0044 to 0051) and five ADRs (0057, 0058, 0060, 0061, 0062). The whole system passed its full test suite (202 scenarios, with 1 and with 4 CPUs) and ran on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.16 · Review: docs/audits/2026-10-25-failure-patterns.md.

What is new

  • Certificate names:
    • A certificate's common name is no longer read as a host name (ADR 0058). Current browsers and libraries behave the same way.
    • A host given as an IPv4 address now matches the certificate's IP address entries.
    • A wildcard can no longer stand on a public suffix such as *.co.uk (ADR 0062). The check uses an extract of the Public Suffix List, which ships under its own licence, MPL-2.0; NOTICE covers it.
  • Cryptography (incident 0044):
    • AES no longer uses lookup tables.
    • Constant-time comparisons are protected from compiler optimisations.
    • Ed25519 verification refuses small-order keys. Before this fix, 1160 of 12 544 forged attempts were accepted; now none are.
    • Keys and handshake secrets are wiped from memory when they are no longer needed.
  • Updates fail closed (ADR 0060):
    • A damaged boot record is rebuilt from the slot the machine actually booted.
    • A damaged downgrade floor refuses stable releases until the owner gives explicit consent.
    • The update server no longer echoes request bytes into its headers.
  • SSH (incident 0046):
    • An authorized_keys line with options is refused, and sshd says so with the line number, instead of ignoring the line silently.
    • Every authentication attempt counts against the limit, including key queries.
  • Kernel (incident 0047, ADR 0057):
    • A closed handle no longer becomes valid again after 65 536 reuses of its slot.
    • The DMA quota is refunded when an allocation fails.
    • Interrupt windows no longer grow with each driver restart.
    • Typed input meant for a program that crashed is discarded instead of reaching the next one.
  • PCI (incident 0050, ADR 0061):
    • A dead driver's interrupt line can no longer silence the driver that replaced it.
    • MSI-X is used only when the device's table is still where it was at boot and the device decodes memory.
  • Tests fixed, not retried: a port-lease test that raced other sockets (incident 0049), and an IOMMU test that read the fault count too early with 4 CPUs (incident 0051).

Trying it

  • USB stick (aricodeos-0.16.0-usb.img.xz, attached; decompress it with xz -d first):
    • Write it to a stick you can wipe, then boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md.
    • Check the stick image against SHA256SUMS.
    • Machines on 0.15.0 update from this page with update and upgrade.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.16.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

These still need decisions from the owner:

  • system image downloads above 6 MiB;
  • applications above 32 KiB (AriFS file size);
  • agents outside the trusted base (ADR 0041);
  • the driver licence (ADR 0042).

Each incident lists its accepted residuals under "What remains". EHCI hubs and split transactions can only be verified on hardware.

AriCodeOS 0.15.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 27 Oct 19:31

AriCodeOS 0.15.0 (2026-10-27): the failure-pattern release. A week of public vulnerability news (OpenSSH, PHP, Node, Java's TLS, rustls' certificate checks) was read for the methods behind each flaw rather than the language, and every place AriCodeOS made the same kind of mistake was fixed: 47 findings, sixteen incidents (0028 to 0043) and seven ADRs (0049 to 0055). Each fix was reproduced before it was changed where a reproduction was possible, each branch had an independent audit, and the whole system passed its full test suite (197 scenarios, with 1 and with 4 CPUs) and ran on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.15 · Review: docs/audits/2026-10-25-failure-patterns.md.

What is new

  • Authority closed on every path: the file service refuses a request whose session is gone, and sshd keeps its host key in a directory of its own (ADR 0050, migrated on first boot with the fingerprint unchanged); every graphical program gets a compositor session that alone owns its windows (ADR 0052); applications can no longer ask for the raw keyboard (ADR 0053).
  • Devices checked, not trusted: the addresses a PCI device reports are checked against its BARs and the kernel's own memory before anything is mapped (ADR 0051); virtio drivers keep their own queue bookkeeping and bound every device-reported offset; a driver's device loses access to a client's buffer once the driver gives it back (incident 0039).
  • Error paths that clean up: a process that fails to start frees all its memory (incident 0041), a partial IOMMU mapping is rolled back, init closes what a failed launch opened, and the supervisor no longer relaunches a service it gave up on (incident 0038).
  • Storage and parsers bounded: GPT tables are read as a stream whatever size they declare, AriFS checks its layout and refuses to keep working on a half-applied commit (incident 0032), and the WASM interpreter's fuel now counts work, imports included (incident 0042, ADR 0055).
  • Network and cryptography: TCP connections stuck closing are released, port 22 is reserved for sshd, DHCP and DNS identifiers are random, the SSH server requires strict key exchange and signs in constant time (incident 0035), certificates are checked against the release date when there is no trustworthy clock, and the TLS seed never falls back to zeros (incident 0036).
  • Distrusted keys (ADR 0054): a list of certificate keys refused anywhere in a chain. It carries the eight eMudhra intermediates whose private keys were compromised this month (the same keys Go and rustls distrust). They chain to roots AriCodeOS does not embed, so no default chain reached them; the list also covers roots an owner adds.
  • Fair diagnostics: one process can no longer push every other event out of the kernel's event ring (incident 0040).
  • Found on the way: the screen console repainted the whole screen for every line, so slow output made some tests depend on where the kernel happened to land in memory (incident 0031); virtio-blk gave up on disk requests after 2 s, too short for a busy host disk (incident 0043, now 30 s).

Trying it

  • USB stick (aricodeos-0.15.0-usb.img.xz, attached; xz -d it first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. Check it against SHA256SUMS. Machines on 0.14.0 update from this page with update and upgrade.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.15.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

System image downloads above 6 MiB and applications above 32 KiB (AriFS file size) need design decisions; agents outside the trusted base (ADR 0041) and the driver licence (ADR 0042) await the owner; the review left the common-name fallback and wildcards over public suffixes in X.509, and its informational findings, as stated; EHCI hubs and split transactions are only verifiable on hardware.

AriCodeOS 0.14.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 24 Oct 18:00

AriCodeOS 0.14.0 (2026-10-24): the system leaves the LAN. Machines update from this project's GitHub releases over HTTPS, a development channel puts a build on real hardware in minutes, and SSH sessions see what their programs print. Each fix was reproduced before it was changed, kernel, IPC, network and update changes were audited by independent reviewers, and everything below was run on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.14.

What is new

  • Public updates (ADR 0048): the updater follows HTTPS redirects (at most five, never from https to http) and accepts the larger headers GitHub sends, so a machine updates from https://github.com/AriCodeLabs/AriCodeOS/releases/latest/download/. This release is the first to carry that source: its stick registers it, and its update files (index, index.sig, aricodeos-14.img) are attached here, signed with the release key. cargo xtask serve-update serves the same path and redirects locally, for tests that need nothing published.
  • Development channel (ADR 0045): update --channel dev / upgrade --channel dev install a signed build of develop or a branch, named by build number and commit, on a machine whose stick opted in; update rollback goes back to the other slot; a stable floor keeps released machines from going below the newest release they ran.
  • Updates that scale: installed images are verified piece by piece up to the slot size, and update apply verifies the copy in the slot before it can boot (incident 0021); one package limit for the whole system, said as such when exceeded (incident 0026).
  • SSH sessions (ADR 0047): programs started from an SSH shell (run bench, the updater) write to the session, through a console object that can only write text; sshd applies flow control.
  • Randomness: diag names what seeded the kernel generator (ADR 0039), and the loader carries a seed across boots, so a machine without rdrand is strongly seeded from its second boot (ADR 0043).
  • Responsiveness: services wait on IPC, interrupt lines and a deadline at once (ADR 0044, ABI 6); a network query went from about 10 ms to 70 µs and the USB controller lost its polling. The compositor repaints only what changed (ADR 0046).
  • Network robustness: a full TCP table recycles connections waiting out TIME-WAIT, and a peer that never closes its side is reset after 30 s (incident 0027).

Trying it

  • USB stick (aricodeos-0.14.0-usb.img.xz, attached; xz -d it first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. Check it against SHA256SUMS. Once it has network, update and upgrade fetch from this page. Machines on 0.13.0 or older cannot follow GitHub's redirects: write the 0.14.0 stick.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.14.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

System image downloads above 6 MiB (the release image is 3.1 MB) and applications above 32 KiB (AriFS file size) need design decisions; one SSH command that once came back empty was never reproduced (incident 0025); EHCI hubs and split transactions are only verifiable on hardware.

AriCodeOS 0.13.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 21 Oct 23:35

AriCodeOS 0.13.0 (2026-10-22): the last high-priority defect closed — DMA memory can no longer leak across protection domains, whether a buffer is unmapped, a driver dies, or a device completes a request late. Each fix was reproduced before it was changed, audited by independent reviewers and verified on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.13.

What is new

  • DMA buffer lifetime (incident 0004, ADR 0038): a process that maps a DMA buffer keeps it alive, so its memory is never handed to anyone else while still mapped. New mmio_unmap system call (ABI 5). What a server keeps mapped counts against its own quota; system services without a quota are bounded by an 8-entry buffer cache. Freed address ranges are reused, and a mapping that fails halfway is rolled back.
  • When a driver dies: the kernel stops the device's bus mastering before freeing the driver's memory; a restarted driver gets its device with bus mastering off and turns it on only after resetting it; devices that advertise Function Level Reset are reset (pci.flr=off disables it); a device that will not stop has its memory quarantined.
  • Buffers a device may still own (incident 0017): after a failed disk request the virtio-blk driver keeps the buffer until it has reset the device, and recovers instead of failing every later request; the USB drivers release such a buffer only when the controller confirms it let go.

Trying it

  • USB stick (aricodeos-0.13.0-usb.img.xz, attached; xz -d it first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. Check it against SHA256SUMS.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.13.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

The kernel does not yet expose whether its random generator was seeded from hardware; EHCI hubs, split transactions and 64-bit addressing are only verifiable on hardware; the driver-death path has run only in QEMU.

AriCodeOS 0.12.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 20 Oct 20:49

AriCodeOS 0.12.0 (2026-10-20): the release audit of 0.11.0 resolved through the failure protocol, and a hardened network and file service. Every fix was made on its own branch with regressions, audited twice by independent reviewers, and verified on the reference laptop.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.12.

What is new

  • USB storage: both drivers reject a command-status wrapper that did not move exactly 13 bytes, and the xHCI driver no longer reports a short read or write as a success (incidents 0007, 0010).
  • Updates: the installer never treats a failed file request as an absent file, so a transient error cannot erase the update state (0008); the updater bounds every network phase, TLS included, by its run deadline (0009, ADR 0033).
  • Network: refusals are named in the shell and recorded in diag (0012); TCP sequence numbers and ephemeral ports come from a per-boot secret, RFC 6528/6056 (0014, ADR 0034); SYN floods are capped per listener and answered statelessly, with the TCP table by state in diag (0013, ADR 0035); every client of the network service has its own session, its sockets are reclaimed when it dies and no client can touch another's (0016, ADR 0037); the receive loop is bounded per round.
  • File service: every client has its own session; a client that dies leaves no open descriptors or half-finished replace behind (0011, ADR 0036).
  • Other: the scheduler self-test is correct on SMP (0015); the HTTP client accepts 8 KiB of headers; the Docker images work on ARM hosts and with host-built artifacts.

Trying it

  • USB stick (aricodeos-0.12.0-usb.img.xz, attached; xz -d it first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. Check it against SHA256SUMS.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.12.0 boots it in QEMU (quit with Ctrl-A X).

Signed with the project's release key, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e (keys/release/).

Known open items

Incident 0004 (a DMA mapping that outlives its buffer); the kernel does not yet expose whether its random generator was seeded from hardware; EHCI hubs, split transactions and 64-bit addressing are only verifiable on hardware.

AriCodeOS 0.11.0

Choose a tag to compare

@Lynx-Boss Lynx-Boss released this 17 Oct 20:32

AriCodeOS 0.11.0 (2026-10-17): the first version signed with the project's release key, published as a Docker image, and the one that opened the project to other people.

Website: https://www.aricodeos.org/ · Master document: AriCodeOS.md, section 94.11.

What is new

  • Update sources with a signed index (ADR 0029): update and upgrade work from updater/sources, verify an Ed25519-signed index with an anti-replay serial, plan and stage installs, and run the installer with least privilege. Verified on the laptop: versions 2 to 6 installed over the network.
  • IPC peer closed (ADR 0030): a client of a dead server learns it at once instead of waiting its full timeout; init retires the endpoints of abandoned services.
  • EHCI driver (ADR 0031): USB 2.0 root ports, hubs, boot HID keyboards and mice, bulk-only storage; the served disk is identified by GPT GUID and serial. Both controllers of the laptop ready at every boot.
  • Boot self-tests only on request (ADR 0032): the test-only programs that wrote to the owner's disk and probed the test hosts now run only with selftest.
  • Incidents closed: HID endpoint recovery and Reset Device (0001 F10/F14), SMP self-test under host load (0002), laptop link after a network update reproduced on purpose (0003), duplicated sections in updater/state repaired on read with fault events (0006). Incident 0004 (a DMA mapping that outlives its buffer) stays open.
  • Kernel base signature: a frozen SHA-512 value in the ABI, reported by the shell with l1981 and checked by the ABI tests.
  • HTTP client accepts 8 KiB of response headers (github.com sends 5.3 KiB).
  • Docker: tools/docker/Dockerfile runs the whole test suite on any machine; tools/docker/try/Dockerfile boots the system in QEMU and is published as ghcr.io/aricodelabs/aricodeos.
  • The project opened: CONTRIBUTING, SECURITY, code of conduct, GitHub templates (bug, proposal, hardware test report), official repository and website in every notice.
  • Release signing key: public half in keys/release/, fingerprint 1d3e24f3c7c753a5bcb384041ace6481736decd86345eab71e2a6ff410ad446e. This release, the USB image below and the Docker image are signed with it. 0.10.0 was signed with the development key.

Trying it

  • USB stick (aricodeos-0.11.0-usb.img.xz, attached; xz -d it first): write it to a stick you can wipe and boot a UEFI x86-64 machine with Secure Boot off; see docs/hardware.md. The internal disk is never touched. Check the file against SHA256SUMS.
  • Docker: docker run --rm -it ghcr.io/aricodelabs/aricodeos:0.11.0 boots it in QEMU with the ari> shell on your terminal (quit with Ctrl-A X).
  • QEMU from source: cargo xtask run --cmdline shell after the requirements in the README.

Known open items

Incident 0004; two xtask runs in the same checkout collide on the test runner's fixed ports; an Ethernet link drop seen once after two hours on the laptop; EHCI hubs, split transactions and 64-bit addressing only verifiable on hardware.