Precedent Guided Decision Governance

Make prior decisions reusable without making them permanent: bind or guide later cases through explicit authority, relevant similarity, rationale, and reliance, with visible rules for distinguishing, reconciling, and overruling precedent.

Version

v1 · 2026-08-24 · History

Solution archetype #

769

Problem family

Authority, Accountability, Legitimacy & Fair-Process Failure

Problem subfamily

Rules, Rights, Obligations & Consistency

Essence

Precedent-Guided Decision Governance makes prior decisions reusable without pretending they are permanent. A prior case guides a later one only after the decision maker checks who had authority, what facts were material, which rationale controlled, whether the precedent remains valid, and whether the new case is similar in the ways that matter.

The pattern joins continuity to controlled change. It lets a system follow, extend, narrow, distinguish, reconcile, suspend, or overrule prior decisions through visible rules. The result is not “do what happened last time.” It is cumulative decision learning with reasons, authority, fair notice, and an update path.

Compression statement

Repeated decisions become arbitrary when every case starts from zero, but they become rigid when yesterday's answer controls merely because it came first. Precedent-Guided Decision Governance treats a prior decision as a defeasible rule-plus-example. It records the deciding authority, material facts, issue, outcome, governing rationale, scope, and later treatment; retrieves prior cases through relevant similarity rather than surface resemblance; checks whether the precedent is authoritative and still valid; explains whether the new case follows, extends, narrows, distinguishes, reconciles, or overrules it; protects justified reliance and equal treatment; and updates the precedent corpus so future decisions inherit the change. The intervention produces consistency with reasons, not mechanical repetition, and adaptation with traceability, not unbounded discretion.

Canonical formula: prior_decision + authority_rank + material_fact_and_rationale_model + relevant_similarity_test + current_validity_check + follow_distinguish_overrule_rule + reliance_and_fairness_review + corpus_update -> consistent_yet_adaptive_decision_governance

When This Archetype Applies

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

Diagnostic problem

A system makes recurrent consequential decisions but lacks a reliable way to carry reasons and constraints from earlier cases into later ones. Decision makers either improvise anew, creating unequal treatment and duplicated reasoning, or invoke prior outcomes without checking authority, factual similarity, rationale, later developments, or justified exceptions. The result is inconsistency, hidden path dependence, selective precedent citation, stale rules, and weak accountability for departures.

What this problem means

Without precedent governance, recurrent decisions oscillate between reinvention and inertia. Reinvention produces unequal treatment, duplicated analysis, and arbitrary dependence on the assigned decision maker. Inertia reproduces an earlier answer even when its facts, authority, rationale, evidence, or context no longer fit.

The hidden difficulty is that similarity is not self-executing. Cases can resemble each other on visible features while differing on the fact that actually supports the rule. Conversely, decision makers can manufacture narrow differences to avoid a precedent they dislike. The archetype makes the dimensions of analogy, authority, and departure inspectable.

Applicability expression6 distinct conditions

Recurring comparable casesandComparable treatment expectationandRule-exceeding prior reasoningandOpen-textured rulesandJustified precedent departureandReliance on settled practice

Algebraic1∧2∧3∧4∧5∧6

groundedpartly groundedopen

6 conditions, all required.

6Required in every casenumbered 1–6

These hold no matter which pattern applies.

1

Recurring comparable cases · grounded

Similar disputes, approvals, exceptions, sanctions, benefits, or incidents recur. more

primePrecedent (Stare Decisis)— Past decisions guide future.

and — also required

2

Comparable treatment expectation · grounded

Stakeholders reasonably expect comparable cases to receive comparable treatment. more

primePrecedent (Stare Decisis)— Past decisions guide future.

and — also required

3

Rule-exceeding prior reasoning · grounded

Prior decisions contain useful reasoning not fully captured in a general rule. more

primePrecedent (Stare Decisis)— Past decisions guide future.

and — also required

4

Open-textured rules · open

Existing rules contain ambiguity, exceptions, open-textured standards, or discretionary gaps. more

and — also required

5

Justified precedent departure · grounded

A later case may need to distinguish or change an earlier approach without arbitrary departure. more

primePrecedent (Stare Decisis)— Past decisions guide future.

and — also required

6

Reliance on settled practice · open

Reliance on settled practice makes abrupt unannounced change costly or unfair. more

Other requirements and context (2)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

• Supporting contextDecision authority is hierarchical, federated, or split across bodies with different weight. more

• Supporting contextThe corpus is large enough that selective memory or retrieval bias can shape outcomes. more

Coverage

4 of 6 conditions grounded · 2 open.

Read the methodology · Download the trigger-logic data

When to Use This Archetype

