Skip to content

The Precedent handbook

Record a decision

Turn a choice into a record someone else can understand, check, and revisit. Save a draft while the details are still taking shape.

In the editor, select one or more Area tags. If no Areas are available, workspace administrators can choose Create an Area; other members should ask an administrator to create one or grant access. Changes to decided decisions are saved with a revision and change note. Each Area shows the decisions explicitly tagged with it.

Start a draft

  1. Open your workspace and choose New decision. Members, Maintainers and Area administrators can create decisions on areas assigned to their groups. Administrators can create decisions anywhere in the workspace; Viewers have read access.
  2. Choose a Type under Type; a new decision starts as a Choice. Choosing another Type renames the fields in place and keeps what you typed.
  3. Fill in the first field, which is named after the Type, and Summary. Use a concrete title such as “Use Postgres full-text search for the product catalogue”.
  4. Choose an owner and one or more areas. Choose a review date or describe a condition that would make the team reconsider. Select Save as draft.

If you leave an edited decision before saving, choose Stay to keep editing or Discard changes to leave. This also applies to revisions and successors. Reloading or closing the tab uses your browser’s warning where supported. Returning every field to its original value removes the warning.

A draft can be incomplete. The checklist shows what still needs attention before it can be approved. Drafts created by capture or an assistant follow the same approval process.

You can reopen a draft, edit its summary or effective date, and save it again without a change note. Change notes are optional while drafting, including assistant updates. Leave the note blank to retain the existing draft note, or enter a replacement. Each save keeps the earlier revisions in history. Once decided, each revision requires a fresh change note.

Choose a Type

Every decision has one of seven fixed Types, chosen under Type in the editor. Its Type sets what it needs before it can be approved; see The seven Types.

Supersede an earlier decision

If the conflict check says a decided decision likely replaces an earlier one, choose Supersede on that finding and give a reason. Where your own approval is enough, the earlier decision is superseded at once by the one you are viewing. Otherwise the supersession is a proposed change, which needs the approvals of both decisions' Areas: the dialog's button reads Propose supersession, and the earlier decision stands until the supersession is approved on its page. On a draft, Supersede is one of the changes you can stage; see Resolve conflicts with staged changes below. Each Area's rule for approvals, access, and billing restrictions apply.

Below the check, open Recorded link impact to see current decisions with recorded inbound links to this decision, to the decisions it explicitly supersedes, and to the decisions it may replace. The disclosure shows how many were found. Impact follows recorded links; unlinked assumptions are not inferred. Review those decisions before superseding anything. If the impact check is unavailable, its message and retry link stay visible.

Write reasoning people can use

FieldWhat to record
Title (named after the Type)The choice itself, in one sentence. Avoid titles such as ‘Search discussion’.
SummaryWhat changes, what the decision covers, and any boundaries on it.
RationaleWhy this option won. In AR-041, Acme Robotics keeps search in Postgres to avoid operating a second datastore for its current requirements.
Alternatives consideredWhat lost and why. Elasticsearch was considered for AR-041, but its additional operating cost was not justified by the current search needs.
AssumptionsWhat must remain true for the choice to hold, such as the size of the catalogue or the search features users need.
OwnerThe person responsible for answering questions about the decision and reviewing it later.
ReviewOn a date, or when a condition is met. For example: reconsider when catalogue search needs exceed the agreed response-time target.

A how-to has a Steps field after Summary, with Write and Preview. Steps hold at most 3,000 characters; past that the counter turns red and saving is disabled until you shorten them.

On a Choice, use the Rationale, Alternatives considered and Assumptions controls to show those fields. Each Type shows only the fields it holds, and a field its Type requires is always shown. Text in a field the chosen Type does not hold is kept while you edit, and the editor says that saving removes it.

Record the losing option precisely. In AR-112, Moneyman had the cheapest quote but lacked UAE settlement, so Acme Robotics rejected it. “Too expensive” would preserve the wrong reason.

Precedent does not store credentials. A save, a proposed change, a note, evidence or a capture whose text looks like a password, key or token is refused, and nothing is saved. The message names the field and the line, so you can remove it and say where the credential is kept instead.

Read a saved decision

