Precedentdocs

Slack and Teams capture

Decisions get made in threads. Capture turns the thread into a draft decision without anyone leaving the channel.

Set up Slack

  1. Open Settings, Integrations as a workspace admin and choose “Add to Slack”.
  2. Approve the install in Slack. The install is bound to your workspace, so a thread captured in your Slack can only ever land in your record.
  3. Link channels on your nodes’ pages. A node’s channel gets its announcements, review notices, and a weekly digest of that node’s open items, and the link runs both ways: decisions captured in the channel are filed under the node. Decisions touching a restricted node appear everywhere in Slack as a bare reference and a link, never a title. Optionally pick a workspace channel too; it receives only a weekly count of open items no node channel covers.

Prefer to own the Slack app yourself? Install from the manifest shown in Settings, Integrations and paste the signing secret. With a bot token, chat accounts link by email and drafts carry the whole thread.

Uninstalling Precedent from Slack disconnects it here too: Slack tells us, and the connection is released straight away. A Slack workspace can only be connected to one Precedent workspace at a time, so this is what frees it to be connected somewhere else without an admin cleaning up by hand.

Capture a thread

/precedent what was decided

Run the command in the thread, or use the “Draft a decision” message shortcut. The thread becomes a draft in the owner’s inbox with the discussion attached as evidence. The first command from an unknown chat account replies with a link that binds it to the signed-in member, so nobody captures into a workspace they cannot see.

With a model account connected (see Ask AI), the thread is read and the draft arrives with a real title, summary, rationale, alternatives, and review trigger. The reply names what was filled in and says when the thread read more like an open discussion than a decision.

Capture never fails because AI failed. With no model connected, or if the call errors, the draft is written anyway with the first sentence as its title and the raw thread attached.

Suggested drafts from linked channels

Most decisions in a channel never get captured, because capture depends on someone remembering the command. A node that has named a Slack channel can also turn on “Suggest drafts from this channel” on the node’s page. With the toggle on, Precedent watches threads in that channel, and once a thread has been quiet for a while it asks the workspace’s own model one question: does this thread contain a decision that is not in the record yet? When the answer is yes, the bot replies once in the thread with a “Draft it” button. Clicking it runs exactly the same capture as /precedent: a draft in the clicker’s inbox, filed under the node, confirmed by a person or not at all.

  1. At most one prompt per thread, ever. A thread the classifier passes on can be reconsidered if the conversation continues; a prompted thread is done.
  2. At most five prompts per channel per day, and every classifier call is metered against the same daily AI allowance as Ask AI, visible on the Settings usage panel.
  3. Turning the toggle off, or clearing the channel, stops reads immediately, including for threads seen while it was on.
Privacy boundary: the toggle is off by default, and nothing in a channel is read unless an admin of the node turned it on. What is read: messages in that one channel, buffered as thread timestamps only; the text itself is fetched from Slack when a quiet thread is classified and is sent to the model account your workspace connected, never to one of ours. No AI key connected means no reading at all. Precedent stores which threads it looked at and what it did, not what anyone said.

Set up Teams

Teams capture uses an Outgoing Webhook: create one in your team pointed at the webhook URL shown in Settings, Integrations, and paste the security token it gives you. Mention the webhook in a thread to capture it, same flow as Slack.