Use it when a system repeatedly decides comparable disputes, approvals, exceptions, sanctions, benefits, incidents, or classifications and stakeholders reasonably expect like cases to receive like treatment. It is especially useful when general rules leave interpretive gaps, prior decisions contain reasoning not captured in policy, and abrupt unexplained change would undermine reliance or legitimacy.

Do not use precedent merely because an old case is available. If the task is a stable computational subproblem, ordinary reuse or caching is enough. If the old outcome is unexplained, biased, secret, or invalid, its repetition is not governance. If a clear current rule resolves the issue, precedent may illustrate but should not displace the rule.

Structural Problem

Without precedent governance, recurrent decisions oscillate between reinvention and inertia. Reinvention produces unequal treatment, duplicated analysis, and arbitrary dependence on the assigned decision maker. Inertia reproduces an earlier answer even when its facts, authority, rationale, evidence, or context no longer fit.

The hidden difficulty is that similarity is not self-executing. Cases can resemble each other on visible features while differing on the fact that actually supports the rule. Conversely, decision makers can manufacture narrow differences to avoid a precedent they dislike. The archetype makes the dimensions of analogy, authority, and departure inspectable.

Intervention Logic

Start by defining which institutions and decision types create binding, persuasive, local, temporary, or nonprecedential guidance. Build structured records that preserve issue, material facts, holding, rationale, scope, authority, evidence, dissent, and later treatment. Retrieve both supporting and adverse cases. Compare material facts through the rationale, check current validity, and resolve conflicts through explicit hierarchy and scope rules.

Every new decision then declares its treatment of precedent. Following applies the prior rationale to materially similar facts. Extending carries the rationale into a justified new range. Narrowing reduces scope. Distinguishing identifies a difference material to the rationale. Reconciling resolves apparent conflict. Overruling rejects the old rule through authorized review, with reliance, notice, remedy, and transition considered. The final decision updates the corpus so future users inherit the treatment.

Key Components

Component	Description
Precedent Authority Map ↗	The authority map prevents retrieval rank, age, or repetition from masquerading as legitimacy. It identifies who may create precedent, where it binds, what review level it carries, and how jurisdiction, publication status, and explicit nonprecedential treatment alter weight.
Structured Precedent Record ↗	A precedent record is more than a result. It preserves the issue, material facts, holding, governing rationale, scope, authority, evidence, dissent, implementation conditions, and treatment history. Without that structure, users copy outcomes and overgeneralize accidental details.
Holding–Rationale Boundary ↗	This boundary states what proposition was necessary to the decision and why. Commentary, illustration, dicta, or implementation detail may inform later reasoning but should not silently become binding. Where several rationales compete, uncertainty must be recorded rather than erased.
Material-Fact Similarity Model ↗	Similarity must be anchored to the prior rationale. The model explains why each factual dimension is relevant and what difference would change the decision. It protects against both superficial analogy and opportunistic distinction.
Retrieval and Adverse Search ↗	Search must return supporting, limiting, conflicting, and negative precedent. A decision maker who searches only for agreement can define the case universe to fit a preferred result. Search coverage, filters, exclusions, and tool ranking therefore require review.
Current Validity and Conflict Rules ↗	Every candidate precedent needs current treatment status. Conflicts are resolved through authority, jurisdiction, issue, scope, specificity, recency, and review level—not by automatically choosing the newest or most frequently cited case.
Treatment Decision and Departure Gate ↗	The present decision explicitly classifies how it treats each controlling precedent. Major departure requires proportionate evidence, authority, reason-giving, and review. This makes change possible without hiding it in invented factual differences.
Reliance, Fair Notice, and Transition ↗	People arrange behavior around settled practice. A changed rule may need notice, prospective application, migration support, or remedy. Reliance governs the manner of change; it does not permanently immunize error or injustice.
Corpus, Citation Graph, and Drift Monitor ↗	The corpus makes decisions discoverable and connects later treatment to earlier cases. A drift monitor searches for unexplained variation, selective citation, stale precedent, unequal exception access, and superseded rules that remain active in playbooks or models.

Common Mechanisms

A precedent case brief captures the structured record. An authority-and-validity table ranks cases and exposes later treatment. A material-fact comparison matrix makes analogy testable. An adverse-search protocol counteracts confirmation. A follow–distinguish–overrule memo documents treatment and reliance. Conflict panels handle recurring high-stakes clashes. Citation graphs propagate status changes. Change notices manage transition, and consistency audits test whether the system actually treats materially similar cases alike.

These are mechanisms, not the archetype itself. A case database can exist without authority rules, fair notice, adverse search, or controlled change. A memo can document an arbitrary choice. The archetype is the coordinated governance pattern connecting all of them.

9 documented mechanisms across 6 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Analysis, Modeling & Optimization · 1 mechanism

• Material-Fact Comparison Matrix — Compares the current and prior cases on rationale-linked factual dimensions and records which differences are material and which are not.

Assessment, Review & Assurance · 1 mechanism

