The Connect Plugin

The connect plugin compares an authored board with the PRDs, RFCs, and ADRs in a document repo, then reports where they disagree.

Purpose

The board comes first. /sync checks it against existing documents and shows which nodes have supporting evidence.

Unlike the code plugin, it does not generate nodes or build a graph from scratch.

Install and connect

The install id is pmap-connect. Add the marketplace and install the plugin.

/plugin marketplace add provenmap/pmap-claude
/plugin install pmap-connect@provenmap
# Restart Claude Code so the commands load.

Connecting

This plugin uses a binding credential, the same repo-to-board credential as the code plugin.

1. Copy the credentials. They appear when a governing source is bound, or later through Generate new secret in the binding's credentials dialog. The secret appears exactly once. Connecting Sources covers the setup.

2. Put the pair in .provenmap/credentials.json in the document repo. Only the owner can read and write it; /login uses mode 0600. Put the board and branch in .provenmap/config.json beside it. A credential field left in config.json is ignored.

Keep .provenmap/ in .gitignore. In CI, use PMAP_BINDING_TOKEN, PMAP_API_SECRET, PMAP_BOARD_SLUG, PMAP_BRANCH, and PMAP_BASE_URL; environment values take precedence.

3. Verify with /configure. It reads both files, validates fields, and tests the connection. It never asks you to paste a bindingToken or apiSecret into Chat.

Then use /status, /start, /logout, or /update as needed.

Note

This plugin never reads an MCP access token or updates host MCP config. That credential belongs to the architect plugin. Signing In & Credentials compares the two.

/sync

/sync mirrors the board locally, reads the repo's documents, and proposes an evidence link wherever a document supports a node. You review the proposals; it pushes approved links and reports drift.

After /login switch moves the binding to a different board, the next /sync carries the previous board's links into the new board's proposals for review. The plugin archives the previous store under .provenmap/boards/_orphaned/ instead of deleting it.

No prior analysis state is required, so a fresh clone can run it.

Important

The connect plugin's /sync links evidence. The code plugin's /sync pushes a graph.

The other commands

There are twelve commands. Two write project files. Run /help in your host for the installed plugin's own list.

Every command ends with an Outcome written for that run: what changed, what the run left, and the next command with its reason. The reason comes from the plugin's reading of this repo's state, blocking problems first. When the next step is an architect's, such as reviewing a pushed batch of insights, it appears as a Hand off line rather than a command.

What It Does Not Have

There is no /analyze, /analyze-archetypes, /adopt, /inspect, /build, or /monitor here. Those belong to the code plugin. The connect plugin needs an authored board first.

Choose the plugin