Skip to content

docs(rcp): publish v1.0.0 spec with explicit stability policy #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Narrator merged 3 commits into from
May 28, 2026
Merged

docs(rcp): publish v1.0.0 spec with explicit stability policy #36

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b4d99c0
docs(rcp): publish v1.0.0 spec with explicit stability policy
May 28, 2026
836f7fa
docs(rfcs): commit RFC 0001 referenced by RCP v1 spec
May 28, 2026
5d9efd7
docs(rcp): correct ManifestEntry.id regex in §5.1
May 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -397,6 +397,8 @@ No single competitor combines build-time stable IDs, deep runtime capture, bidir

## MCP Tools

The agent-facing surface — tools, prompts, wire schemas, error envelope, and a stability policy — is specified by the **Runtime Context Protocol (RCP)**. RCP is versioned independently of this implementation. The current version is **[RCP v1.0.0](./docs/rcp/v1.md)**, published from `@domscribe/protocol@1.0.0`. IDE and agent vendors integrating against Domscribe should treat the spec as the contract; the table below is a human-readable index.

| Tool | Description |
| ----------------------------------- | --------------------------------------------------------------------------------------- |
| `domscribe.query.bySource` | Query a source file + line and get live runtime context (props, state, DOM snapshot) |
Expand All @@ -412,7 +414,7 @@ No single competitor combines build-time stable IDs, deep runtime capture, bidir
| `domscribe.annotation.search` | Full-text search across annotation content |
| `domscribe.status` | Relay daemon health, manifest stats, queue counts |

See the [`@domscribe/mcp` README](./packages/domscribe-mcp/README.md) for detailed tool schemas, response formats, and prompt definitions.
See the [`@domscribe/mcp` README](./packages/domscribe-mcp/README.md) for detailed tool schemas, response formats, and prompt definitions, and **[RCP v1.0.0](./docs/rcp/v1.md)** for the protocol spec and stability policy.

---

Expand Down
2 changes: 2 additions & 0 deletions TECHNICAL_SPEC.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -372,6 +372,8 @@ Pluggable transport layer for runtime ↔ overlay communication:

#### MCP Tools (for coding agents)

> The agent-facing surface — tool/prompt names, wire schemas, error envelope, and stability policy — is specified by [RCP v1.0.0](./docs/rcp/v1.md), versioned independently as `@domscribe/protocol@1.0.0`. The table below summarises what this implementation exposes; the spec is the contract.

| Tool | Description |
| -------------------------- | ------------------------------------------------------------------------------ |
| `annotation-get` | Retrieve annotation by ID |
Expand Down
Loading
Loading