The Record tab starts with Summary (saved decision text) and Rationale (recorded reasoning), followed by Alternatives considered, Assumptions and then evidence, each named as the decision's Type names it. Each part starts with a line and its heading. Saved wording stays as written, including tentative wording. A how-to's Record tab shows its Steps after Summary, and the row under its title shows its expiry; see How-to. A fact's summary is its Detail, and the row under its title shows Last verified, the day its current text was last approved, in place of Decided; see Fact. A lesson's summary is What caught us out. A term's summary is its Meaning, at most 500 characters. An Area holds one decided term of each name, so a draft term named like a decided term in one of its Areas lists A different name as missing and cannot be approved; see Term. A draft how-to, fact, lesson or term lists, before its evidence, up to three decided decisions of those Types that share an Area with it and read alike, under Similar decisions, and a link under its title leads there. If it repeats one, archive the draft; if it replaces one, supersede that one from its own page. It never blocks approval.

A part with nothing recorded is not shown on its own. One line after the recorded parts names what is missing, for example Rationale, alternatives considered and assumptions not recorded. It names only fields the decision's Type holds. Evidence remains source material; it does not fill that gap. If you can edit the current draft or decided record, the line ends with Edit this draft to add them or Revise this decision to add them, except while a proposed change to the decision waits for approval. In the editor, choose Rationale to show the field. Historical and closed records offer no edit link.

Check the status and warnings above the record before relying on it. Conflict findings and change requests are on the decision's Conflicts tab, and links under the title lead to it. The tab shows a red number for conflicts that need attention, or a red dot when the check needs running or a change request is waiting. A decided decision that may only replace others shows a grey number, because nothing conflicts. One row under the title gives the owner, the Areas, the date it was decided and its review date, or its expiry for an exception. A side panel shows the actions you may take as buttons: Reaffirm, Revise and Supersede, then Ask AI about this and Trace impact, then Reverse on its own. A lesson also offers Make this a rule, which opens Supersede with Rule chosen. On a narrow screen the panel appears before the record. Administrative controls is a separate disclosure in the same panel. Record details, at the end of the Record tab, holds the supporting metadata. On a draft, one table above the tabs lists each of its Areas, what it still needs and who has approved, and the side panel names your next step, Approve or Ask for approval, with a sentence saying what it does. A request for changes sits above the table and quotes the person's note. Linked decisions, conditions and outcome history follow the supporting reasoning; Revisions and Event log keep the earlier text and recorded actions accessible.

Attach evidence and connect decisions

Evidence is added after the first save. Open the draft's Record tab and use the evidence controls to add a URL or upload a supporting file. Keep the material that lets someone check the reasoning, such as a comparison, meeting excerpt, or requirement.

Use Add link under Linked decisions to name another decision by reference. Choose depends on when this choice relies on it, affects when this choice changes its context, or departs from when this decision is an exception to it (see Record an exception). Use Supersede to create the successor relationship.

Access to a decision does not automatically grant access to an external evidence link. A teammate may still need permission in the system that hosts the linked document.

Approve the decision

  1. Check that the title, summary, owner, at least one area, and review date or condition are present. Complete anything else the decision's Type needs, such as an expiry date or a departs-from link; see The seven Types.
  2. Read the reasoning and evidence. If the draft was created by AI, check it against the original discussion before treating it as the team's choice.
  3. Choose Approve when your approval counts, or Ask for approval when the draft's Areas need other people. In the editor the same button reads Save and approve or Save and ask for approval.
  4. The status becomes Decided once the draft has the approvals each of its Areas requires. Share the decision's URL or reference and review it when its date arrives or its condition is met.

Each Area sets how many approvals a decision needs and whether the owner's own approval counts. The owner, an Area administrator or a workspace administrator asks for approval; anyone with Member access or higher to an Area can then approve, or request changes with a note. Viewer access does not allow approving, including for the owner. Billing and checklist requirements still apply. See Approve decisions.

Check conflicts on save

When you choose Run conflict check or Retry conflict check, the button shows Checking for conflicts… and is disabled until the check finishes. A message beside it explains that the check may take a moment. The result stays in the Conflict check panel; if the check is unavailable, you can retry. On a decided decision, Run conflict check sits beside Trace impact while your result is out of date or missing.

