Skip to content

docs(spec): record why delegate and request are not capabilities of their own - #325

Merged
Mearman merged 2 commits into
mainfrom
feat/delegate-capability
Oct 1, 2026
Merged

Mearman merged 2 commits into
mainfrom
feat/delegate-capability

Conversation

@Mearman

@Mearman Mearman commented Oct 1, 2026

Copy link
Copy Markdown
Member

Records the decision on #323 and #324 in the spec where the capability model is defined, and pins the property it rests on with a test in each implementation. Refs #323, refs #324.

The right to delegate a capability therefore always includes using it,
which is the property that rules out a delegate-only permission.
… of their own

A delegator can name itself as bearer, so a delegate-only permission would
not separate delegating from using. A receiver already decides on the
optional token a request carries, so a request capability would wrap
tokens without closing the stranger case.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
🔒 Security Review ✅ Completed 2026-10-01T13:47:52.828699Z 0a2fda6 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Mearman
Mearman merged commit dbeb2e9 into main Oct 1, 2026
9 checks passed
@Mearman
Mearman deleted the feat/delegate-capability branch October 1, 2026 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant