Screens
You cannot judge ascreen you did notwrite down
The alert you remember is the one that worked. The forty that did not are the reason the screen is not worth running. Only a kept record tells the difference, so every firing is persisted with what fired and why.
What gets kept, and why each part matters
The firing, with its context
Which symbol, which condition of which screen version, which scheduled run, and the price at the time. The version matters: changing a screen creates a new version rather than editing in place, so a history that spans an edit does not silently mix two different rules.
Once per event, not once per run
Firings are idempotent. A screen that runs every five minutes on an hourly condition sees the same qualifying candle twelve times, and a naive implementation alerts twelve times. Yours alerts once, with a per-symbol cooldown behind it, so the history counts events rather than polls.
Degraded runs are marked, not hidden
If market data stalls and a symbol cannot be evaluated, the run says so. A screen that quietly returns nothing looks exactly like a market with nothing in it — and those two need to look different, because one is a market condition and the other is an outage.
It is what makes a screen improvable
With the record you can ask questions that mean something: how often does this fire, on which symbols, in which regime, and what happened next. Without it, every screen is as good as its most memorable hit, which is how a strategy survives years past the point where it stopped working.
Questions about alert history
How long is it kept?
Firings persist — they are the evidence. Run summaries are pruned on a retention window, because "scanned 40, found 0" from last month is not evidence of anything, while the firing that came out of it is.
Can I get alerts on my phone?
Yes, over Telegram, with a strength threshold so the channel does not become noise. The same firing is in the console either way.
Does an alert do anything by itself?
No. An alert is information. It can start a conversation with the assistant, a research job or a backtest, and any order that eventually comes out of that passes the risk gate like every other.
What if I want to stop one screen without deleting it?
Pause its schedule. The screen, its versions and its history stay. Deleting a screen removes its versions, runs, schedules and alerts together, which is why deletion is deliberately not something the assistant can do.
Start a record tonight
A paper account gets the whole screener, including the history that makes it judgeable.