Vouch request: chuks #2714
chuks
started this conversation in
Vouch Request
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
What do you want to work on?
I want to contribute an interoperability example that shows a Ratify Protocol delegated authority being used with OpenShell and MCP. In the example, a human (or agent/sub-agent) principal signs a Ratify authorization which specifies exactly what an agent can do, on what system (resource/tenant), and time limits for the action(s). The agent carries the proof as a cryptographic bundle in MCP
_metathrough an OpenShell-backed connection. OpenShell enforces the allowed destination and MCP tool, while an independent receiver on the system verifies the proof before the action(s) are performed on the system.I have already built and tested the external reference using OpenShell v0.0.102, MCP, and the published Ratify Protocol (alpha.16) -> identities-ai/ratify-protocol#61
I would like to reduce this to a small, useful contribution with all the documentation, successful cases, and denial cases, and seeking guidance from the maintainers on whether this contribution falls under an OpenShell example, community integration, or another form of contribution.
Why this change?
Not a change to the underlying OpenShell.
OpenShell and Ratify enforce complimentary security boundaries. OpenShell controls what an agent can access at runtime, and Ratify allows the receiving system to verify that the principal authorized/delegated the specific (business) action that the agent is requesting. A combination would give OpenShell users a runnable pattern for combining runtime policy with portable, receiver-verified delegated authority, which further strengthens the security (and auditability) posture.
Checklist
All reactions