ABSD RC1 corresponding first-party source

Corresponding first-party source for the ABSD Developer Preview RC1 binaries, published separately as absd-source-rc1.

Source commit: 370badf53442983d8076d38273df67b056e810ac.
Source tree: 618549573803186289720b0985cebe680782b14f.
SOURCE-MANIFEST.toml SHA-256: 784c0b92a5e53c90221a2972205447f1eecd9a51441a6efc878bf1ecc13e7f22.

The source manifest records the original kernel and platform revisions, filtered trees and exact curated edits. This public tree is not an identical archive of either development repository. The manifest records qualification state at assembly time; it does not silently acquire later qualification claims.

Follow docs/RC1-SOURCE.md for the pinned public inputs, reconstruction commands, check prerequisites and limitations. Check scripts are included; see the clean-environment result below. Other-project integration sources and private historical qualification records are not included.

The RC1 binary release remains separate. Its tag and original assets are unchanged. Its automatic GitHub Source code archives still name the earlier public source preview at that binary tag. Source availability and the reconstruction instructions do not by themselves establish byte-for-byte independent reproduction, hardware support or stronger resource guarantees.

The additive notices correction is 64,836 bytes, SHA-256 4c3096ab9a4a7a41b39bdf382c57f471ad30c2fdcd5439b315b9674552667c4a. It supplements the original notices archive. The original SHA256SUMS and NOTICES.md are unchanged and do not list this addition.

The in-tree README, source instructions and manifest preserve their proposed/candidate wording from assembly time. This release record and body state the publication status. TinyCC compiler qualification is NOT_RUN / not included in this source; the kernel/core criteria are unchanged.

Clean-environment qualification used source 41f5a1baec603b68206df59cc200954c300c143d, tree 2911ef7a9af04150e6e85e7f14217f717e1910dc, in two separate project-run disposable-VM occurrences. These were not reproductions by an independent outside builder.

• Original occurrence 697f92ce-302d-4a3f-8900-1a28e31577ae: the documented kernel and platform core checks passed. The subsequent reconstruction refused because the core recovery fixture had retained a log inside the manifest-verified source. That reconstruction remains failed; it was not rescored.
• Supplemental occurrence 0a779a31-aa44-4fed-95ec-924261773376: a fresh untouched checkout of the same source fetched and rebuilt successfully, including operator validation and the 16-case, 61-check enrollment matrix. The core checks were not repeated in that occurrence.
• The published source includes the separately host-tested and independently reviewed correction that binds the recovery fixture's work directory outside the source tree. It also includes the reproduction documentation and manifest assembler-identity update. Its kernel and platform component trees are identical to the tested source. These later source revisions were not re-executed as guest campaigns; the distinct check, rebuild, correction and correspondence evidence is disclosed rather than labeled as a new-source guest pass.

All 40 other named executables (three services, 25 native commands and 12 C ports) were byte-identical in the fresh-VM reconstruction. All 12 raw C catalog hashes and all 12 installed/stripped catalog hashes matched.

The eight Rust ports (basename, seq, cut, fold, nl, uniq, base64, rg) differed at the fresh checkout root because the frozen port build embeds absolute platform/staged-library source paths. The unchanged public build at the recorded original paths, controlled occurrence f1ec9925-980c-4e7d-8c7f-5159c4256dcc, reproduced all eight complete published ELF files byte for byte. Separate reviewers verified the exact source and all eight output comparisons. This establishes that recorded-input/path correspondence; it does not establish general root independence or compiler correctness. The earlier namespace archive-ownership refusal is preserved as a separate precompiler failure. The public source instructions give the literal nonroot namespace replay and all 48 expected named-executable hashes. The printed namespace replay block was reviewed and syntax-checked but was not itself executed verbatim: it differs from the executed f1ec9925 launcher by using one namespace session for preparation/build and placing ABSD_USERLAND_BUILD outside the bind parent; f1ec9925 reproduced the eight ports. Stable platform/sysroot remapping and two fresh builds at different roots remain subsequent-release work.

All three original supplemental whole-media comparisons remain DIFFERENT, with their finite causes examined separately:

