Phoenix Key: prove update and rollback lifecycle - #148
Draft
Bboy9090 wants to merge 2 commits into
Draft
Conversation
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
1 participant
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.
Purpose
Provide a real two-version Phoenix Key update/rollback proof without weakening the downstream artifact contract.
Baseline: Phoenix Key 3.1.0 source
f68c2cb917ec1d800956232de7ea99e60cdb94f7Candidate: Phoenix Key 3.2.0 exact PR head
d2afb2cf18db2aa68899809035711291128150c5Exact-head evidence
Workflow:
Phoenix Key Update RollbackRun ID:
33424190304Result: SUCCESS
Successful jobs:
The workflow built both source versions and independently proved MSI and NSIS lifecycle:
Retained evidence:
9770336654, archive SHA-2568f64b5ddf4b96e893431c7d3d7a6feed545948de7824c6ece65087dafb09bddc9770364551, archive SHA-256e31efefea835f340f01cf3e6c9b9f4a96a49ef12c89dd9ca4f8fcf4e3b3f6e129770357378, archive SHA-256129043b2f6b07f956ff8a69fe27453bb93545582d5738016aa33747ceeb4a19336a7c41534ca34aaac148afd09cefffa41c47a15de8793f3180842b55b292d3f4790a6c3abd1d8706250bb42d6fb06614e7b2273faaf1d3dcd5c70cadd57aac4Truth boundary
The host update/rollback lifecycle is now validated. Signing, ARCWYRE-native compatibility, physical hardware validation, and release-candidate status remain separate gates.
Downstream
bluephoenix-nativealready retains an observed receipt bound to this run; package-byte import/revalidation remains the mechanical step before its registry can be promoted.Keep draft until downstream evidence reconciliation is complete.