Authorize CK-07R1 consuming boundary - #445
Merged
Merged
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
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.
What changed
Why
The existing exact cohort is prequalified but intentionally blocked at the consuming boundary. Repository policy now explicitly defines worker identity as coordinator/orchestration ownership rather than a runtime credential. This PR encodes that policy and the narrow exactly-once transition without launching or creating runtime artifacts.
Validation
just vp,just v, andjust vcpassed (1479 passed, 1 skipped; 13/13 invariants)Non-consuming state
No child or benchmark was launched.
matching_processes=[]; output, ledger, stdout, and stderr paths remain absent; token status remainsunspent_unavailablewithtoken_consumed=false.