How to represent both agent OBO human and agent OBO itself in COAZ mapping
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 160
- Forks
- 41
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 23
Description
4.3 says:
For autonomous agent use cases, the context MUST include the identity of the agent. At least one field of either the subject or the context MUST be derived from the token input variable via a CEL expression.
However, the same MCP tool can be invoked by both an autonomous agent and an agent acting on behalf of a user. The COAZ mapping is the same for all callers, though. Suggest removing the "For autonomous agent use cases" part and strengthening to "The context MUST include the identity of the agent".
Splitting from #483
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with section 4.3 and compare the proposed wording change with the context from issue #483. Determine whether requiring the agent identity in the context consistently covers both autonomous agents and agents acting for users, then confirm that the specification text clearly reflects the agreed behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100