Connecting Sources

Sources connect a board to code, docs, tickets, notes, and URLs that describe the real system.

For the catalog and governing-source rules, see the Sources Overview.

Before you start

Sources live in a workspace catalog. Register once, then bind where needed. You need contributor access or above.

A binding is governing when it shapes the board, or reference when Chat and insights read it without changing the board. Sources Overview covers source limits and the exclusive Code Plugin slot.

Register a source

Open the board's hub, find the Bindings card, and choose Add. In the catalog picker, choose Add Source.

• Note — paste the markdown or text, and give it a title.
• Web URL — paste the address, and give it a title you can recognize later.
• Code Plugin — name the source; credentials are issued later, when a board binds it.
• A connector — coming soon. Every provider is listed with Coming soon until it ships; see Provider Sources.

Registering is not binding. A source in the catalog does nothing until a board binds it.

Bind it to a board

From the Bindings card, Bind Governing Source starts a governing binding and Add starts either kind:

• Govern this board: this source shapes the graph, participates in sync, and can conflict with another governing source. The button reads Bind as governing source.
• Attach reference context: this source is read-only context. The button reads Attach reference source.

Bind a governing Code Plugin source and the board becomes an app board. Make this an app reaches the same result with fewer fields by registering the source for you. Use the binding dialog when the source is already in your catalog. App Boards & Hubs covers app board behavior.

The credentials you get once

When a governing Code Plugin binding completes, Plugin credentials — copy now opens automatically. It shows the binding token and API secret as two snippets: .provenmap/credentials.json for a local repo, and PMAP_BINDING_TOKEN, PMAP_API_SECRET, PMAP_BRANCH, PMAP_BOARD_SLUG, and PMAP_BASE_URL exports for cloud sessions or CI.

Copy them immediately. The live secret is shown only at issue — here, and each time you use Generate new secret later. Later credential views show ck_cp_live_****.

Expand

1. 1

   The amber warning is literal

   A live secret is shown once, at issue. Ask again later and you get a mask — generate a new one instead.

2. 2

   For a local repo

   One copy gives you the .provenmap/credentials.json block; /login or /configure writes the board and branch into config.json.

3. 3

   For a cloud session or CI

   The same values as exports, for a host where there is no config file.

Generate new secret issues an additional credential for the binding. Each machine keeps its own credential. Existing credentials keep working until you revoke them from the dialog's Connections list. Signing In & Credentials covers the lifecycle, The Code Plugin covers the fields, and the Boards API covers the request format.

Sources that come from a connector

Connector sources are coming soon. When a provider ships, you will authorize it once under Settings → Connectors, then use Add Source → Import from a connector → your provider to browse and select. Provider Sources covers what each will bring.

When a binding breaks

The board hub shows binding problems. Each binding has a pulse and sync state. Sources Overview explains each signal.

What's next