Red Herring Filter Checklist¶
Checklist — instantiates Relevance-Substitution Detection and Correction
Screens the moves in a live deliberation for issue-shifting, affective activation, or narrative cues that quietly replace the relevant evidence.
Red Herring Filter Checklist watches a deliberation as it unfolds and screens each move — each argument, objection, anecdote, or reframing — against the one question the group is supposed to be settling. Its target is not a single feeling but the stream of contributions in a live discussion, and its characteristic failure to catch is the diversion: a move that draws attention off the question at issue and onto something adjacent, louder, or easier. The checklist pins the actual question in writing, flags any move that shifts the ground away from it, and asks whether that move is influencing where the group is heading. What makes this mechanism itself is that it is issue-anchored and move-by-move: it does not test whether one cue survives removal, it audits a running conversation for the moment the topic quietly changes underneath everyone.
Example¶
A city council is deciding whether to approve a rezoning application for a mid-rise apartment block: the question is whether the site meets density, traffic, and setback standards. During public comment the debate drifts. One speaker spends five minutes on the developer's involvement in an unrelated lawsuit years ago; another warns that "this is how neighborhoods lose their character"; a council member recounts a vivid story about a different building across town that "everyone hated." The clerk running the Red Herring Filter has the question fixed at the top of the sheet — does this application meet the three published standards? — and tags each move: the lawsuit is a character diversion (issue-shift, not evidence about setbacks), the "character" line is a narrative cue, the cross-town anecdote is a vivid but non-comparable case. None are struck from the record, but each is labeled off-issue and set aside from the standards-based decision. When the vote comes, the council can see that three of the loudest inputs never bore on the actual criteria, and the decision returns to the traffic study and the setback measurements that do.
How it works¶
- Pin the question. The exact matter at issue is written down first, in the group's view, so every later move can be checked against a fixed target rather than a drifting one.
- Screen each move by type. The checklist carries a short taxonomy of diversions — issue-shift, ad hominem, affective activation, narrative/character appeal, anecdote-as-data — and each contribution is tagged against it.
- Audit the influence. For any flagged move, note whether it is actually steering the group's leaning; a red herring that no one is following can be left alone, one that is moving the room is called out.
- Label, don't delete. Diversions are annotated as off-issue and quarantined from the decision basis rather than censored, so the record stays honest and the ruling stays relevant.
Tuning parameters¶
- Taxonomy breadth — how many diversion types the checklist screens for. A rich taxonomy catches subtle shifts but slows a live meeting and invites over-flagging; a short one is fast but misses exotic diversions.
- Flag threshold — how far a move must stray before it is tagged. A low threshold catches early drift but can feel like pedantry; a high one waits until the diversion is obvious.
- Influence gate — whether every off-issue move is labeled or only those actually swaying the group. Labeling all is thorough; labeling only load-bearing ones keeps the intervention proportionate.
- Who holds the sheet — a neutral facilitator versus a participant. A neutral holder is less defensive but adds a role; a participant is cheaper but may weaponize the flags.
When it helps, and when it misleads¶
Its strength is catching the substitution that happens between people rather than inside one head: the slow slide of a meeting off its own question. It operationalizes the old idea of relevance as a norm of argument — the demand that each move actually bear on the point in dispute rather than merely change the subject.[n1] Anchoring to a written question is what makes a diversion visible as a diversion.
Its failure mode is mistaking genuinely relevant context for a red herring. Not every move that broadens the frame is a diversion; sometimes the "off-topic" objection is exactly the reframing that reveals the real question. The classic misuse is procedural silencing — using "that's a red herring" to rule an inconvenient but relevant point out of order, which is itself a diversion. The guarding discipline is to require that a flag name why the move fails to bear on the fixed question, and to allow any participant to contest the question itself rather than only the moves under it.
How it implements the components¶
question_at_issue_record— pinning the exact matter in writing is the anchor every screened move is checked against.update_pathway_audit— the influence step traces whether a flagged diversion is actually moving the group's leaning, not just present in the room.cue_quarantine_or_label— off-issue moves are annotated and set aside from the decision basis rather than deleted.
It does not name the affective cue's grip via psychological_activation_pathway or run the single-cue removal test of a channel_independence_check — that focused affect isolation belongs to Affect–Evidence Split Prompt, its checklist twin.
Related¶
- Instantiates: Relevance-Substitution Detection and Correction — provides the live, move-by-move screen that keeps a deliberation anchored to its own question.
- Sibling mechanisms: Affect–Evidence Split Prompt · Analogy Mapping Table · Question–Evidence Matrix · Decision-Basis Disclosure · Reweighted Update Log · Cue-Validity Audit · Proxy-Relevance Audit · Blinded or Masked Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Red Herring Filter Checklist operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it screens the moves in a live deliberation for issue-shifting, affective activation, or narrative cues that quietly replace the relevant evidence.
Independent corroboration: The frozen evidence defines Red Herring Filter Checklist as 'Screens the moves in a live deliberation for issue-shifting, affective activation, or narrative cues that quietly replace the relevant evidence', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Interface, Display & Cue — Red Herring Filter Checklist includes features of a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Rhetoric
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Red herrings are rhetorical relevance diversions within argumentation practice.
Related originating lineages:
- Philosophy — Informal logic materially formalized relevance fallacies and their diagnosis.
Review resolution: Both blind reviewers agree that rhetoric is the primary origin. Explicit reconciliation of domain reach disagreement adopts reviewer_a's classification because red herrings are rhetorical relevance diversions within argumentation practice. The resulting lineage records alternates=philosophy, origin_mode=cross_disciplinary_synthesis, and domain_reach=universal; these describe formative provenance separately from later applicability.
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¶
[n1] In informal logic, the red herring (a form of ignoratio elenchi, "ignoring the point to be proved") is a move that wins attention by changing the subject rather than by bearing on the question at issue; this checklist is a working test for that fallacy in a live room. ↩