With a workspace model or the app-funded Luna default available, web editor and assistant saves compare the full decision text with visible, decided, currently effective guidance sharing an explicit Area tag. Decisions in unrelated Areas are excluded. The applicable decisions are ranked by similarity to the proposal, and the closest twenty that fit the model input limit are compared. When every applicable decision has an embedding, three quarters of those places go to the decisions closest in meaning and the rest to the best matches on the proposal’s words that are not already chosen, so a decision among the closest in meaning is compared even when it shares no word with the proposal. A decision that has no embedding yet is ranked on its words alone, and while many have none, more of the places go to word matches. The panel says how many of the applicable decisions were compared, then how many potential conflicts it found and which decisions they are, for example “Compared all 9 applicable decisions and found 1 potential conflict: AR-041. It needs a staged change or an acknowledgement before approving.”

The check reports two kinds of finding, each with references and source passages from both records. A conflict means that carrying out the proposal would break the earlier decision: the proposal requires or allows something that decision forbids, or prevents something it requires. A stricter limit, a rule for part of what the earlier decision covers, or an added requirement is not a conflict. Likely replaces means both decide the same question, so deciding the proposal would make the earlier decision obsolete; a restatement or a tightened limit is a replacement without being a conflict. A finding that is both, a different answer to the same question, is shown as Would supersede, and the message says the proposal would supersede that decision. The model selects numbered passages; the application copies their text, with ellipses between separate passages. Before asking for approval, explicitly acknowledge any conflicts, including Would supersede findings, unless a staged change answers them or the draft already supersedes that decision. Replacements that are not conflicts need no acknowledgement. Acknowledgement is recorded on the event that decides the draft and does not replace any earlier decision.

Opening a decision shows your stored verdict. When you can edit or approve a draft, opening its Conflicts tab runs the check if it has not run for you or is out of date; other tabs never run it. A decided decision's Conflicts tab lists only findings against decisions still in force: decided, effective today and not expired. It exists only while there is such a finding or a change request to answer. If the proposal, the compared guidance or the model configuration has changed since your verdict, or the check itself has been updated, it is marked out of date and approval waits until you run the check again. The verdict follows the individual findings: any finding where the proposal would break the earlier decision means conflicts, and otherwise the check is clear. The draft is saved even if the model fails, returns an answer in the wrong format or cites a decision or passage that was not supplied, the daily limit on the app-funded default is reached, the proposal alone exceeds the input limit, or the scope holds more than 200 visible areas or 1,000 applicable decisions. Approval waits for a successful retry. The check asks the model for an answer constrained to the expected format where the provider supports it. An answer in the wrong format, or one that cites something not supplied, is sent back once with the reasons for a corrected answer before the check reports unavailable; that second request counts towards the AI allowance like any other. Where neither a workspace model nor an app-funded default is configured, approving remains available after manual review. AI can miss conflicts or flag compatible decisions, and a conflict with a decision outside the closest twenty goes unseen; check the quoted evidence yourself. Revisions to already decided decisions are checked after saving and keep their Decided status.

To get help resolving a finding, choose Suggest a fix on it. Each request is one AI call against the workspace allowance, made only when you ask. The model receives only the two decisions of that finding, both of which you can already see, and suggests one action: amend the existing decision, supersede it, reverse it, edit the new proposal, or record the proposal as an exception with a departs-from link. The finding then shows the suggestion with the current and suggested text of each changed field, the change note for the existing decision, and a short explanation. For example, if a draft retains raw images for 30 days and AR-097 requires deletion within seven days, the suggestion may shorten the draft's retention to seven days.

A suggestion never changes anything by itself, and you can ignore it. For a change to the draft, Apply to this draft opens the editor with the suggested wording filled in. Nothing is saved until you save, and saving runs the conflict check again. For a suggested change, reversal or supersession of the existing decision on a draft, Edit and stage opens the same dialog as Propose a change, Reverse or Supersede on that finding (see Resolve conflicts with staged changes below), filled in with the suggested wording and change note or reason. Change any of it, then stage it, or close the dialog and nothing is staged. Edit and stage appears only where you are allowed to make that change to the existing decision. To decide later instead, Add to my inbox opens the same filled-in dialog and keeps the change as an item in your inbox, or, when someone else owns that decision, can open the draft and is allowed to make the change, Add to Priya Shah's inbox sends it to them. Nothing changes until it is accepted from the inbox; a supersession can be accepted once the draft is decided. Where neither applies, the suggestion says who can make the change. Where a change to that decision is already staged, the suggestion starts from the staged text, because that is what the check compared; review the staged change on the finding instead. A suggestion belongs to your current check: when the draft, the compared guidance or the model changes, it is hidden until you run the check and ask again. Staging another finding's change keeps the other suggestions, and running the check again keeps each suggestion whose two decisions have not changed. Staging marks the check out of date, and the Conflicts tab runs it again. If no model is configured, the AI allowance is reached, the provider fails, or the model returns a suggestion that does not fit the record, the page says so and nothing changes.

