Reusable Decision Precedent¶
Decision-reuse practice — instantiates Strategic Caching
Records a prior ruling and the reasoning behind it so structurally similar cases can be decided by reference — bounded by scope conditions and review triggers, and always subordinate to the governing authority.
A reusable decision precedent caches a completed judgment and its rationale — the facts, the ruling, and the reasoning that connected them — so that a later case with the same structure can be decided by reference to it instead of adjudicated from scratch. Its defining move is caching how a hard call was made and why: the reasoning is reused, not merely the outcome, so future deciders understand the ruling well enough to know when it applies. And it is deliberately subordinate — a precedent guides a new decision but must never quietly become the authority in place of the governing rule it was derived from.
Example¶
An insurer's claims adjusters keep hitting the same edge case: whether water damage from one particular appliance-failure mode is covered under a common policy form. The first time it lands, a senior adjuster rules on it, then writes down the facts, the decision, and the reasoning grounded in the policy language, and files it as a precedent with explicit scope conditions — "applies to policy form X, this failure mode, losses under $Y" — and a review trigger: "revisit if the policy wording changes."
Later adjusters facing a matching case now decide it in minutes by reference, and — crucially — they decide it the same way the senior adjuster would have. Cases that differ in a material way are escalated rather than forced onto the precedent. Illustratively, consistency across the team rises and senior attention is reserved for genuinely novel calls. When legal later updates the policy form, the review trigger fires and the precedent is re-examined before it can mislead anyone.
How it works¶
- Record judgment and rationale. Capture not just the outcome but the reasoning and the facts that drove it, so a future decider can tell whether their case truly matches.
- State scope conditions. Name explicitly the case features under which the precedent applies — the guard against overreach.
- Stay subordinate to the source of truth. Tie the precedent to the governing rule or policy it interprets, so it remains a reading of authority, not authority itself.
- Set review triggers. Name the events — a rule change, a reversal, observed drift — that require the precedent to be revisited or retired.
Tuning parameters¶
- Scope breadth — how widely the precedent is stated to apply. Broad scope yields more reuse but more overreach risk.
- Bindingness — advisory guidance versus mandatory rule. More binding buys consistency at the cost of case-by-case judgment.
- Review-trigger sensitivity — how readily a precedent is flagged for re-examination. Sensitive triggers catch drift early but churn the corpus.
- Precedent-set size — how many precedents are maintained before the collection itself becomes hard to search and reconcile.
When it helps, and when it misleads¶
Its strength is consistent, fast handling of recurring hard calls with the reasoning preserved, so future deciders apply the ruling knowingly rather than mechanically.
Its failure modes are a precedent applied outside its real scope, and the shadow-source-of-truth drift in which the convenient precedent gradually displaces the governing rule it was supposed to serve (the archetype's central warning). The classic misuse is citing a precedent whose facts differ in a way that matters — exactly the failure that legal practice guards against by distinguishing a case.[n1] The discipline is to state scope conditions plainly, keep every precedent tied to its source of truth, and honor review triggers so a stale ruling is retired rather than compounded across every case that cites it.
How it implements the components¶
cache_item_selection— choosing which decisions recur with enough structural similarity to be worth recording as precedent.source_of_truth_reference— tying each precedent to the governing rule it interprets, keeping it a subordinate reading rather than the authority.invalidation_rule— review triggers (rule change, reversal, drift) that require a precedent to be revisited or retired.
It stores a decided judgment to guide a new ruling; it does not pre-authorize an action within fixed limits and route out-of-scope requests onward — that standing permission, with its fallback_retrieval_path, is Cached Approval — and it is a completed decision, not a readable how-to answer scored by reuse_value_model, which is Knowledge-Base FAQ's.
Related¶
- Instantiates: Strategic Caching — the judgment instance: a prior decision and its rationale cached for reuse, governed by scope and review.
- Sibling mechanisms: Web Cache · Memoization · Knowledge-Base FAQ · Local Inventory Cache · Prepared Template Library · Cached Approval
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Reusable Decision Precedent operates as a persistent ledger, log, register, or case record that preserves history and traceability because it records a prior ruling and the reasoning behind it so structurally similar cases can be decided by reference — bounded by scope conditions and review triggers, and always subordinate to the governing authority.
Independent corroboration: The frozen evidence defines Reusable Decision Precedent as 'Records a prior ruling and the reasoning behind it so structurally similar cases can be decided by reference — bounded by scope conditions and review triggers, and always subordinate to the governing authority', so its operative form is Record, Log & Register.
Nearest alternative: Rule, Policy & Commitment — Reusable Decision Precedent includes features of a standing rule, threshold, contractual commitment, or policy constraint governing future conduct, but its defining operation is a persistent ledger, log, register, or case record that preserves history and traceability.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Reasoned precedent applied to structurally similar later cases is a canonical legal decision mechanism.
Related originating lineages:
- Organizational & Management Science — Institutional decision logs materially adapt precedent with scope and review triggers.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: records a prior ruling and the reasoning behind it so structurally similar cases can be decided by reference — bounded by scope conditions and review triggers, and always….
Review resolution: Both blind reviewers agree that law_governance is the primary historical origin. Explicit reconciliation of alternate origin disagreement starts from reviewer_a’s mechanism-specific evidence: Reasoned precedent applied to structurally similar later cases is a canonical legal decision mechanism. Reviewer A proposed alternates=organizational_management, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false; reviewer B proposed alternates=public_administration_policy, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=false. The final record retains every independently supported alternate from either review (organizational_management, public_administration_policy) without an arbitrary cap, selects origin_mode=single_lineage to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=false from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Precedent's nearest twin is Cached Approval, and the two are easily blurred because both live in governance. The separator is what is cached: a precedent caches a judgment and its reasoning to help decide a similar case, subordinate to a governing rule; a cached approval caches a standing permission to act within fixed limits, with an escalation path for anything outside them. A precedent tells you how to decide; a cached approval tells you that you may proceed.
[n1] Stare decisis — the common-law doctrine of deciding like cases alike by following prior rulings. It pairs with distinguishing: showing that a new case differs materially from the precedent so the precedent does not control. That pairing is the built-in guard against applying a cached judgment outside its real scope. ↩