Media	Published SHA-256	Supplemental SHA-256
operator ISO	d1181d465f9dcbc1322087e5c3e2235ac48007c081d7f150494436ae7d30ecef	7a2f456dc8754d497e68783eeb90f2bb933b7f9fd6db66d06906fd31403cfef1
raw blank disk	c9913d3bb889ddaffb223e77ac3d8c8c8bb222144ee349068cba79044bc25a78	321c30e51ea5743f20f38246baab9e93f878c8aa592722a95c5415059feadde9
enrollment ISO	7251c6262cf3ad311c12bff09a0cfe94f59d8986c38041d50e59b43a63340b7f	004925542d620f4893943add97bbfaf1bdb39202ec9197e3c56fe13a474d5a1c

The operator ISO's only changed file was its kernel. Kernel program headers and allocated section content matched except the GNU build-ID note; metadata differences comprise LLVM private-symbol suffixes and resulting string/section-table offsets and build ID. The enrollment kernel also records its auxiliary build directory in DWARF. The source instructions include exact code/data section hashes. These comparisons do not prove arbitrary differing kernels equivalent.

The blank disk retained the layout, every byte before the filesystem region, and all 100 record names/nonallocation metadata. Its only changed file contents were the eight Rust ports; sizes and subsequent block allocations account for the filesystem differences. The other 79 file contents matched. Empty active authorized keys and absence of a host seed were checked separately.

The enrollment ISO additionally uses plain grub-mkrescue, with ISO volume/file dates and hybrid GPT identifiers, clock-derived disk/search UUID, FAT volume serial and directory dates, uninitialized free-space bytes, host GRUB translations/backup files and layout-derived boot locations/checksums. All 78 changed EFI FAT bytes were assigned to serial (4), dates (49), UUID (6) and unallocated space (19). The EFI program matched after its one UUID substitution; the BIOS image and boot catalog matched after their decoded location/checksum substitutions. Eight absent English translation/backup files account for 136 data sectors and two directory sectors. These finite read-only controls explain this pair; they neither alter the original unequal files nor waive new differences.

TinyCC compiler qualification and the 12 extended other-project integration steps are NOT_RUN / excluded. The optional UEFI case, the opt-in heap-scenario driver and 26 historical/optional media host cases were not exercised by the original core run. Physical hardware, external independent reproduction, whole-media byte identity and stronger resource guarantees are unclaimed. The existing kernel/core criteria and all original failed or unequal verdicts remain unchanged. Follow the pinned source instructions for inputs, replay and comparison boundaries; source availability and a completed build are distinct from these qualification claims.

ABSD Developer Preview RC1

ABSD Developer Preview RC1: a downloadable, unsigned QEMU preview.

Start with QUICKSTART.md (attached). It covers downloading, verifying checksums, creating and enrolling a machine with your own SSH key, booting under QEMU, and logging in.

What this is: a single-operator ABSD system that runs in QEMU on an x86-64 host, with one virtual CPU, at least 256 MiB of RAM, an IDE disk and e1000 networking with static IPv4. You reach it over SSH.

Not in this preview: physical hardware, ARM64, multiple CPUs, IPv6, UDP, DNS, DHCP or outbound network connections from the guest, or in-place upgrade or rollback. To update, replace the machine with a newer preview, as QUICKSTART describes. QUICKSTART and MANIFEST.toml list the limitations.

Integrity: these files are unsigned. SHA256SUMS detects corruption; it does not prove who produced the files.

Source:

• The attached absd-rc1-boot-corresponding-source.tar holds the corresponding source for the GRUB and GNU Unifont boot components. absd-rc1-third-party-notices.tar.gz holds the third-party notices.
• First-party ABSD source and reconstruction instructions are provided separately at absd-source-rc1, commit 370badf53442983d8076d38273df67b056e810ac. Its SOURCE-MANIFEST.toml and docs/RC1-SOURCE.md describe the exact component revisions, curated edits and reconstruction limits. This separate source tag does not move the binary release tag or establish byte-for-byte independent reproduction.
• The "Source code" archives GitHub attaches automatically to this release are the earlier public source preview (absd-preview-20261010) at the tagged commit. They are not RC1's source.

Additive notices correction: absd-rc1-third-party-notices-correction-1.tar.gz (64,836 bytes; SHA-256 4c3096ab9a4a7a41b39bdf382c57f471ad30c2fdcd5439b315b9674552667c4a). This supplements the original notices archive. The existing SHA256SUMS and NOTICES.md are unchanged and do not list this addition; verify it against the digest above.

Release id inside the files: absd-rc1-c12c-20261018t161241z.fvcgzh.