Skip to main content
business computer-science law medicine-and-health political-science

Precedent

Description

Precedent is the structural shape of deciding the current case by analogy to a prior decided case. In common-law systems, the principle of stare decisis (“to stand by things decided”) makes precedent binding under specific conditions: higher courts’ decisions bind lower courts in the same jurisdiction; courts’ own prior decisions bind themselves absent overruling. The institutional formalization is elaborate — citation, distinguishing, overruling, en-banc reconsideration — but the underlying cognitive move is case-based reasoning by structural similarity. The structural shape is three-part. Prior case: the previously-decided case whose disposition is being invoked. Specific, identifiable, citeable; not a generalization but a particular adjudicated instance. Relevant similarity: the structural shape shared between the prior case and the current one — the legal test, the pattern of facts, the issue being decided. The argument is that the cases are analogous in the load-bearing respects — and the corollary art of distinguishing is showing that a candidate precedent is not actually analogous in the load-bearing respects. Binding force: the strength with which the prior case constrains. Binding (must follow), persuasive (should consider), or illustrative (worth knowing). Precedent has a hierarchy of authority. The cross-domain export lands wherever case-based reasoning by structural similarity is the operating mechanism. Codebases have internal precedent — how something was done last time becomes the default for how it’s done this time, even without explicit policy. Organizations have institutional precedent — how the last instance was handled becomes the template for the next. Medical case conferences explicitly invoke precedent: prior cases inform current diagnosis. Design-pattern reuse in software architecture is precedent operating at the design-decision layer. The deep cross-concept analogy worth naming: precedent and few-shot reasoning are structurally the same concept at different substrates. Few-shot is a small set of in-context examples that establish a pattern, applied to a new case via structural similarity learned by the LLM’s attention. Precedent is a small set of decided cases that establish a pattern, applied to a new case via structural similarity argued by the lawyer. The institutional formalism is dramatically different — citation hierarchies vs. attention layers — but the underlying operation is the same. This is precisely the kind of cross-substrate structural identity worth holding open: precedent and few-shot are strong cross-domain analogues whose deeper consolidation becomes legible once exemplar density on both sides compounds.

Triggers

User-initiated: User is making a current decision and reaching for “how have we / they / I handled this before?” Vocabulary cues: “precedent,” “case law,” “prior,” “on point,” “controlling case,” “we’ve done this before,” “by analogy to,” “first impression.” Agent-initiated: Engine notices the user is treating the current case as novel when in fact it is structurally similar to a previously-decided case in their own history or in widely-known canon. Candidate inference: “is this a first-impression case, or is there precedent? The prior case might constrain or guide this decision.” Situation-shape signals: Decisions framed as novel that are actually analogous-to-prior; absence of citation discipline (“I’m sure we’ve done this before but I can’t remember how”); first-impression cases that are actually distinguishable from precedent that should apply; organizations without institutional memory of prior decisions.

Exclusions

  • First-impression cases — genuinely-novel situations have no precedent; forcing precedent on a first-impression case is category-error. The concept requires there be a structurally-similar prior decision.
  • Distinguishing on the load-bearing axis — sometimes the apparent precedent is not actually analogous in the load-bearing respects; the art is recognizing this. Cited but distinguished precedent is precedent that was considered and found inapplicable.
  • The prior decision was wrong — precedent’s binding force depends on willingness to follow it; sometimes the correct move is overruling rather than following. The concept coexists with overruling-doctrine.
  • Rapid context change — in domains where the underlying context shifts faster than precedent accumulates (frontier AI capability questions, emerging-tech regulation), precedent from even a few years ago may be structurally obsolete.

Structure

Internal structure of precedent: a table of its component slots and the concepts that fill them.

Relationships

