DROP ALERT NOTES
Keep the channel quiet at night without muting the market
A hard mute throws away overnight moves. Raise the night floor, route survivors to a quiet lane and keep the log running.
Do not mute the stream at night; change what the night asks of it. The drop stream reports every fall at or above your min_drop, and a hard mute throws away exactly the moves the channel exists for. The better answer is a night policy: a higher floor after hours, a quieter destination for what survives it, and a log that never sleeps. All three run inside the relay you already have.
Why muting is the wrong default
Your night is somebody else's slate. Tennis in another timezone, a basketball league on the other side of the map: the hours your channel wants quiet are the hours whole cards move. A muted alert is not a delayed alert; it is gone, and the morning has no record that it happened.
There is a second cost. A mute edits your data. The dedupe and cooldown rules depend on a complete history of what fired; a night of silence leaves a hole that next month's threshold tuning reads as a quiet market.
Raise the floor, not the walls
The stream takes min_drop as a query parameter, with the documented example at 5 and the floor at 1, as the drop alerts guide sets out, checked 2026-10-23. A night policy can be as simple as a relay that reconnects at 23:00 with a higher value and back at 07:00 with the day value. The 3 percent move still arrives in the log; only the channel stops hearing about it.
Live and prematch arrive on separate streams, so the split costs nothing extra: keep the live floor where it is if your nights cover live cards, and raise only the prematch one, where moves develop over hours and a dawn reading loses little.
Give the survivors a quieter lane
What crosses the night floor still deserves a destination, not a shout. Route after-hours alerts to a low-priority channel that nobody pages from, or buffer them and send one grouped message in the morning. The relay guide keeps the webhook POST off the reading loop with a small queue; the night lane is the same queue with a different webhook at the end.
Keep the lane count small. Day channel, night channel, urgent if you run one: three destinations cover a relay's whole life.
Keep the record running
Whatever the channel does, the log keeps every alert with its fields and the policy that handled it. That record is what makes a night policy honest: a month of logs tells you whether the night floor caught anything you would have acted on, and the answer feeds the next threshold review.
Quiet is a routing decision, not an off switch. The stream keeps its tempo, the channel keeps its silence, and the log keeps the truth.