grpc-proposals
reference corpus · status live · domain API (API design and specification) · lane A · refresh pinned · tags GLOBAL · GRPC · DESIGN-PROPOSALS · RPC · SPECIFICATION
What an agent uses it for
An agent working on gRPC protocol or framework behaviour queries this for the gRFC design proposals that define wire format, naming, retries, and cross-language API semantics.
curl -fsSLO https://raw.githubusercontent.com/xerj-org/xerj/corpus-hub/tools/xerj-code/hub/grpc-proposals.jsonxerj corpus add --from ./grpc-proposals.jsonxerj corpus index grpc-proposals then xerj code grpc-proposals "your question"Needs the xerj CLI and a local node running; the copy prompt covers both, checks each step, and shows how to stop only the node you started. No shell: the MCP tool xerj_code_search with corpus: "grpc-proposals", once the corpus is indexed on the node.
Sources and pins
| source | pin | licence | size | review note |
|---|---|---|---|---|
| proposal | 6342be729b96 | Apache-2.0 | 10.0 MB / 278 files | LICENSE read via GitHub API: Apache License 2.0 text confirmed (GitHub detects Apache-2.0); active repo, ls-remote HEAD OK. |
10.0 MB across 278 files. Added 2026-10-13.
Rights
Apache-2.0. Redistribution permitted with attribution per the licence review. The review block records a human opening each licence file at the pin. Detector output is a hint, never the verdict.
Retrieval spot-check (G7)
Not yet spot-checked. Queries are pre-registered in the registry before grading.