Skip to content

docs: add Capability Manifest Protocol integration guide - #643

Open
vystartasv wants to merge 2 commits into
aipotheosis-labs:mainfrom
vystartasv:docs/capability-manifest
Open

docs: add Capability Manifest Protocol integration guide#643
vystartasv wants to merge 2 commits into
aipotheosis-labs:mainfrom
vystartasv:docs/capability-manifest

Conversation

@vystartasv

@vystartasv vystartasv commented May 6, 2026

Copy link
Copy Markdown

What This Adds

A documentation page (CAPABILITY_MANIFEST.md) showing how the Capability Manifest Protocol standardizes agent capability declaration, complementing ACI's 600+ tool discovery with verifiable, signed capability statements.

Why This Matters for ACI

ACI solves tool discovery — semantic search finds the right tool. Capability Manifest solves tool trust — proving an agent can actually use it responsibly:

Concern ACI Today ACI + Capability Manifest
Tool discovery Semantic search ✅ Semantic search ✅
Tool trust Implicit (has API key) Cryptographic (signed manifest)
Rate limits Per-app config Per-agent constraints in manifest
Delegation trust Assumed Verified Ed25519 signature

Manifest Example

{
  "agent_id": "agent-abc123",
  "capabilities": [{
    "tool": "gmail_send_email",
    "provider": "aci",
    "constraints": {"max_recipients": 50, "rate_limit": "100/hour"}
  }],
  "signature": "ed25519:..."
}

What's in the Doc

  • Manifest structure with JSON example
  • ACI integration flow (discovery → verification → delegation)
  • Links to related specs (Identity, Trust Score, Onboarding)
  • Getting started with the open-source SDK

References


Summary by cubic

Adds CAPABILITY_MANIFEST.md, a guide to the Capability Manifest Protocol showing how agents declare and sign capabilities and how ACI verifies them, with a JSON example and the discovery → verification → delegation flow. Updates include canonical spec links, the correct workswithagents pip name, a link to 6-language reference implementations, and a minor code block lint fix.

Written for commit 4ba4b98. Summary will update on new commits.

Summary by CodeRabbit

  • Documentation
    • Added comprehensive Capability Manifest Protocol docs: purpose, structure, sample JSON manifests, verification workflow, governance guidance, and getting-started resources to help declare and verify tool capabilities.

Review Change Stack

Documents how the Capability Manifest Protocol standardizes
agent capability declaration — complementing ACI's 600+ tool
discovery with verifiable, signed capability statements.

Shows manifest structure, ACI integration flow, and how
Ed25519 identity enables trust-before-delegation.

Related: aipotheosis-labs#642
@vercel

vercel Bot commented May 6, 2026

Copy link
Copy Markdown

@vystartasv is attempting to deploy a commit to the Proxy Team on Vercel.

A member of the Team first needs to authorize it.

@vystartasv
vystartasv had a problem deploying to CICD_FOR_FORKED_REPO May 6, 2026 19:42 — with GitHub Actions Failure
@vystartasv
vystartasv had a problem deploying to CICD_FOR_FORKED_REPO May 6, 2026 19:42 — with GitHub Actions Failure

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

@coderabbitai

coderabbitai Bot commented May 6, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 13b8e13c-f875-424d-a238-54c8b0815885

📥 Commits

Reviewing files that changed from the base of the PR and between 135c2f6 and 4ba4b98.

📒 Files selected for processing (1)
  • CAPABILITY_MANIFEST.md
✅ Files skipped from review due to trivial changes (1)
  • CAPABILITY_MANIFEST.md

📝 Walkthrough

Walkthrough

A new documentation file CAPABILITY_MANIFEST.md is introduced that defines the Capability Manifest Protocol, outlining its purpose, JSON structure with agent identity and capability declarations, verification workflow with ACI, getting started guidance, and references to related protocols.

Changes

Capability Manifest Protocol Documentation

Layer / File(s) Summary
Protocol Introduction
CAPABILITY_MANIFEST.md (lines 1–12)
Introduces the Capability Manifest Protocol and its role in declaring tool capabilities for agent delegation and verification.
Schema Definition
CAPABILITY_MANIFEST.md (lines 14–35)
Defines manifest structure with JSON example showing agent_id, public_key, capabilities array (tool, provider, verified_at, constraints), and signature field.
Integration Workflow
CAPABILITY_MANIFEST.md (lines 37–43)
Describes how manifests integrate with ACI for delegation, verification, and capability delegation steps.
Resources & References
CAPABILITY_MANIFEST.md (lines 44–56)
Provides getting started guidance and lists related protocols (Identity Protocol, Trust Score, Onboarding Protocol).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related issues

Poem

I hop with a manifest held tight,
Keys and capabilities gleam in light,
Signatures stamp the trust in sight,
ACI checks, then sets things right,
Hooray—delegation takes flight! 🐇✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add Capability Manifest Protocol integration guide' directly and specifically describes the main change: introducing a new documentation file that serves as an integration guide for the Capability Manifest Protocol.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CAPABILITY_MANIFEST.md`:
- Around line 9-12: Add a language identifier to the fenced code block
containing the two lines starting with "ACI tool discovery" and "Capability
Manifest" so markdownlint MD040 is satisfied; update the triple-backtick fence
that encloses the strings "ACI tool discovery    →  \"Here's the Gmail send
function\"" and "Capability Manifest   →  \"This agent is verified to use Gmail
send responsibly\"" to include the language token (e.g., text) immediately after
the opening ``` backticks.
- Around line 48-50: The three external references in CAPABILITY_MANIFEST.md are
incorrect or inaccessible: verify and replace the Spec URL with its final,
directly accessible URL (follow the 301 and use the canonical destination);
confirm the correct PyPI package name for the Python SDK (or remove the `pip
install works-with-agents` line if no package exists) and update it to the
verified install command; and validate the "Reference implementations: 6
languages" claim by checking the repository or documentation and either correct
the number of languages listed or remove the claim and link to a verified list
of implementations. Ensure each updated item in the file (the Spec URL line, the
Python SDK pip line, and the reference implementations line) points to
accessible resources and add brief evidence (e.g., package name or repo link) in
the manifest text.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5a5ac9e7-4875-4463-8ada-8eade268a1cb

📥 Commits

Reviewing files that changed from the base of the PR and between 0006bee and 135c2f6.

📒 Files selected for processing (1)
  • CAPABILITY_MANIFEST.md

Comment thread CAPABILITY_MANIFEST.md Outdated
Comment thread CAPABILITY_MANIFEST.md Outdated
- Add text language identifier to fenced code block (markdownlint MD040)
- Fix spec URLs to canonical workswithagents.dev addresses
- Fix pip install to workswithagents (actual PyPI package name)
- Add verified 6-language reference implementations link
@vystartasv
vystartasv had a problem deploying to CICD_FOR_FORKED_REPO May 12, 2026 21:24 — with GitHub Actions Failure
@vystartasv
vystartasv had a problem deploying to CICD_FOR_FORKED_REPO May 12, 2026 21:24 — with GitHub Actions Failure
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