feat(spec): add optional valid-until to capability-request - #105
Merged
Conversation
Lets a requester bound how long its own ask is worth granting -- a receiver refuses a request whose deadline has already passed outright rather than presenting a stale ask to a human for approval, and a future relay/facilitator forwarding the request can drop it once expired rather than keep holding or forwarding it. Reuses the same message/token-lifetime concept the plan's own section E already names, rather than inventing a second TTL field. No new frame or verb, no conformance vector regen needed: capability-request's existing open extension tail already made this an additive field, matching every other domain's own use of the identical pattern.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Lets a requester bound how long its own ask is worth granting -- a receiver refuses a request whose deadline has already passed outright rather than presenting a stale ask to a human for approval, and a future relay/facilitator forwarding the request can drop it once expired rather than keep holding or forwarding it. Reuses the same message/token-lifetime concept the plan's own section E already names, rather than inventing a second TTL field.
No new frame or verb, no conformance vector regen needed: capability-request's existing open extension tail already made this an additive field.
Closes #82.