Skip to main content
RCP/1 is stable. These documentation pages are the readable specification — each protocol concept has its own page. This page is the map: it links every part of the normative document to the page that explains it, states the conventions, and shows a complete session end to end.

Normative document

spec/rcp-1.0.md — the single source of truth, RFC-2119 + JSON-RPC 2.0.

JSON Schema

Draft 2020-12 schema for every message shape.

Conventions

The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, MAY, and OPTIONAL are used as defined in RFC 2119 and RFC 8174 — and only when in ALL CAPS. All messages are JSON-RPC 2.0; all bytes are UTF-8 JSON.

Section map

Mapping SOTA techniques to RCP

Every mainstream retrieval technique maps onto an RCP surface — the protocol was designed backwards from the state of the art:

A worked session

A complete stdio session against a SOTA server — handshake, a hybrid + rerank + MMR retrieval with a filter and a progress stream, a cancelled call, and shutdown. is client→server, is server→client; one JSON object per line.
For evaluation and quality (Recall@k, MRR, nDCG@k, MAP) and the reproducibility handles behind them, see the normative Appendix F.