bullshit-detector

# bullshit-detector Separate what's verifiably true from what's hype in any piece of content. ## Workflow **Start at step 1 now. The steps below are the plan** — they are already ordered, and each one says what it needs. There is nothing to work out in advance, and working it out anyway is measurably expensive: across 35 instrumented runs the phase before the first tool call is almost entirely deliberation, 15% of all the thinking a run does, and the single longest uninterrupted block on record — 421 seconds — sits there, before a claim had been read or a search issued. Read step 1, do step 1. **Two modes, and the user picks.** Default is **full** — every step below as written. Run **quick** only when the user asked for speed in this request ("quick check", "rough read", "gut check", "don't spend 20 minutes"); never choose it silently, and when in doubt, run full. Quick cuts **breadth, never depth** — measured on this exact corpus: capping follow-up searches bought no wall time at all and collapsed the confirm rate, because a claim that gets one search stalls at 🟡 on evidence a second search would have settled. So a claim quick mode checks gets the full treatment, and the cuts are three, named at the point each applies below: only the five most consequential incidental claims are checked (the rest are ⚪ not checked), no `coverage-check`, and no hostile-reader section. **Everything else holds — especially the steelman before any ❌, because a fast false accusation is still...