• Precedent Consistency Audit — Samples recurrent decisions to test whether similar cases were treated alike, citations were complete, exceptions were equally available, and status stayed fresh.

Control, Automation & Runtime · 1 mechanism

• Precedent Citation Graph — Represents authority, citation, and treatment relationships among decisions and propagates narrowing, supersession, and overruling alerts through the network.

Organization, Role & Governance · 1 mechanism

• Precedent Conflict Panel — An authorized review body that resolves recurring or high-consequence conflicts among prior decisions and sets the controlling line.

Protocol, Workflow & Routine · 2 mechanisms

• Adverse-Precedent Search Protocol — Requires search for cases that limit, distinguish, conflict with, or undermine the proposed precedent treatment before a decision is finalized.
• Precedent Change Notice and Transition Plan — Communicates changed guidance, whose reliance is affected, the effective date, how pending cases are treated, and what remediation and migration support apply.

Representation, Specification & Plan · 3 mechanisms

• Follow–Distinguish–Overrule Memo — States the precedent treatment choice, its material reasons, the authority relied on, reliance effects, effective scope, and the review route.
• Precedent Authority and Validity Table — Displays candidate precedents side by side by authority, scope, jurisdiction, current validity, and later treatment.
• Precedent Case Brief — A structured brief recording a single precedent's authority, issue, material facts, holding, rationale, scope, dissents, implementation conditions, and later treatment.

Parameter / Tuning Dimensions

Precedential Weight

Weight ranges from illustrative example to binding authority. It should track mandate, hierarchy, jurisdiction, review, publication, and declared status.

Abstraction Level

A narrow holding reduces overreach but may generate artificial distinctions and repeated work. A broad rule transfers efficiently but can outrun the rationale. Generalize only as far as reasons and evidence support.

Similarity Threshold

Broad thresholds invite overmatching; strict thresholds can rationalize inconsistency. Tune by consequence, heterogeneity, and the causal or normative relevance of each fact.

Departure Burden

The burden should rise with authority, reliance, irreversibility, rights impact, and unequal-treatment risk. Low-stakes local learning may need only a documented reason; major doctrinal change may require panel review, notice, transition, and remedy.

Corpus Openness

Open reasons support fair notice and accountability. Confidentiality may protect patients, employees, security, privilege, or trade secrets. The design must preserve controlling reasons and access-equivalent guidance without exposing protected detail.

Update Cadence

High-volume or fast-changing systems require continuous treatment propagation and periodic audit. Low-volume systems may update on decision events, but ownership and invalidation triggers must still be explicit.

Invariants to Preserve

• Check authority and current validity before analogy.
• Tie similarity to material facts and governing rationale.
• Surface adverse, conflicting, limiting, and negative treatment.
• Explain departures through a recognized treatment path.
• Protect fair notice and access to materially relevant guidance.
• Consider reliance without freezing error or injustice.
• Propagate narrowing and overruling to every downstream artifact.
• Keep automated similarity subordinate to accountable judgment.

Target Outcomes

The archetype should produce more consistent treatment, less duplicated reasoning, clearer explanations, earlier detection of stale or conflicting precedent, and more disciplined change. It should improve institutional memory without making history infallible. A successful system can explain both why it followed yesterday and why it changed today.

Tradeoffs

Consistency supports trust and prediction but can entrench error. Narrow precedent protects against overreach but reduces transfer. Open reasons support equality but may conflict with confidentiality. Automation improves retrieval but can reproduce bias and conceal adverse treatment. Each tradeoff requires a governed boundary rather than a universal setting.

Failure Modes

Outcome-Only Precedent

The system copies what happened without preserving why. Require a structured case record and holding boundary.

Surface-Similarity Overmatch

Cases share labels or visible features but differ on the fact that supports the rule. Use rationale-linked comparison and adverse cases.

Selective Citation

Decision makers retrieve only supportive cases. Require adverse search and audit citation coverage.

Precedent Lock-In

Reliance rhetoric makes correction impossible. Establish validity review and an authorized change path.

Stealth Overruling

A decision abandons prior rationale while claiming an immaterial distinction. Apply a departure gate and independent review.

Secret Precedent

Insiders receive guidance and exceptions unavailable to similarly situated parties. Publish controlling rules or access-equivalent anonymized summaries.

Stale Treatment Propagation

Superseded cases remain in tools, caches, or playbooks. Use citation-graph alerts, explicit ownership, invalidation, and audit.

Biased History as Authority

Repeated discrimination is redescribed as consistency. Audit outcomes and rationales, authorize corrective overruling, and address remedy and transition.

Neighbor Distinctions

