Solution 03
Stage rollout with query-scoped suppression controls
01 — Root cause addressed
This limits the blast radius created when uncommon query failures meet a rollout reaching hundreds of millions of users within about a week.
02 — Implementation
Release the feature to a monitored traffic slice before general availability, watch specifically for factual advice grounded in satire, jokes, or unreliable user-generated content, and retain query-type suppression controls. Those controls should allow health, humour, satire, or UGC-dependent overview triggers to be narrowed quickly while the underlying retrieval failure is investigated.
03 — Prevention
Define the monitored failure classes and scoped suppression controls before expansion, then widen traffic only after the relevant query groups meet review criteria.
04 — Trade-offs
Staging limits exposure but does not repair retrieval or tone detection. It also delays broad availability and needs operational monitoring. This is the wrong choice as the sole response after a grounding defect is known, because reducing traffic cannot make an unreliable answer correct.