Short answer: give each restaurant menu fact an explicit freshness deadline, reject expired evidence before semantic ranking, and page on freshness-budget burn before the assistant starts answering from an old index. For a campus dining assistant inside an education platform, this is the least complex design that keeps schedule changes visible without rebuilding every embedding on every poll.
The page arrives at 02:13: menu_answer_stale_ratio has crossed the alert threshold for the third evaluation interval. The on-call view shows that retrieval is healthy by its usual measures: requests complete, candidates come back, and the vector index responds. Yet a dining-hall answer still cites yesterday's dinner hours. A green retrieval service can return bad evidence.
That is the operational trap.
The signal that should have fired earlier is not generic latency or an empty-result count. It is the age of the newest eligible source record compared with the freshness budget for that fact class.…