evidence: register exact Flow 1.35.1 synthetic workflow admission - #42
Merged
Merged
Conversation
Signed-off-by: abrichr <richard.abrich@mldsai.com>
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.
Register the workflow admission for the exact synthetic reference bundle qualified on the published Flow 1.35.1 wheel.
The admission binds encrypted bundle
sha256:bee27e24a177599d7f83fe1cf332e850d64f26bf9c1c68ccf21ff10202128bc4and runtime wheelsha256:cfbc89acc6a2e3bcb5502a4d1fb29e985a03149a7f14c32c259254676bb3f11d. It preserves the 18-group decision receipt at its actual containing main commit,4a4ae1aceacee1e069b029f498bd996e07821840.The scope is one local synthetic workflow, six conditions with three groups each, and simulated operator/reviewer principals. It doesn't establish customer workflow qualification or hosted availability. The product release admission remains a separate required step.
This registry revision appends the workflow object and signature bundle through the existing authority. All prior entries and the current signer, authority, and revocation records stay intact. The required nullable expiry preserves current revocation checks.
Validation: Independent review verified the exact unsigned plan, signed output, one-use result, and three-file registration at
2a947361a16fb29e0e0da09785cdf186dfe31ae7. The unchanged append-only validator passes. Registry revision 5 contains 78 entries and preserves the first 76. The object issha256:947224523757df41127be021fc66adee5746f07ff1a0e913319c5461e430e34d; its signature bundle issha256:93334be2510f0036a77341bb5eed555dbff790e7b4db1f47a5ebade371ebf1aa.