Screen firings
A rule matched: which symbol, which condition, at what price. Once per event rather than once per poll, with a per-symbol cooldown.
Delivery
Every alerting product is one week from being muted. The threshold, the cooldown and the deliberate absence of a "buy" button are what keep this one useful.
A rule matched: which symbol, which condition, at what price. Once per event rather than once per poll, with a per-symbol cooldown.
A re-check on a position or a candidate that concluded something has changed — with the reasoning, not just a direction.
The flow stopping is itself an alert. Two days of silent model-provider failures is the reason this exists.
Ask for your signals, pause a watch, check status. The bot is a read-and-control surface, and it is deliberately not an order entry surface.
Not everything a screen finds is worth a notification. A minimum strength is applied before anything is pushed, so the channel carries the ones you would want woken for.
A condition that stays true for six hours is one event, not six hours of messages. This is enforced where the firing is recorded, so the history and the channel agree on what happened.
An analysis that reaches your phone cost a model call. The daily ceiling is checked before the turn runs rather than after, so a noisy day cannot quietly become an expensive one.
No. You can pause things, read things and ask things. An order needs a confirmation in a place with the full context in front of you, which a chat message is not.
Raise the threshold, lengthen the cooldown, or pause the schedule. All three are one command, and pausing keeps the screen and its history.
Yes — one firing, delivered to whichever surfaces you enabled. The history is the single source, so a message and the record cannot disagree.