The inbound-reply-clock bake alert paged #alerts for Western Slope because a prospect sent a bare "Thank you so much!" and Clara's closer-skip guard correctly chose not to reply. The clock cannot tell "Clara is down" from "Clara decided on purpose that no reply is owed". Record the suppressing guard durably on the conversation row and exempt the no-reply-is-owed guards from the clock. Observability only: nothing about what Clara sends to customers changes. No feature switch.
Status is DERIVED from each row’s own PR, decision and prod-evidence links by
bin/refresh-tracker reply-clock-silence — never typed. Last refreshed
2026-10-16 20:06Z.
Every row opens: when it was added, why it exists, and the links that prove it. Rows waiting on a human carry a Decide → link straight to the answerable question on the decisions page. Statuses are re-derived from live PR, decision and prod-evidence state by bin/refresh-trackers; nothing here is typed by hand, and merged is not shipped until a prod_evidence permalink says the fix was exercised in production.