Files

T

retoor cc1c130b51 CAP protocol both directions: agent speak plus orchestrator drivers (1.39.0)

- Agent side: --cap-manifest plus --cap-speak stream-json binding with
  transcript-diff frames, diff/transcript artifacts, session config
- Orchestrator: PTY driver (settle heuristics on PtyProc/TuiVtScreen),
  stream-json, ACP-stdio (permission/elicit/fs/terminal serving) and
  A2A drivers (dual draft/current spelling, SSE mapping)
- Sessions, fleets: worktrees, master plans, mediated routing,
  budget refusal, audit log, research auto-answerer, --cap CLI
- cap.md contract with drift tests; research/cap-protocol archive
- Suites 1119 + 16 green

2026-10-18 13:17:35 +02:00

2.2 KiB

Raw Blame History

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.

2.2 KiB Raw Blame History