Last updated August 3, 2026
The Connect Plugin
Your PRDs, RFCs and ADRs already describe the system someone meant to build. The connect plugin runs in the repo where that writing lives, puts it next to the board, and tells you where the two disagree.
What it's for
Grounding, not architecture push. The board comes first — an architect authors it — and this plugin proves it against documents that already exist. Every board node either has writing behind it or it doesn't, and /sync is how you find out which.
That's the reverse of the code plugin, which reads a codebase and pushes a graph it built there. Nothing here invents structure: the connect plugin never mints a node you didn't author.
Install and connect
The install id is pmap-connect. Add the marketplace for your AI coding host, install it, and restart the host so its commands load. From there:
/loginsigns you in through the browser and connects this document repo to a board, writing the credential triple (bindingToken,apiSecret,boardSlug) into.provenmap/config.jsonfor you./configureis the manual path — hand-managed credentials, self-hosted instances, CI. It reads the config file rather than asking you for anything: never paste abindingTokenorapiSecretinto chat./statusshows what this repo is bound to,/startnames the next command to run,/logoutclears the local credentials, and/updatepulls the latest build.
Your secret comes from the platform once, when the binding is created — Connecting Sources has where to copy it and what to do if you missed the moment.
/sync
This is the command the plugin exists for. It mirrors the board locally, reads the repo's documents, and proposes an evidence link wherever a document backs a board node. You review the proposals, it pushes the link set, then it reports the drift — the places where board and documents no longer agree.
It's cold-start safe: no prior analysis state has to exist first, so a fresh clone can run it straight away.
The connect plugin's /sync and the code plugin's /sync are different commands doing different work — one links evidence, the other pushes a graph. Don't read a claim about one as a claim about the other.
The other commands
Twelve in total. Two write files in your project; the rest read, report, or push.
What it doesn't have
There's no /analyze, /analyze-archetypes, /adopt, /inspect, /build or /monitor here. Those are the code plugin's, and their absence is the point: this plugin never builds the layer hierarchy and never mints nodes and edges from a cold start. Give it a board first.