alpha26: correct collector semantics and add time sync#52
Merged
Deadbytes101 merged 9 commits intoJul 15, 2026
Conversation
Deadbytes101
marked this pull request as draft
July 15, 2026 19:37
Deadbytes101
marked this pull request as ready for review
July 15, 2026 19:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ALPHA.26 STATUS SEMANTICS
Corrects three issues found during physical BIOS validation of the exact Alpha.26 source candidate.
SOURCE BOUNDARY
WHAT CHANGED
overlayroot as operational only when every lower layer is under/run/live/rootfsthermalandwatchdogsubstring counting with bounded kernel-fault signaturessystemd-timesyncdPRESERVED CONTRACTS
timestamp.nonce.bodyHMAC-SHA256 wire contractVERIFICATION
Local Python verification:
The tests cover expected live-overlay truth, unexpected writable roots, normal kernel boot messages, real bounded fault messages, time synchronization, privacy, HMAC, source identity and failure exit contracts.
RELEASE BOUNDARY
This changes the appliance image. The existing successful image and its hash remain historical evidence and must not be overwritten. A new Debian 12 Bookworm build, new artifact identity, QEMU BIOS gate, physical BIOS gate, physical UEFI gate and unattended soak are required before any Alpha.26 tag or stable claim.