evidence: register measured Flow 1.35.1 qualification receipt - #41
Merged
Conversation
Signed-off-by: abrichr <richard.abrich@mldsai.com>
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 measured qualification decision for the published Flow 1.35.1 release from
44e99a48ebf048c18892aa17cef6ae594db0d0c2.The decision binds one sealed synthetic reference workflow and 18 fresh trial groups, with three groups in each required class. Its primary outcomes are 12
VERIFIED, threeHALTED_BEFORE_EFFECT, and threeRECONCILIATION_REQUIRED. The retained database and input records supply the effect checks. The silent-incorrect-success, over-halt, unsafe-effect, model-call, retry, replay-dispatch, and unplanned-intervention counters are zero. Native external network-call counts remainunknown.The measured manifest is
sha256:8167536c8cc0c6dcdae8a54a2843b3a71920baa7eaf401bbc9149ecc1e29b996. Its 831 artifacts include the published-wheel installation proof, public release records, and all 27 native phase reports. The earlier studies remain unchanged. This scope doesn't establish a customer workflow or product-wide Production.The registry appends the decision object and its signature bundle through the existing software Ed25519 authority. It preserves the signer registry and current authority/revocation objects. Workflow issuance must reference this pair at the real main commit after merge.
The public object is
sha256:01f11ce3f7343e407f67ab6e5e6e2490af852602f4cae473e0de0d91cd6f6984; its bundle issha256:219de812a126e2e6ecc2ffc60ca21788ba2c820851d5040c6aa0e02247db6d30. Registry revision 4 keeps the first 74 entries and appends this pair.Validation: The unsigned plan received independent review. Independent review also verified both signatures, the exact plan fields, the permanent one-use record, and the three-file registration at
61108829ae4b2c4c8f05c2d23d3d0630e8a1d6cf. The local registry validator passes against the previous main registry.The repository snapshot test retains all 74 historical entries under their original revision-3 registry head. It also validates the current complete registry, so later append-only receipts can pass without changing the production validator. Independent review and all 23 focused registry tests pass.