fix: consume until-revoked Flow release receipts - #473
Merged
Merged
Conversation
Signed-off-by: Richard Abrich <richard.abrich@mldsai.com>
Signed-off-by: Richard Abrich <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.
Flow now accepts the canonical verifier's required
expires_at: nullvalue. The producer preserves the admission expiry, but Flow rejected null withexpires_at/string_type, so receipts for admissions valid until revocation could not decode.The field remains required. The consumer can't replace a missing expiry with null. Supplied timestamps still expire at the exact boundary; malformed timestamps, future verification times, altered object bytes, invalid self-binding digests, and local release identity drift still fail validation.
Release integration depends on the companion Cloud guard for current authority and revocation state. That guard checks the current canonical trust objects during retention, dispatch, poll, and initial/resume/continue permit issuance. Keep publication gated until the complete Cloud boundary review passes. Receipt decoding preserves the canonical expiry; authorization still requires the surrounding current-state checks.
Validation: 157 focused receipt and hosted tests pass, along with Ruff 0.16.5, type checks for 290 source files, release consistency, and the claims structure gate. A receipt generated by canonical
.githubsource80761c2ce46eb9365ea3b3a6982f37cab00dea7dfrom the registered public Flow objects also passes exact-byte decoding and local identity comparison. That deterministic fixture is a compatibility test, with no live signing or authorization claim.Opened by an agent session, not the founder.