Precedent Matching Workflow¶
Governance workflow — instantiates Nearest-Exemplar Response Reuse
Treats a prior decision as binding guidance so like cases are decided alike — reusing the earlier ruling for consistency, and departing only by formally distinguishing the new case.
A Precedent Matching Workflow reuses a prior case not because the old answer is likely correct but because reusing it is legitimate — it keeps like cases decided alike. Its currency is consistency and defensibility, in the spirit of stare decisis.[n1] The prior decision, its holding, and its stated reasoning are stored as a binding record, and a new case is decided by matching it to the governing precedent. What makes the workflow more than rubber-stamping is its escape hatch: a decision-maker may depart from precedent only by distinguishing the case — showing on the record that a material difference makes the earlier ruling inapplicable. And because a stored decision can carry forward the prejudice of the era that made it, the workflow runs a guardrail over which precedents may bind at all. It reuses for consistency; it distinguishes for exceptions; it screens for taint. It does not measure similarity numerically and it does not rewrite the old remedy.
Example¶
A benefits agency's appeals board is deciding whether a gig worker qualifies for a hardship exemption. Two years ago the board ruled that a rideshare driver in materially the same position did qualify, and wrote down why: irregular income, no employer sick pay, documented medical costs. That ruling is the governing precedent, stored with its holding and reasoning. The board's default is to follow it, so this claimant is treated the same way the earlier one was — the point of the workflow is that two people in the same situation should not get opposite answers depending on who hears the appeal.
The agency's representative argues the cases differ: this claimant had brief employer coverage during the relevant months. The board runs the distinguishing test — is that difference material to the holding, or incidental? It decides the difference is decisive and departs from precedent, recording exactly why so the departure is itself auditable. Separately, a decades-old precedent that turned on the claimant's marital status is flagged by the bias guardrail as resting on a factor the agency no longer treats as legitimate, and is excluded from the set of rulings allowed to bind.
How it works¶
- Locate the governing precedent. Identify the prior decision whose facts and holding control the present case; where several apply, resolve by authority and recency.
- Reuse for consistency. Apply the holding by default, so the new case inherits the earlier reasoning rather than being re-argued from scratch.
- Distinguish to depart. The only legitimate way off the precedent is to show a material difference on the record — an explicit exception probe, not a private change of mind.
- Guard the source. Screen precedents for tainted or discriminatory grounds and bar them from binding, regardless of how "on point" they look.
- Document the rationale so both the reuse and any departure are defensible to an outside reviewer.
Tuning parameters¶
- Binding strength — strict (precedent controls unless overturned) to persuasive (precedent merely informs). Strict binding maximizes consistency but ossifies mistakes; persuasive binding stays flexible but invites arbitrariness.
- Distinguishing threshold — how material a difference must be to justify departure. A low bar lets decision-makers escape any precedent they dislike; a high bar traps the system in bad rulings.
- Precedent hierarchy and recency — which authority wins when precedents conflict, and how fast old ones lose weight.
- Guardrail strictness — how aggressively suspect precedents are quarantined versus retained with caveats.
When it helps, and when it misleads¶
Its strength is legitimacy: consistent, predictable, defensible decisions that treat similar people similarly and constrain individual whim. In contested or public decisions, "we did what we did last time, and here is the ruling" is worth more than a fresh but idiosyncratic judgment.
Its failure mode is bad-case amplification — a wrong or biased precedent, once stored and honored, is reused precisely because it is stored, and its authority compounds each time it binds. Path dependence sets in; the system can ossify around a ruling everyone privately doubts. The classic misuse is citing a precedent to launder a predetermined outcome, reaching for whichever prior case supports the answer already chosen. The guarding discipline is the pairing this workflow is built on: a real distinguishing test that can defeat reuse on the record, a bias guardrail that can strip a precedent of its authority, and periodic review that retires rulings the world has moved past — so consistency does not curdle into fossilization.
How it implements the components¶
stored_exemplar_case— the precedent record: the prior decision with its holding, reasoning, and scope of validity, kept as binding guidance.countercase_and_exception_probe— the distinguishing test that lets a material difference defeat reuse and force a departure on the record.privacy_and_bias_guardrail— screens which precedents may legitimately bind, quarantining rulings built on tainted or discriminatory grounds.
It does not compute a similarity_metric (that's Similarity Search over Case Embeddings) or cast a neighbor_set vote (K-Nearest-Neighbor Case Matcher); it does not fix a fast, coverage-bounded response_reuse_boundary as an operational starting action under time pressure — that's Incident Playbook Lookup, which reuses for speed where this workflow reuses for legitimacy; and it does not adaptation_delta_note-adapt the prior remedy — Case-Based Reasoning System does that.
Related¶
- Instantiates: Nearest-Exemplar Response Reuse — this is the archetype's governance variant, where prior cases carry consistency and legitimacy weight.
- Consumes: Similarity Search over Case Embeddings — to surface candidate precedents from a large body of prior decisions before the human matching begins.
- Sibling mechanisms: Case-Based Reasoning System · K-Nearest-Neighbor Case Matcher · Similarity Search over Case Embeddings · Incident Playbook Lookup · Expert Case Recall Checklist · Case Similarity Rubric · Exemplar Feedback Registry
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Precedent Matching Workflow operates as a repeatable ordered procedure or handoff sequence that coordinates action because it treats a prior decision as binding guidance so like cases are decided alike — reusing the earlier ruling for consistency, and departing only by formally distinguishing the new case.
Independent corroboration: The frozen evidence defines Precedent Matching Workflow as 'Treats a prior decision as binding guidance so like cases are decided alike — reusing the earlier ruling for consistency, and departing only by formally distinguishing the new case', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Applying prior rulings to like cases and departing only through formal distinction is the doctrine of precedent in operational form.
Review resolution: Both blind reviewers agree that law governance is the primary origin. Reconciliation resolves domain reach disagreement. Formative alternate lineages are retained as none; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=single_lineage describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Stare decisis ("to stand by things decided") is the doctrine of following precedent so that like cases are decided alike; departure is legitimate only by overruling or by distinguishing — showing the present case differs materially from the precedent. ↩