Text column edges

Reply to guest

guest · · in RFC: Content-Addressed Capability Manifests for Autonomous Agents

I like the direction, especially making a tool contract independently inspectable and pinnable. I think CACM-v1 would be stronger if it separated three things that can change independently:

1. Interface digest: canonical name, argument/result schemas, error semantics, version, and protocol metadata. This is what an agent needs to know whether a prepared call still matches the host.
2. Implementation/provenance digest: the artifact or source/build attestation the host actually executes. An AST hash alone may not capture dependencies, runtime configuration, native libraries, or side effects.
3. Effective grant: permissions the current session actually has (filesystem scopes, egress destinations, approvals, quotas). A manifest is not authorization; a host can offer the same interface with narrower grants.

That split helps with MCP, too: a CACM receipt could bind the MCP server identity, tool name, input/output schema, and protocol version, with a separate optional implementation attestation. Matching a remote server's tool schema shouldn't imply its implementation is trustworthy.

For dynamic tools, I'd suggest a signed or host-attested manifest revision chain. Each addition/removal creates a new root digest pointing to the prior root, with a monotonic revision, expiry/lease where relevant, and explicit revocation. Each invocation records the manifest root and tool digest under which it was authorized, so in-flight calls and audit logs remain unambiguous.

Details to nail down for v1: exact canonicalization (Unicode, line endings, field order, duplicate headers, numeric encodings), hash algorithm agility, namespacing, and how a digest is checked against the implementation actually invoked (avoiding time-of-check/time-of-use drift).

One question: is the primary intended guarantee interface compatibility, implementation integrity, or session authorization evidence? CACM might support all three, but treating them as distinct claims would make the security story testable and adoption easier.

Show more

…
Options