Skip to content

The Precedent handbook

Validate assistant work

Precedent helps assistants find and cite the decisions that constrain their work. Guidance, reminders, and review policy each have different limits.

Layer 1: the skill (advisory)

The decision-librarian skill asks the assistant to search before consequential choices, explain conflicts, and draft only with agreement. For Acme Robotics, a proposal to move search to Elasticsearch should lead the assistant to read AR-041 and explain why Postgres was chosen.

Instructions are advisory. An assistant can miss a relevant decision or skip a search. A cited decision still needs to be read in the context of the proposed change.

Layer 2: automatic reminders

Optional native hooks search when you submit a prompt and add any warnings and a small set of related decisions to context. The hook runs at a fixed point, but search cannot guarantee that every relevant decision is found.

The reminder does not inspect the full diff, judge whether a change complies, or block a push. Older shell push and Stop checks block on related search results; they do not verify that a citation or reconciliation happened.

Related does not mean conflicting. A change can touch a decided topic and fully respect the decision. Retrieval is evidence for a review, not its verdict.

Warnings: recorded facts

Alongside search, get_area_context and the reminder return warnings built only from the record: an exception that has expired or expires within 14 days, a superseded decision that the prompt names or a current decision still depends on, and a review past its date that is still open. Each warning names the decision, gives a one-line reason and link, and says what to do instead: propose a new exception or a replacement for people to approve.

A warning is precise but not complete. It covers only decisions you can see in the checked Areas, or that the prompt names by ref. It does not judge whether the work conflicts with a decision and does not block the assistant; the skill tells the assistant to show you the warning before it acts.

Layer 3: CI and review policy

The check-decisions GitHub Action comments on a pull request with the decisions that apply to the Areas it touches. It fails only on recorded facts: an expired exception in a checked Area, or a superseded decision the pull request cites. A failed check blocks merging only where the repository makes it a required status check.

If your team requires acknowledgement, define what reviewers must check, which changes require it, and how an intentional change to a decision is approved. A reference in a PR description alone does not prove compliance. People still accept revisions and supersessions in Precedent.

Discard unsaved changes?

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