Skip to content

The Precedent handbook

Capture from chat and transcripts

Decisions get made in threads and meetings. Capture turns a Slack thread, or a pasted meeting transcript, into draft decisions.

Set up Slack

  1. Open Settings, Integrations as a workspace administrator 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 areas’ pages. An area’s channel gets its posts, review notices unless the Area turns them off, and a weekly digest of that area’s open items, and the link runs both ways: decisions captured in the channel are filed under the area. A new draft is posted to its Area’s channel however it was created: in Precedent, from Slack, or by an assistant. Decisions touching a restricted area 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 area 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 a workspace administrator cleaning up by hand.

The Slack app is covered by the privacy policy. For help installing or using it, see the support page.

A workspace administrator can turn off approving and reaffirming from Slack under Settings, Approvals; posts still go out, without the Approve and Reaffirm buttons.

Connecting your Slack account

Precedent needs to know which member a Slack account belongs to. An email match, or the link the first command replies with, connects the account well enough to draft from Slack. Approve and Reaffirm buttons in Slack need more: sign in with Slack once, either from Settings, Integrations, or from the link Slack replies with, so Slack itself confirms the account is yours. Signing in with Slack needs the Precedent app from Slack; a workspace that runs its own Slack app can draft only from Slack.

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 workspace model or the app-funded Luna default available, the thread is read and the draft arrives with a real title, summary, rationale, alternatives, and review date or condition. 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 neither model available, or if the call errors, the draft is written anyway with the first sentence as its title and the raw thread attached.

Approve a draft from Slack

Precedent rewrites the posts it sends rather than posting again. A decided draft’s post names everyone whose approval counted and drops its Approve button, a reaffirmed decision’s row in a review post names who reaffirmed it and drops its Reaffirm button, and a reversed or archived decision’s post says Reversed or Archived.

A draft’s post in its Area’s channel carries an Approve button once approval has been asked, or before that when the owner’s own approval counts in every Area the draft needs. While approval is asked the post says Awaiting approval, who asked, and how many more approvals each Area needs, for example “Needs 1 more from Payments and 2 more from Security”, and “Changes requested” while a request for changes is open. A post that cannot name every Area still short, because one is restricted or archived, says “Needs more approvals” instead.

Approve opens a form that lists each Area the draft needs, with how many approvals it needs and how many it has, and says whether yours is the last one needed. Submitting it records your approval, as you, if you could approve the draft in Precedent; the draft becomes Decided when your approval completes every Area’s rule. Connect your Slack account with Sign in with Slack first.

If nobody has asked for approval yet, the owner, an Area administrator or a workspace administrator can ask from the same button: submitting asks for approval and records their approval where it counts. Where their own approval does not count, the form says so and its button reads Ask for approval. A draft with unresolved conflicts, or one that supersedes or changes other decisions, is sent for approval in Precedent, where the reason and those changes can be given in full; once it is, people can approve it from Slack.

The form says why instead when you need Member access to one of the draft’s Areas, when your approval does not count because you own the draft, when your Areas already have the approvals they need, and when nobody has asked for approval yet. Requesting changes, withdrawing an approval and closing a request for approval (Back to draft) happen in Precedent.

If a review date or condition is the only thing a draft is missing, the form asks for it first. Saving it adds a new revision to the draft, and the form then shows what approving will do. The review stays on the draft if you close the form before approving. This needs a draft whose approval is not asked yet, and its owner, an Area administrator or a workspace administrator pressing Approve. Anyone else finishes the draft in Precedent.

Get feedback when you capture

After saving, the reply reports current decisions with recorded dependency or affects links to the new draft and to any decision it explicitly supersedes. Impact follows one level of recorded links; assumptions that nobody linked are not inferred. Linked decisions and counts respect your access. Chat replies keep titles and dependency details in the signed-in app.

When a workspace model or the app-funded default is available, a Slack capture runs the model-based conflict check for the person who captured it as the draft is created. For anyone else who opens that draft, and for anyone who opens a transcript draft, the check runs the first time someone who can edit or approve the draft opens its Conflicts tab. The check compares the full text with the closest applicable guidance in the draft's areas and reports conflicts, which need acknowledgement before asking for approval, and decisions the draft likely replaces, each with a Supersede control for an authorised person. Filing alone never changes an earlier decision. See Record a decision for failure handling and scope limits.

The link check needs no AI key and runs after saving; a failed check leaves the saved draft intact.

Transcript capture shows feedback for each new draft above the inbox. The same feedback is available on the decision page and in an assistant's draft response.

Suggested drafts from linked channels

Chat capture requires a linked area where the capturing user has Member, Maintainer or Area administrator access. Administrators can capture unassigned drafts. Most decisions in a channel never get captured, because capture depends on someone remembering the command. An area that has named a Slack channel can also turn on “Suggest drafts from this channel” under For integrations on the area’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 configured automation 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 area, approved by people 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 counted with the workspace’s other provider calls, visible on the Settings usage panel. Calls that use the app-funded default stop at the daily limit.
  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 area or workspace administrator 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, or Precedent’s Luna account when the app-funded default is configured. With neither available, no reading takes place. Precedent stores which threads it looked at and what it did, not what anyone said.

Paste a meeting transcript

Meetings decide more than threads do, and meeting tools hand you a transcript nobody rereads. From the New decision page, follow “Paste it and Precedent finds the decisions”. Your workspace model, or the app-funded Luna default, reads the pasted transcript for decisions the meeting actually reached; several per meeting is normal. When Acme Robotics pastes the standup where they settled AR-041, the candidate arrives with the title, the rationale (“one datastore is one failure mode”), and the verbatim lines where the call was made, so the model’s reading can be checked against the transcript.

  1. Nothing is captured until you tick the candidates you want. A candidate the model read as still open is marked and unticked by default, so a discussion does not become a record by accident.
  2. Choose an area where your group role is Member, Maintainer or Area administrator before extraction. Each ticked candidate becomes a draft on that area, owned by you, with its supporting excerpt kept beneath the summary. Add a review date or condition, then approve it or ask for approval, the same as any other draft.
  3. Every read is counted with the workspace’s other provider calls, using your workspace model or the app-funded default. Only the app-funded default has a daily limit. Unlike thread capture there is no no-model fallback: with neither model available the page says so and reads nothing, and a failed read costs a retry, not a draft, because the paste stays in the form.

Discard unsaved changes?

Your changes have not been saved. Stay to keep editing, or discard them and leave.