Skip to content

Precedent and Rationale Repository

Maintained register — instantiates Institutional Rule–Role Stabilization

Keeps an indexed archive of past decisions and the reasoning behind them, so like cases are decided alike and the institution's memory outlives its people.

When every case is decided from scratch, the same facts get opposite rulings depending on who happens to be on duty, and the reasoning behind hard calls evaporates the moment the people who made them leave. Precedent and Rationale Repository fixes both by accumulating past decisions together with the reasoning that produced them into an indexed, retrievable corpus that later decisions are checked against. Its defining move is storing the why, not just the what: an outcome-only log tells you what was done, but a rationale-bearing archive lets a future decider see whether their case truly matches — and lets a bad precedent be re-argued against its own stated reasons rather than blindly followed. It is the institution's working memory, and the quiet engine of consistency across both cases and staff turnover.

Example

A large platform's trust-and-safety team rules on thousands of edge cases a day — borderline posts, novel scams, appeals. Early on, two nearly identical reports get opposite outcomes because different moderators caught them, and nobody can reconstruct why either call was made. The team builds a precedent repository: each significant ruling is filed with the facts, the specific policy applied, and a short rationale. New cases are searched against it by fact-pattern, and a moderator who wants to depart from a matching precedent has to say why — distinguishing the case or arguing the precedent is wrong.

Over a year it becomes the team's internal "case law." A new hire on their first week can decide a gnarly case the way a five-year veteran would, because the veteran's reasoning is on file. Consistency stops depending on individual memory, and when a past ruling turns out to be mistaken, it can be overruled on the record rather than quietly contradicted.

How it works

  • Capture decision + rationale. File each significant ruling with its facts, the rule applied, and the reasoning — not just the outcome. (These are the decision memos it archives.)
  • Index for retrieval. Organize by fact-pattern and issue, not merely by date, so the relevant precedent actually surfaces when a like case appears.
  • Make consultation a step. Require new decisions to check precedent first; a departure must be justified by distinguishing the facts or overruling the prior call.
  • Keep it revisable. Provide an explicit overrule path so bad precedents are re-argued and retired against their reasons, not silently ignored or permanently entrenched.

Tuning parameters

  • Bindingness — whether precedent strictly governs or merely advises. Strict binding buys consistency; loose binding buys adaptability to novel cases.
  • Capture threshold — which decisions get recorded, from every ruling to landmark cases only. Broader capture means richer memory but heavier curation.
  • Indexing richness — how finely cases are tagged and cross-referenced. Better retrieval, higher upkeep.
  • Overrule friction — how hard it is to depart from precedent. High friction stabilizes; too high ossifies.
  • Access breadth — who may read it. Wide access aids consistency and transparency; some sensitive cases argue for limits.

When it helps, and when it misleads

Its strength is consistency, equal treatment, and durable memory: like cases get like outcomes, decisions survive the people who made them, and the institution stops re-litigating settled questions. This is path dependence used deliberately — the stabilizing kind.[1]

Its failure mode is the same force turned pathological: a repository with no overrule path entrenches past mistakes, and "we've always decided it this way" becomes a substitute for a reason rather than a summary of good ones. A rich body of precedent can also be cherry-picked — cited selectively to justify almost any position — and a growing archive can calcify an institution against change it needs. The discipline is to store rationales, not just outcomes, and to keep a real overrule path: a precedent that can be re-examined against the reasoning that created it stays a memory; one that can only be obeyed becomes a cage.

How it implements the components

  • institutional_memory_and_record — it is the durable, indexed record of what the institution decided and why, held independently of any current office-holder.
  • interpretation_and_discretion_rule — accumulated precedent becomes the working rule for how ambiguous cases are read and how far an office-holder's discretion runs.

It does not justify any single live decision (that's the Public-Reason Decision Memo, whose outputs the repository files) or set the formal rules the precedents interpret (that's the charter, bylaws or operating agreement).

References

[1] Stare decisis — the common-law principle of standing by decided cases so that like cases are treated alike. Departures are permitted but must be reasoned, which is exactly why storing rationales (not just outcomes) matters. ↩