Alerts are state transitions, not a duplicate feed. They appear when an entity crosses a meaningful product boundary: a first observation, confirmed acceleration, newly resolved contract or other monitored change.
Alert lifecycle
Transient notifications draw attention for a few seconds, then disappear from the top bar. The notification inbox remains the durable operator record with source, type, score and related entity routes.
Common alert types
- first ticker mention;
- first contract mention;
- gaining attention;
- verified acceleration;
- relationship or identity update.
When a contract is explicit in source text, it should be extracted as its own entity and linked to the same evidence item. The ticker and contract may therefore produce separate but related notifications.
Delivery channels
The in-product inbox is the durable operator record. Telegram is an active downstream delivery channel with separate receipts, retries and public/private routes; it does not run a second analysis system. X publication remains human-reviewed, with the automated outbox held and dry-run until its separate approval, correction, idempotency and kill-switch gates pass.