Resolve conflicts with staged changes

When the check lists conflicts on a draft, you can change the draft, or stage changes to the earlier decisions it conflicts with. Each finding, Conflict, Would supersede or Likely replaces, offers the actions you are allowed to take on that decision, with Supersede first on Would supersede and Likely replaces findings: Propose a change opens its current text for editing with a change note, Reverse ends it with a written reason, and Supersede replaces it with the draft. Edit this proposal opens the draft itself. Actions you cannot take are not shown: proposing a change follows the rules for revising that decision, and reversing and superseding follow the existing rules for those actions.

Every change is optional. Stage any of them or none, and choose Remove on a staged change to drop it; a removed change is never applied. Staged changes are saved on the draft and change nothing until the draft is decided, in the web app, from Slack or by accepting the prompt their assistant's app shows (Approve a draft). Deciding the draft applies every staged change in the same step, or none of them. A proposed change becomes a new revision of the earlier decision, with your change note and a reference to the draft, and must still meet that decision's Type checklist. A reversal keeps the record, with Reversed status and your reason. Abandoning or archiving the draft leaves the earlier decisions as they are.

Staging or removing a change, or editing a proposed change's text, marks the conflict check out of date. The Conflicts tab runs it again when you return to it: a decision with a staged change is compared as amended, so the check shows whether the change resolves the conflict. If someone revises or reverses an earlier decision after you staged a change to it, approval waits until you stage the change again or remove it. A proposed change keeps the earlier decision's review date or condition, so it is not offered once that decision's review date has passed: review the decision first. A staged change whose decision becomes due before the draft is decided is flagged, and approval waits until the decision is reviewed or the change is removed. The approval dialog lists what will happen, for example “This changes AR-041 and reverses AR-112. AR-087 is unchanged.” Conflicts without a staged change still need the acknowledgement. The event that decides the draft records each conflicting decision as changed, superseded, reversed or left as is, and each changed decision's history names the draft. A change staged from a suggestion is marked From an AI suggestion on the draft, and the event that decides the draft and the changed decision's revision or event say it was suggested by AI and name the person who staged it, for example “AR-041 changed (suggested by AI, accepted by Dana Reyes)”. With nothing staged, approving works as it always has.

A draft created as the successor of an earlier decision, from Supersede on that decision or by an assistant, already supersedes it when decided. Its finding shows Supersession pending instead of any staging action, the conflict needs no acknowledgement, and asking for approval needs the reason. To keep the earlier decision, or change or reverse it instead, choose Remove supersession on the finding or remove the link under Linked decisions; this is possible only while the successor is a draft. A completed supersession stays in the history.

When you cannot make a change to an earlier decision yourself, the finding offers to ask its owner instead, for the changes the owner is allowed to make. The button names the owner, for example Ask Priya Shah to review a change, a reversal or a supersession. Write the proposed text or reason, and the owner gets an inbox item and an email that quote both conflicting passages and your proposal. The finding then shows Waiting for the owner, and you can withdraw the request. Approving the draft does not wait: a pending or declined request leaves the earlier decision as it is, so the conflict still needs the acknowledgement. If the owner accepts, the change is proposed on their decision and applies once its Areas' approvals are in. It applies at once where the owner's approval is enough. If the earlier decision is revised after you asked, the request stays open and the owner reviews the change against the current text before accepting. A supersession can be accepted once your decision is decided. Archiving the draft closes its requests without a change, and so does reversing, superseding or archiving the earlier decision.

If approving is unavailable

Read the checklist and the explanation beside the action. Missing fields, Type requirements, your access to the draft's Areas, an Area rule that cannot be met, or a read-only workspace can prevent approving. A workspace administrator can help with roles and Area rules in Settings; subscription expiry is covered in Plans and billing.

Discard unsaved changes?

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