admission: bind Flow 1.35.1 to measured reference evidence - #45
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
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 matching release admission for published Flow 1.35.1 and append its release and synthetic workflow references to the canonical ledgers.
The admission binds source
44e99a48ebf048c18892aa17cef6ae594db0d0c2, wheelsha256:cfbc89acc6a2e3bcb5502a4d1fb29e985a03149a7f14c32c259254676bb3f11d, and sdistsha256:c5c6c437472b23999223b0d2473dbf21de2ca05274c270ae3854adeda6b07dca. The existing issuer checks the complete measured evidence chain and current authority before consumption. Release sequence 2 preserves the prior admission identity; every new nested evidence reference names its actual containing commit.The reference campaign has 18 groups across six conditions, one exact synthetic bundle, and 831 retained artifacts. Primary outcomes are 12
VERIFIED, threeHALTED_BEFORE_EFFECT, and threeRECONCILIATION_REQUIRED. Native model-call counts are zero; external network-call counts remain unknown. Customer workflow admission and product-wide Production require their separate gates.The existing
already-published-pypipath binds the published bytes and actual tag controls. GitHub release 385710075 retainsimmutable:false. No historical signed object or prior ledger row changes.The repository evidence guide now separates the published-wheel qualification from the historical September 8 study. Snapshot tests retain the original seven release and workflow objects, derive the latest registered Flow identity, and use a deterministic test-only clock. Runtime validators and refusal/expiry tests are unchanged.
The release admission ID is
sha256:279d6e0a9728be2d6466106b07a23a45cb6dd8acf0c4f4bcc2047d09468cabb1. Its objectsha256:0edd19d51d449e3eaba21463117fb19148553a817e03c8c5b804953a26bcbb51and bundlesha256:114c70ce18f6633b0a2b9c4b7b274e8f7484e711a102f182cf3d1f417ec74910were committed and pushed at2ed288e8bd47dd1809f883cc75e3f5ce34348692before the ledger reference was constructed. The merge must preserve that commit.The workflow ledger preserves its exact original main reference at
f0fb9cc812c0d1653b1ec2998749b078f244308e. The consumer now accepts the signed1.35.1-reference.1bundle version under the existing canonical syntax and length rules. It retains the evidence-class, digest, signature, authority, expiry and privacy checks; only the obsolete0.0.0-syntheticequality was removed.Independent reviews cover each plan, signed pair, one-use result, registry delta, final ledger references, documentation and consumer correction. All 337 canonical unit tests pass, including actual signed old/new workflow rows and malformed-version, identity-digest and byte-binding refusals. Both ledger history checks pass. Current canonical verification against the merged ledger and exact downloaded artifacts remains the consumer's required boundary.