Releases: RecursiveIntell/Recursive-Linux
Release list
v0.1.0-experimental — hardware-target installer candidate
Recursive Linux — experimental hardware-target installer candidate (2026-09-06)
This pre-release publishes a local Fedora 44 installer candidate using the interactive hardware-target profile. The ISO is attached as a release asset rather than committed to Git history.
Source snapshot: b7540dce3283b723f92103a7c2aeede37b5b550d. The attached ISO predates this commit and is bound to the recorded embedded Kickstart and payload hashes; no clean byte-identical rebuild from this source snapshot has been demonstrated.
Asset verification
File: hermes-workbench-recovery-installer-20260906-v2.iso
Bytes: 1,217,396,736
SHA-256: 6f2e1406db4a4d5970f489589d5f1d51549e25e00fb1a88d5d1bd7b4430221fc
sha256sum hermes-workbench-recovery-installer-20260906-v2.isoEvidence supported
- Static inspection found BIOS and UEFI El Torito entries, a boot-configuration reference to the embedded hardware-target Kickstart, and an embedded payload matching the locally recorded payload hash;
checkisomd5reported PASS. These checks do not prove that either firmware path installs or first-boots successfully. - A separate destructive VM-only fixture installed and first-booted under the recorded BIOS/QEMU validation path. That VM result does not validate the attached hardware-target ISO’s installation path.
- The hardware-target Kickstart does not preselect disk clearing, automatic partitioning, a target disk, credentials, or an encryption secret. Proceeding through the interactive installer can nevertheless modify storage and boot state.
- No physical USB device, physical disk, partition table, bootloader state, or UEFI variable was written as part of this work.
Boundaries and known gaps
The attached ISO was not cleanly rebuilt end-to-end from official Fedora input after the external source medium disconnected. It is not hardware-qualified, UEFI-installed-system verified, physical-media verified, reproducibly built, or production-ready.
Do not format, repartition, write a USB device, or migrate a disk based solely on this release. Review the exact-device and recovery gates in docs/PREFORMAT-GO-NO-GO.md.
See the sanitized public evidence receipt for the exact validation scope and exclusions.