Dynamic Subproblem Reuse caches useful solutions but does not determine normative authority, reliance, or legitimate departure. Archetype Overmatching Guardrail helps distinguish a precedent but does not govern its authority and lifecycle. Symmetry-Based Fairness tests equal treatment at a point in time; precedent governance creates continuity across time. Deviant Case Analysis refines explanations through anomalies. Alignment Governance resolves present disputes. Emergent Formalization turns stable practice into general rules. Precedent governance connects these activities while case-based reasoning remains necessary.

Cross-Domain Examples

In public-benefit administration, a hardship-waiver precedent register can make exceptions equally discoverable while allowing reasoned distinctions. In platform moderation, authoritative cases and policy versions can reduce team drift. In software operations, incident decisions can be reused with conditions and invalidation triggers. In clinical conferences, prior exceptions can inform discussion without becoming binding rules for different patients.

Non-Examples

Copying a cached calculation is subproblem reuse. Searching a database without checking authority is retrieval. “We have always done it this way” is path dependence, not precedent governance. Repeating a biased historical practice is not consistency. One vivid anecdote does not create an authoritative rule.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

• Analogy: Transfer structure between domains.
• Path Dependence: Outcomes are shaped by the specific historical sequence of past choices, which lock in consequences and foreclose alternatives that persist despite present incentives to change.
• Precedent (Stare Decisis): Past decisions guide future.

Also references 14 related abstractions

• Abstraction: Focus on core elements.
• Accountability: Responsibility for actions.
• Adaptation: Systems adjust to conditions.
• Adjudication (Dispute Resolution): Dispute resolution.
• Collective Memory: Shared narratives.
• Comparison: Place items in a shared frame along chosen dimensions to read off a relation between them.
• Consistency: A set of commitments cannot jointly derive a contradiction.
• Equivalence Relation: Groups elements into equivalence classes.
• Feedback: Outputs influence inputs.
• Formal System: Symbols, formation rules, axioms, and inference rules closed under mechanical derivation.

▸ Show 4 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Legal Stare Decisis Governance · domain variant · recognized

Applies binding and persuasive judicial or administrative precedent through jurisdiction, hierarchy, holding, later treatment, distinguishing, and authorized overruling.

• Distinct from parent: Adds legal source-of-authority, jurisdiction, remedial consequence, and prospective-effect rules.
• Use when: A legal or quasi-legal institution recognizes precedent as a source of authority; Rights, duties, sanctions, remedies, or benefits require fair notice and review.
• Typical domains: courts, administrative adjudication, professional discipline
• Common mechanisms: precedent case brief, precedent authority and validity table, follow distinguish overrule memo

Organizational Decision Precedent · governance variant · recognized

Uses prior approvals, exceptions, sanctions, incidents, and resource decisions to guide comparable organizational cases while governing authority and policy drift.

• Distinct from parent: Emphasizes internal mandates, distributed units, operational speed, confidentiality, and escalation from case precedent to explicit policy.
• Use when: Similar discretionary decisions recur across teams, regions, or professional roles; Unequal exception access or undocumented departures create fairness and coordination risk.
• Typical domains: human resources, procurement, platform moderation, safety operations
• Common mechanisms: precedent case brief, precedent conflict panel, precedent consistency audit

Case-Based Reasoning Governance · implementation variant · recognized

Governs software-assisted retrieval and adaptation of prior cases so similarity does not substitute for authority, causal relevance, validity, or accountable review.

• Distinct from parent: Adds model and data provenance, similarity calibration, adverse-case retrieval, explanation, performance monitoring, and human-override requirements.
• Use when: A system retrieves prior cases to recommend classifications, actions, or explanations; Similarity, adaptation, and outcome feedback can be inspected and audited.
• Typical domains: customer support, claims processing, clinical decision support, software operations
• Common mechanisms: material fact comparison matrix, adverse precedent search protocol, precedent consistency audit

Near names: Stare Decisis, Case-Based Reasoning, Rule by Prior Decision, Precedent Index, Precedent Distinction Memo.

Editorial Notes

Problem Classification

Classification: Authority, Accountability, Legitimacy & Fair-Process Failure → Rules, Rights, Obligations & Consistency

Problem kernel: precedent reasons and constraints do not bind recurrent decisions consistently

Rationale: Recurrent decisions lack a stable, selectively binding rule for carrying authority, rationale, relevant similarity, reliance, and justified exceptions from prior cases into later ones, producing unequal treatment and arbitrary departures. Fair hearing is nearer when affected parties lack voice, impartial judgment, review, or remedy in a dispute; those elements are not necessary to the precedent-continuity problem.

Boundary considered: Authority, Accountability, Legitimacy & Fair-Process Failure → Fair Hearing, Dispute & Remedy Failure

Why this classification prevailed: Rules consistency governs reasoned continuity and exceptions across recurring cases; fair hearing governs evidence, voice, impartial adjudication, review, and remedy for affected parties.

Review outcome: Adjudicated after independent review; high confidence.