How to pin evidence to your board

Open the source

Choose the citation marker ([n]) under a claim, or Show me the source in the inline strip below it (in a thread), or Show me the source on a pin (on your role home). The evidence panel opens docked beside the thread or the role home (reference); the address gains ?source=<id> so the view can be shared and revisited.

Pin it

Choose Pin on the passage, figure or table card in the panel. Pin is a single control: it reads “Pinning” while the call runs and the card shows the inline line “Pinned to your board” (or “Not pinned.”) at once. The web app calls POST /programs/{program_id}/pins with PinIn {target_type: chunk | asset, target_id}; the API answers 201 with PinOut {id, program_id, user_id, board, target_type, target_id, document_id?, licence_code, chip_class, attribution_line?, third_party_suspected, integrity_status, note, created_at, updated_at} and audits pin.create. One pin per target per person: pinning the same item again returns the existing pin.

To pin with a note, choose Add a note beside Pin: a one-line inline form expands under the card with the field “Note (optional, up to 300 characters)” and a live count; Enter pins with the note, Escape collapses the form and returns focus to Add a note. Fact (verified in web/components/console/evidence-panel.tsx:93-96, 116-123 and web/lib/content.ts:290-291): the control, the form and the 300-character check exist | Consequence: the note is built, and a board card shows it under the pin. The API also accepts target_type: record in PinIn, and PinOut carries record_type and href for a record pin so the board can open it (contract 12.3, recorded 2026-09-16). Fact (verified in api/app/schemas/workbench.py:92-93 and web/components/workbench/pin-card.tsx:40-41, 91-92): both fields exist and a record pin on the board carries Open the record | Consequence: opening a record pin is built. Fact (verified by grep: PinControl is rendered only in web/components/console/evidence-panel.tsx): no record page carries a Pin control | Consequence: pinning a record from its page stays designed.

Read your board

My evidence board is the third region of your role home. Each pin renders as the panel would: the chip in the reader’s words (“open access (CC BY)”, “share-alike”, “open access, no derivatives”, “metadata and link”, “internal”), the attribution line on every open-access figure, table and passage, the share-alike line where it applies, and the correction or retraction flag when the watch has found a notice. A pinned table row carries its column header and unit. A record pin shows “Record: <type>” and Open the record, which follows PinOut.href to the record page. GET /programs/{program_id}/pins returns your pins plus the program board.

Share to the program board

Choose Share to board on a pin. The control confirms inline, the API copies the pin as a board pin (board: true, shared_from_pin_id set), re-checks the licence code and the third-party flag, and shows the result in place. A target suspected of being third-party content inside an upload is refused with 422 third_party_content and the pin stays personal; the line under the control says why. Sharing needs program.documents.manage and audits pin.share. Board pins appear on every member’s board and in the program board view.

Unpin

Unpin is a single control with an inline confirmation line; it calls DELETE /programs/{program_id}/pins/{id} (your own pin, or a board pin under program.documents.manage) and audits pin.delete. Unpinning a personal pin leaves a board copy in place; removing the board copy needs the manage key.