> ## Documentation Index > Fetch the complete documentation index at: https://agentconcepts.io/llms.txt > Use this file to discover all available pages before exploring further. # red-herring > A load-bearing distractor: an element placed (or surfacing organically) that the observer takes to be load-bearing, but is not. Structural sibling of chekhov's-gun — looks the same on the surface; the difference is the payoff. business computer-science languages-and-literature law # Red herring ## Description A load-bearing distractor: an element placed (or surfacing organically) that the observer takes to be load-bearing, but isn't. The structural sibling of chekhov's-gun — same surface signal (something positioned for attention), opposite payoff (chekhov's gun fires; red herring doesn't). The concept's diagnostic value is that **the observer's attention is being misdirected** — either deliberately (mystery-novel red herrings, security decoys) or accidentally (debugging the wrong symptom, optimizing the wrong metric). The diagnostic question — *"is this distractor's apparent load-bearing-ness real?"* — runs the load-bearing test on a candidate that's signaling load-bearing-ness. If removing the distractor doesn't change observable outcomes, it's a red herring; if it does, it's a Chekhov's gun. ## Triggers **User-initiated:** User describes attention being drawn to elements that turn out not to matter, debugging-the-wrong-thing, or deliberate misdirection. Vocabulary cues: "red herring," "distractor," "misleading," "rabbit hole," "false lead." **Agent-initiated:** Agent notices that observer attention is concentrated on an element whose actual contribution to outcomes is unclear. Candidate inference: "is this load-bearing or is it a red herring?" **Situation-shape signals:** Stuck debugging sessions. Strategy discussions dominated by an element whose stake is unclear. Post-mortems that conclude "we were looking at the wrong thing." ## Exclusions * **Genuine confusion without misdirection** — when the system itself is opaque and observers can't tell what's load-bearing, "red herring" is too strong a framing; the issue is signal/noise, not deliberate or apparent misdirection. * **Multiple actually-load-bearing elements** — sometimes the distractor IS load-bearing and the perceived-main-thing is ALSO load-bearing; declaring one a red herring forces a frame that doesn't fit. * **Honest blind alleys in research** — pursuing a hypothesis that doesn't pan out isn't a red herring; it's normal exploratory work. The concept requires that the apparent-load-bearing-ness was misleading from the start. ## Structure Internal structure of red-herring: a table of its component slots and the concepts that fill them. ## Relationships Relationship neighborhood of red-herring: a graph of the concepts it connects to and the concepts it is a part of. * [chekhovs-gun](/concepts/chekhovs-gun) — structural sibling; same surface signal, opposite payoff. The load-bearing test distinguishes them. * [cargo-cult](/concepts/cargo-cult) — red-herring is cargo-cult at observer-attention level: surface signal of load-bearing without underlying mechanism. * [load-bearing](/concepts/load-bearing) — red-herring is the deliberate-false-positive on the load-bearing test; identifying red herrings IS the load-bearing-test discipline. * [doctrine](/concepts/doctrine) — debugging doctrines exist to combat red herrings ("start at the actual error, not the visible symptom"). ## Examples Mystery / detective fiction tradition: Agatha Christie's deliberate red herrings are the canonical literary examples. debugger time spent on the wrong line; the real bug is several layers down. Parkinson's law of triviality: discussing trivial elements (the bike-shed color) more than important ones; the trivial details become attention red herrings. false-positive load-bearing data; misdirects the case. canonical literary case; misdirects reader attention. deliberate red herrings to draw attackers away from real targets. The TV Tropes "Red Herring" page collects the trope's literary usage — load-bearing-looking elements deliberately placed by an author to misdirect the audience's attention. The term's etymology traces to 18th-century fox hunting, where strongly-scented smoked herrings were reportedly used to throw hounds off a trail; the structural shape — *load-bearing-looking element that does not in fact bear load* — is the diagnostic the trope crystallizes. The portability is wide. In debugging, the visible error is often a *symptom* whose actual cause lies elsewhere; chasing the symptom is the debugging red herring (debugging doctrine: "start at the actual error, not the visible symptom"). In security, honeypots and decoy networks are *deliberate* red herrings — they look like real targets to attackers but are not load-bearing for the system. In product analytics, vanity metrics (raw signups, raw pageviews) look like progress signals but often don't correlate with the load-bearing outcomes (retention, revenue). And Parkinson's law of triviality — "bike-shedding" — describes attention concentrating on the easy-to-discuss-but-low-stakes element while the load-bearing decision passes without scrutiny. **Inference**: When attention is concentrated on a candidate element, run the load-bearing test ("if this element were removed, would outcomes change?") before deepening the investigation; the load-bearing-looking element may be a red herring. page views look load-bearing for business outcomes; revenue-correlated metrics actually are.