52 lines
2.2 KiB
Markdown
52 lines
2.2 KiB
Markdown
|
# CAP homepage (cap-protocol.org)
|
||
|
|
|
||
|
|
## Metadata
|
||
|
|
|
||
|
|
| Field | Value |
|
||
|
|
|---|---|
|
||
|
|
| Institute | Molodetz Institute — Research & Retrieval Division |
|
||
|
|
| Subject | cap-protocol |
|
||
|
|
| Document type | Source Dossier |
|
||
|
|
| Tier | 1 |
|
||
|
|
| Source title | CAP CLI Agent Protocol (homepage) |
|
||
|
|
| Source URL | https://cap-protocol.org/ |
|
||
|
|
| Source type | project page |
|
||
|
|
| Source date (published) | Unknown, not stated (living page; draft 2026-05-18 banner) |
|
||
|
|
| Date researched | 2026-10-18 |
|
||
|
|
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
|
||
|
|
| Research method | direct page fetch, read in full via saved output |
|
||
|
|
| Confidence | High |
|
||
|
|
| Status | Active |
|
||
|
|
|
||
|
|
## Summary
|
||
|
|
|
||
|
|
Positioning page: the protocol-stack table (MCP/ACP/A2A/CAP layers), the PTY-substrate plus fast-paths plus orchestration pitch, a manifest example, the two normative doc links, the reserved-profile table, status timeline, and FAQ (ACP/A2A differences, binding optionality, cooperative interruption pointer to §10.6).
|
||
|
|
|
||
|
|
## Key findings
|
||
|
|
|
||
|
|
- Layer claim: CAP is orch-to-CLI-agent at fleet scale; one agent may speak all four protocols at once.
|
||
|
|
- Only PTY is required; "most agents implement at most one fast-path" (FAQ) sets the interop expectation tai should design to.
|
||
|
|
- Reserved profiles: devops, data, security, research, content, sysadmin, network. Only coding is defined.
|
||
|
|
- Governance: rsclaw maintainers transitional; LF proposal once 3+ independent implementations exist. Tai would count toward that bar.
|
||
|
|
- Spec text CC BY 4.0, reference code MIT.
|
||
|
|
|
||
|
|
## Pros / strengths
|
||
|
|
|
||
|
|
- Fastest correct mental model of where CAP sits; the FAQ preempts the ACP/A2A confusion directly.
|
||
|
|
- Confirms fast-path optionality as the norm, which justifies tai's phased binding rollout.
|
||
|
|
|
||
|
|
## Cons / limitations / caveats
|
||
|
|
|
||
|
|
- Marketing surface, not normative; the manifest example on the page trims fields the spec requires (e.g. no `capabilities.streaming_output`).
|
||
|
|
- Status timeline may lag the repo (page says reference impl "in progress", repo STATUS says the driver matrix is done).
|
||
|
|
|
||
|
|
## Relevance to tai
|
||
|
|
|
||
|
|
Justifies phased conformance (PTY + one fast-path first) and records the licensing and governance facts the implementation conclusion relies on.
|
||
|
|
|
||
|
|
## Changelog
|
||
|
|
|
||
|
|
| Date | Change |
|
||
|
|
|---|---|
|
||
|
|
| 2026-10-18 | Initial dossier created. |
|