Exception Comparator Memo¶
Template — instantiates Governance Exception Management
A single-case template that pulls up materially similar prior approvals and denials and forces the decision-maker to state whether this case follows, distinguishes, narrows, or departs from them — and why.
The Exception Comparator Memo is the artifact that keeps one decision honest against the ones before it. Filled in while a specific exception is being decided, it retrieves the most materially similar prior cases — including adverse ones the decision-maker might rather forget — and requires an explicit choice: follow the precedent, distinguish it on a stated material difference, narrow it, or depart from it with reasons. Its defining move is that it looks backward across the decided population from inside a single live case: it is not a portfolio survey and not the case's own evidence file, but the reasoning bridge that ties this decision to the ones it must be consistent with. A memo that cannot name the closest prior case, or that cites only the favorable ones, has not done its job.
Example¶
A content platform is weighing a policy exception: a journalist wants to keep up a graphic war-crime video that ordinarily violates the graphic-violence rule, invoking a public-interest documentation ground. The reviewer opens an Exception Comparator Memo. It surfaces the four closest prior cases: two comparable public-interest archives that were granted with an age-gate condition, one denied because the footage was gratuitously edited for shock, and one granted then later revoked when it spread as harassment. The template forces the reviewer to place the current case against each: follow the two grants (same documentary purpose), distinguish the shock-edit denial (this upload is unedited), and account for the revocation risk by proposing the same age-gate and a re-review trigger.
The output is a short, reasoned paragraph the decision hangs on: this case follows the archive precedents, is distinguished from the shock-edit denial by X, and adopts the harassment safeguard learned from the revoked case. Anyone later can see not just what was decided but how it sits in the line of like cases.
How it works¶
- Retrieve the nearest cases, including adverse ones. The template deliberately pulls denials and later-revoked grants, not just supportive precedents, to defeat selective citation.
- Force a named disposition per comparator. For each prior case the reviewer must mark follow / distinguish / narrow / depart — no silent omission.
- Require the material difference, not the outcome. Distinguishing must rest on a stated fact that matters, never on "this one feels different."
- Handle confidential precedents by abstraction. Where a prior case is protected, the memo compares abstracted factors rather than exposing the record, so consistency doesn't become secret law.
- Emit a reasoned consistency paragraph. The result is a compact justification that becomes part of the decision's reasoning.
Tuning parameters¶
- Comparator recall breadth — how many and how loosely-matched prior cases are surfaced. Broader recall catches inconvenient precedents but raises reviewer load and noise.
- Adverse-case mandate — how strongly denials and revocations must be included and addressed. Stronger mandates fight cherry-picking but lengthen the memo.
- Distinguishing rigor — how demanding the "material difference" standard is. High rigor prevents pretextual distinctions but can trap genuinely novel cases in old molds.
- Abstraction level for confidential cases — how much a protected precedent is generalized. More abstraction protects privacy but weakens the comparison's bite.
- Precedential weighting — how much binding force prior cases carry versus mere guidance. Heavier weight improves predictability; lighter weight preserves case-by-case fit.
When it helps, and when it misleads¶
Its strength is that it makes "treat like cases alike" operational at the moment of decision, exposing inconsistency and selective reasoning before they harden into unequal treatment. Forcing an explicit follow-or-distinguish is what converts a gut call into a defensible, reviewable line of reasoning.
Its failure mode is false consistency: a reviewer copies the outcome of a prior case without testing whether its facts, authority, or rationale still hold — the form of the memo performed while its substance is skipped.[n1] The classic misuse is treating a superficially similar case as controlling and rubber-stamping its result, freezing a bad early exception into precedent. The guarding discipline is that the memo grades on the quality of the follow/distinguish reasoning, not on outcome-matching, and that adverse comparators are mandatory — an informal self-check that the closest denial was genuinely confronted, not skipped.
How it implements the components¶
exception_comparator_and_consistency_rule— it is the direct instrument of this component: surfacing like cases and requiring explicit follow / distinguish / narrow / depart treatment.reasoned_exception_decision_record— the memo's consistency paragraph becomes part of the decision's recorded reasoning, tying the outcome to the precedents that shaped it.
It does not capture the current case's own facts, claimed ground, or requested scope — that intake is the job of its template twin, the Exception Request and Evidence Dossier's governing_rule_and_exception_mandate, accessible_exception_request_and_evidence_path, and minimum_necessary_scope_and_conditions. The memo consumes the dossier and looks outward at prior cases, not inward at this one.
Related¶
- Instantiates: Governance Exception Management — it supplies the per-case consistency reasoning the lifecycle requires.
- Consumes: Exception Request and Evidence Dossier — it needs the current case's facts before it can compare them to prior ones.
- Sibling mechanisms: Exception Request and Evidence Dossier · Sampled Exception Consistency Audit · Reasoned Waiver or Variance Certificate · Exception Review Panel or Designated Officer
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The mechanism is a single-case template that externalizes comparable precedents, required follow-distinguish-narrow-depart positions, material differences, and a reasoned consistency paragraph.
Nearest alternative: Interface, Display & Cue — Its fields force attention, but the operative form is the persistent structured decision memo rather than a transient user-facing prompt.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Comparing a live case with precedents and stating whether to follow, distinguish, narrow, or depart is canonical common-law reasoning.
Review resolution: Both reviewers agree that law_governance is primary. I retain no additional origin domain only as formative origin lineages; single_lineage is appropriate because the alternate domains informed practice without constituting independent ownership. Reach is multi_domain because the structure transfers across several fields but is not a near-universal human pattern, an applicability judgment kept separate from provenance. Encyclopedia synthesis is true because the exact generalized artifact is an encyclopedia-authored combination or refinement. No unresolved historical ambiguity remains after reconciling the secondary fields.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The memo is a single-case instrument and should not be confused with its retrospective cousin, the Sampled Exception Consistency Audit, which sweeps many decided cases after the fact to detect drift. The memo defends one decision as it is made; the audit judges the whole population later.
[n1] Distinguishing is the common-law technique of showing that a seemingly controlling precedent does not apply because of a material factual difference. Genuine distinguishing enforces consistency; pretextual distinguishing — or blind outcome-copying — produces the false consistency this mechanism guards against. ↩