The Precedent handbook
The seven Types
Every decision in Precedent has one of seven Types. The Type sets what the decision holds and how assistants receive it.
At a glance
| Type | Answers | Example |
|---|---|---|
| Choice | What did we choose, and why? | AR-012, “Use Postgres full-text search for the parts catalogue.” |
| Rule | What must we always or never do? | AR-055, “Never run a database migration during a release window.” |
| Exception | What is waived, for whom, until when? | AR-118, “Keep raw inspection images for 30 days instead of seven.” |
| How-to | How do I do this here? | AR-130, “Restore the staging database from last night's backup.” |
| Fact | What is true about our setup? | AR-144, “The warehouse robots report telemetry every 30 seconds.” |
| Lesson | What caught us out, and what to do instead? | AR-151, “Pause the telemetry import before resizing its database.” |
| Term | What does this word mean here? | AR-160, “Fleet.” |
Choice
A choice records what the team picked from the options it had, and why. Use it for an approach, a tool, a vendor or a design that someone could reasonably have done differently. Note the options that lost and why, so the question is not reopened without new facts. Example: AR-012, “Use Postgres full-text search for the parts catalogue.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, and a review date or condition. |
| Default review | None |
| How assistants receive it | Loaded with its Areas, and searched before a consequential choice. |
Rule
A rule is a standing instruction: something the team always or never does in an Area. It needs a rationale, because a rule nobody can explain gets ignored. Assistants read rules first and treat them as instructions for the Areas a rule is tagged with, so tag it with every Area it covers. Example: AR-055, “Never run a database migration during a release window.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, a review date or condition, and a rationale. |
| Default review | 365 days |
| How assistants receive it | Loaded first for the Areas it is tagged with. |
Exception
An exception waives a rule or choice for a named case until a set date. It says what is waived, why, what reduces the risk meanwhile and which decision it departs from, and it needs approval from someone other than its owner. From the day after its expiry date it shows as Expired, and the decision it departs from applies again in full. Example: AR-118, “Keep raw inspection images for 30 days instead of seven.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, an expiry date, a departs-from link, a rationale, its compensating controls, and approval from someone other than its owner. |
| Default review | None |
| How assistants receive it | Loaded with its Areas, and searched before a consequential choice. |
A one-person workspace cannot decide an Exception until a second person has access.
How-to
A how-to says how to do one task here, in steps that fit on one screen: at most 3,000 characters. Write the steps as a numbered list and put commands in code blocks. Never paste a password, key or token; say where it is kept. Assistants see a how-to's title and summary with its Areas and read the steps when the task needs them, and they offer its commands to you rather than running them. A how-to has an expiry date, so someone checks the steps still work. Example: AR-130, “Restore the staging database from last night's backup.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, an expiry date, and steps. |
| Default review | 180 days |
| How assistants receive it | Listed by title and summary; the full text is fetched when the task needs it. |
Fact
A fact records something true about your setup that later work depends on, such as a limit, a schedule or where something lives. Put the fact in one sentence, and say in the detail where it holds and how to check it. A fact has an expiry date: after it, assistants treat the fact as possibly untrue until someone checks it and reaffirms it. Example: AR-144, “The warehouse robots report telemetry every 30 seconds.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, and an expiry date. |
| Default review | 180 days |
| How assistants receive it | Listed by title and summary; the full text is fetched when the task needs it. |
Lesson
A lesson records something that caught the team out and what to do instead. The title says what to do instead; What caught us out says what happened, when and what it cost. Assistants read the lessons for an Area and warn you when work is about to repeat one. When it should be followed every time, choose Make this a rule on the lesson to supersede it with a rule. Example: AR-151, “Pause the telemetry import before resizing its database.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, and a review date or condition. |
| Default review | 365 days |
| How assistants receive it | Loaded with its Areas, after rules and terms. |
Term
A term records what a word means here, so people and assistants use it the same way. The title is the word as people write it, and the meaning is one or two sentences, at most 500 characters. An Area can hold only one decided term with each name. Assistants read terms first, with the rules. Example: AR-160, “Fleet.”
| Item | For this Type |
|---|---|
| Needs before it can be approved | A title, a summary, an owner, at least one Area, and a review date or condition. |
| Default review | 730 days |
| How assistants receive it | Loaded first for the Areas it is tagged with. |
Choosing a Type
| Types | How to choose |
|---|---|
| Choice or Rule | Did you pick between options once, or must people always or never do something? A choice records the pick; a rule is followed every time. |
| Fact or How-to | Is it something true, or something to do? A fact is one sentence you can check; a how-to is steps you follow. |
| Lesson or Rule | A lesson says what went wrong and what to do instead. When everyone must do it every time, supersede the lesson with a rule. |
Changing a Type
A draft's Type can change at any time; text that does not belong to the new Type is named before it is removed. A decided decision changes Type only in a revision with a change note, and the revision needs the approvals its Areas require.