Precedent Index¶
Artifact — instantiates Dynamic Subproblem Reuse
Connects recurring issue patterns to their stored resolutions and, before reuse, runs a fit check on jurisdiction, facts, and context so only genuinely matching precedents are applied.
Precedent Index connects recurring issue patterns to their previously-worked resolutions — but its defining trait is that it matches fuzzily, and therefore must validate fit before it reuses anything. A new situation is never bit-for-bit identical to a past one, so the index cannot simply look an answer up; it must judge whether a candidate precedent is close enough on the dimensions that matter, note how it must be adapted, and record who keeps the whole collection current and trustworthy. That fit judgment is the heart of the mechanism. A precedent index without it is just a document archive; the check — jurisdiction, facts, currency, context — is what turns retrieval into responsible reuse.
Example¶
A litigation team keeps facing the same recurring motions — motions to compel arbitration in employment disputes among them. Their Precedent Index maps that issue pattern to a shelf of past briefs and argument modules that resolved it before. When a new matter arrives, an associate does not paste the old brief; the index's fit check runs first. Is this the same controlling jurisdiction? Is the governing statute still in the version the precedent relied on, or was it amended? Are the facts — an at-will handbook clause versus a signed standalone agreement — analogous or distinguishable? Is the anchor case still good law, or has it been overruled or narrowed on appeal? Only precedents that clear those gates are pulled, and each comes with an adaptation note telling the associate how to distinguish the opposing party's facts and where the prior reasoning must be reshaped. A knowledge-management attorney owns the index — retiring entries when a decision is reversed and adding new ones as issues recur. Reuse here is fast, but never automatic: the check stands between a useful precedent and a citation to law that no longer holds.
How it works¶
- Fit gate before reuse. Every candidate resolution passes an explicit test on the dimensions that decide applicability — jurisdiction, controlling authority, factual analogy, and currency — and a failure on any one blocks reuse rather than discounting it.
- Adaptation, not transplant. A precedent that fits is still reshaped to the present facts; the index records how to distinguish and analogize, so reuse is a reasoned move, not a copy.
- Active stewardship. Because the underlying law and facts drift, a named owner keeps entries current, retires ones that have been overruled, and adds new patterns — without which the index silently rots into a trap.
- Fuzzy by design. Unlike an exact-key store, it expects near-matches, which is precisely why the fit check and the adaptation note are structural rather than optional.
Tuning parameters¶
- Fit-check strictness — how demanding the applicability test is. Strict checks prevent misapplied precedent but reject usable ones and slow the work; loose checks reuse widely but let poorly-matched authority through.
- Match dimensions — which axes the fit check weighs (jurisdiction, statute version, fact pattern, date, procedural posture). Adding dimensions raises precision but makes every reuse more laborious.
- Currency cadence — how often entries are re-verified against new rulings; the gap between reviews sets how long a quietly-overruled precedent can sit live.
- Adaptation latitude — how far a precedent may be stretched to a new context before it must be re-worked from scratch rather than adapted.
When it helps, and when it misleads¶
Its strength is that it makes accumulated institutional reasoning reusable without discarding judgment: recurring issues get answered faster and more consistently, and the fit check keeps that speed from becoming recklessness by forcing an explicit applicability test each time.
Its failure mode is overfitting to precedent — treating a stored resolution as universally valid and reasoning by superficial resemblance past the point where the facts or the law have moved.[n1] The classic misuse is a slack fit check that waves through a precedent from the wrong jurisdiction or a since-amended statute, lending a stale answer the authority of settled practice. The guard is to make the fit check a real gate rather than a formality, to keep currency review active through a named owner, and to require an adaptation note that states plainly why this precedent governs this situation.
How it implements the components¶
fit_validation_rule— the applicability test on jurisdiction, facts, authority, and currency is the index's defining gate before any reuse.adaptation_note— for each reused precedent, the recorded reasoning for distinguishing and analogizing it to the present matter.ownership_and_maintenance_role— the named steward who keeps entries current, retires overruled ones, and adds new patterns.
Unlike its fellow artifact the Dynamic Programming Table, which stores each answer under an exact state_representation key that matches or doesn't, the precedent index matches fuzzily — which is why its defining work is the fit check, not the memoized_solution lookup or the reuse_key the table indexes by.
Related¶
- Instantiates: Dynamic Subproblem Reuse — it reuses stored resolutions for recurring issue patterns under an explicit fit test.
- Sibling mechanisms: Dynamic Programming Table · Reusable Playbook Library · Modular Planning Template · Memoization Cache · Dynamic Programming Method · Recurrence Equation · Cache Invalidation Review
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: The mechanism maintains an actively stewarded index of actual precedents, stored resolutions, fit conditions, currency, and retirement history.
Nearest alternative: Representation, Specification & Plan — It is a reference, but its value depends on maintained provenance and evolving historical entries.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Indexing recurring issues to prior resolutions originates in legal digest and precedent practice.
Related originating lineages:
- Computer Science & Software Engineering — Computer science contributes dynamic reuse and context-fit checks in a searchable tool.
- Library & Information Science — Library and information science contributes classification and retrieval.
Review resolution: Both blind reviewers agree that law governance is the primary origin. Reconciliation resolves alternate origin disagreement, domain reach disagreement. Formative alternate lineages are retained as computer_science, library_information_science; later breadth of use is recorded separately as domain_reach=multi_domain, while origin_mode=cross_disciplinary_synthesis describes the relationship among origin lineages.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The precedent index and its sibling the Reusable Playbook Library both reuse stored answers for recurring situations, but they draw the line differently: the playbook library keys and curates ready-to-run modules and trusts curation to keep them apt, while the precedent index makes the fit judgment itself the mechanism — every reuse must pass an applicability gate. When mismatched application is dangerous rather than merely inefficient, the fit check is worth the friction.
[n1] Stare decisis — the doctrine of standing by decided cases — makes precedent reusable, while the countervailing practice of distinguishing a case (showing its facts differ materially) is the safety valve. A precedent index operationalizes both: the fit check decides whether stare decisis applies or the case must be distinguished. ↩