Evidence

Each milestone and release gets a record like the ones below, newest first: what is claimed, what was built, where it ran, what was checked, and where the claim stops. Older records stay as they were written.

"Accepted" and "reviewed" on this page mean re-examined by AI model sessions separate from the ones that did the work, not by an independent human (how it is developed). A release is a named internal build with recorded digests; it is not distributed, and nothing here can be downloaded.

Release absd-20261003.1

RELEASE-QUALIFIED Accepted 2026-10-04.

Claim
The single-operator system of the milestone below, built as an exact kernel and platform pair, qualified under QEMU with TCG or KVM, and installable, updatable from the previous release, and able to roll back to it.
Build identity
Kernelfcfbab9867da40eebb0c4dd266b82484ae7e76c5
Platformc54dc90007fe509c0e118b7ec9c6cbd6ea9aa356
Release manifestSHA-256 d73f559e5e6f7dc6e0d601f7bfc518890e3bdf8b5099cc9cbb5d35eb0a092a21
Release ISOSHA-256 3fa0402692ae4fb5c83447599f4e18584cc5caf48dd68930a4ad24e804dca18d
VersionsKernel ABI 1, application ABI 1, file server protocol 2, filesystem format 2
Previous releaseabsd-20261002.3, kept unchanged as the rollback target
Environment
QEMU on one Linux development host, x86-64, TCG or KVM, one CPU; an IDE disk or one NVMe namespace; e1000 network model.
Tests
AreaResult
Whole platform check193 host executions, 26 runtime targets
Update and rollbackInstalled system updated from absd-20261002.3, served and accepted, then rolled back, with both generations intact and site state preserved; halted-image backup and restore
Program images87 adversarial images: 60 refused, 27 boundary cases accepted; resources unchanged after each
Kernel output paths28 checks for leaked addresses or stale memory, none found
Sessions300 consecutive SSH sessions returning to the same memory baseline
ReconstructionRebuilt from fresh clones at the pinned commits and compared

Acceptance was composed from separately run and separately reviewed stages, not from one uninterrupted run. Earlier runs failed and stay on record: one on SSH server memory growth across sessions, repaired in the platform; and the first end-to-end run, which stopped on a resource count after the first program-image refusals. That count difference is not yet explained; the image cases passed when rerun as their own stage, after a test-only start-up fence was added; that is not a general quiescence result.

Limitations
  • Emulation only. Physical hardware qualification: not yet established.
  • One CPU. Several-CPU work is not part of this release.
  • Updates are staged from a host onto a halted image and take effect at reboot; no updater runs on the system.
  • Not yet: weeks of operation on a named machine without a build host.
Date
2026-10-04

General usability under QEMU

MILESTONE-QUALIFIED Recorded 2026-09-27.

Claim
ABSD can be used as a single-operator system under QEMU: an operator builds an image from source, boots it, logs in over stock OpenSSH, keeps files across sessions and reboots, runs a shell with pipes and redirection, the installed commands and manual, and real Rust workloads, and shuts the machine down in order.
Build identity
Tagmilestone/general-usability-qemu-20260927
Kernel19831726395c9f64fabcdd58c84bcbdd30f701b8
Platformff025b1c333ee611ae47d196c23d2b2ccd9cd6fc
Reproducibility55 programs byte-identical across two clean builds
Rustrustc 1.95.0 with a pinned, locally held standard-library source snapshot (experimental target x86_64-unknown-absd)
ManualRendered by GNU groff 1.23.0; the two builds' rendered trees identical
Physical probe ISOSHA-256 073467abffe2f01a06b817be460c1e729441c70fe52c110fa1f3326daac9b30f: the read-only image recorded with the milestone. Not booted on hardware.
Operator ISO used on the home pageSHA-256 0839ee6e50075c96661732a97c4d2bbc3eef662caadb1380239ea16b577eeaf8, built from the tag for the captured session. ISO images are not byte-reproducible; this names one file, not a release.
Environment
QEMU 8.2.2 with TCG on one Linux development host; x86-64, one CPU, -cpu max,vendor=GenuineIntel,+rdrand; default PC machine with SeaBIOS; IDE disk image; e1000 network model on user networking; OpenSSH 9.6 client on the host. Kernel boot gates also ran on a q35/OVMF machine with NVMe and on the read-only physical image under SeaBIOS and OVMF (details).
Tests

The platform's full check script, end to end, exit status 0, no QEMU process left behind. Counts are the script's own.

AreaResult
SSH, against ABSD129 checks
SSH, against a Linux reference target67 checks
File server39 checks
Served boot and shutdown65 checks
Commands and manual pages160 checks
Operator image90 checks
Performance bounds23 checks
Durable state, crash scenarios26 scenarios, 377 boots
Filesystem and SQLite store349 boots, including 66 modeled power cuts and 10 corruption cases refused
NetworkingARP, IPv4, ICMP echo, TCP streams, 200 reconnects
Compatibility probe19 programs: 10 build, 9 run; 19 of 25 cases equal to Linux
Kernel gatesUnit tests and lint, deterministic boot suites, broker, image spawn, network, durable reader, block probe (ATA and NVMe), NVMe, external workload, physical-image safety gate, laptop-shaped machine, shell
Workloads
Stock OpenSSH sessions driving the shell and commands; file transfer of 0 B to 1 MiB; an SQLite store under crash and modeled power-loss injection; and real programs from another project (a journal, a support resolver, a diagnostics tool, a store writer and resolver), each compared with its Linux build.
Limitations
  • Emulation only. Physical hardware qualification: not yet established.
  • Power loss is modeled below the filesystem; no real power was cut and no drive's flush behaviour was tested.
  • One CPU; one operator identity (several sessions are not several users); 16 processes system-wide.
  • Uploads take about 45 to 60 s per MiB under TCG.
  • An interrupted command's children keep running; a later shutdown then ends in an unreaped stop (QEMU status 71) after the file server has committed.
  • No update or rollback of an installed image; no fork, signals, threads, kernel sockets, IPv6, DNS, DHCP, outbound networking, dynamic linking, C programs, or Linux binaries.
Date
2026-09-27