Relationship neighborhood of precedent: a graph of the concepts it connects to and the concepts it is a part of.
  • few-shot — cross-domain structural analogue at the LLM substrate; the canonical precedent–few-shot pair that motivates treating cross-substrate analogy as a first-class catalog primitive.
  • doctrine — what precedent accumulates into; doctrine is crystallized precedent.
  • seeding — early precedents seed the shape of the doctrine that follows.
  • reflection — internal precedent (your own past decisions) vs. external precedent (others’ past decisions); same use of past, different source.
  • uniformity-dividend — following precedent extracts uniformity-dividend on decisions; the consistency reduces decision-cost across N similar cases.

Examples

Common-law judicial decisions · law

the canonical instance; Marbury v. Madison (1803) cited for judicial review, Brown v. Board (1954) cited for equal-protection analyses, Miranda v. Arizona (1966) cited for custodial-interrogation doctrine; each case becoming controlling precedent for later analogous fact-patterns.

AI few-shot reasoning · computer-science

a handful of in-context examples establish a pattern that the LLM applies to new instances; the structural analogue of legal precedent.
“how do we handle this error” → look at how the same kind of error is handled in prior code; the prior approach becomes the default for the new code.
software architects choosing the Adapter pattern because a structurally similar interface-mismatch was handled by Adapter in a prior project.
“the last time a country in this position did X, the response was Y”; international relations encoded as informal case-law.
Kolodner’s Case-Based Reasoning is the standard textbook treatment of case-based reasoning (CBR) as a computational paradigm. CBR systems solve new problems by retrieving similar past cases from a case library, adapting their solutions to the new situation, and storing the result as a new case for future use. The four-step CBR cycle — retrieve, reuse, revise, retain — closely tracks the structure of legal precedent and of analogical reasoning more generally, but with explicit computational machinery: indexing schemes for case retrieval, adaptation rules for transferring solutions across surface differences, evaluation methods for revised solutions, and learning algorithms that accumulate the case base over time.Inference: CBR is precedent operationalized as a software architecture, and the operational machinery it makes explicit is what precedent-handling in legal, organizational, and codebase domains usually leaves implicit. The four-step cycle is a usable checklist: retrieve — what prior case(s) does the current situation most resemble?; reuse — what features of the prior solution transfer directly?; revise — what needs adaptation because surface features differ?; retain — what should be stored so the current case becomes precedent for future ones? Most informal precedent-handling failures map onto a missing step in the cycle: organizations that retrieve well but never retain (decisions get re-litigated each time), or that retain well but never revise (every new case inherits exact prior solutions even when surface differences mattered).
physicians presenting current cases by reference to prior published cases or institutional cases; the prior case’s diagnosis and management informs the current case.
“how did we handle the last layoff” / “how did we handle the last security incident” / “how did we handle the last exec departure”; the prior handling becomes the template.
William Blackstone’s Commentaries on the Laws of England, published in four volumes between 1765 and 1769, gave the English common-law tradition its first systematic written treatment. Blackstone’s account of precedent — that judges are bound to follow prior decisions of the same court or of higher courts on materially-similar facts, and that the body of decided cases is the law on which subsequent reasoning rests — codified what had been an unwritten institutional practice. He also made the distinguishing discipline explicit: a precedent governs only when the present case is structurally similar in the load-bearing respects, and showing the cases differ on a material axis is the canonical move for not being bound. The Commentaries shaped legal education and judicial reasoning on both sides of the Atlantic for the next two centuries; Lincoln read it; American law schools used it as a primary text into the 20th century.Inference: An institutional practice can run for centuries on tacit shared discipline before someone writes it down — and writing it down changes the practice. After the Commentaries, distinguishing-from-precedent became a named move that lawyers could explicitly perform and judges could explicitly evaluate, where previously it had been part of the wordless craft of advocacy. The pattern is general: codification is not neutral capture of pre-existing practice; it is a structural intervention that makes the previously-tacit available for argument, critique, and revision. The catalog’s own move — writing down the structural primitives that practitioners use implicitly — is a directly analogous codification, applied to analogical reasoning rather than to common-law adjudication.