> For the complete documentation index, see [llms.txt](https://www.degenbot.wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.degenbot.wiki/understanding-alerts.md).

# Understanding alerts

Read directional alerts, compare the three streams, and understand outcome updates.

An alert is a timestamped observation under a particular method. Its meaning depends on the market, direction, timing, conditions, and outcome rule—not only the headline.

Begin with [Read an alert](/understanding-alerts/read-an-alert.md), then open the page matching the stream in your message.

| Stream                                                          | Reading guide                                                                            |
| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| [1m LONG+SHORT](/understanding-alerts/one-minute-long-short.md) | Understand short-term direction without assuming a one-minute expiry or alert frequency. |
| [Fast Move](/understanding-alerts/fast-move.md)                 | Distinguish an early observation from a move already underway.                           |
| [Consensus](/understanding-alerts/consensus.md)                 | Understand agreement without treating it as certainty.                                   |

Reported version names include **Fast Move v3.2** and **Consensus v4**. They identify methods, not a performance ranking or a guarantee those versions remain deployed. Use the version shown in the actual report.

Read [Outcomes and expiry](/understanding-alerts/outcomes-and-expiry.md) to understand success, failure, ambiguous data, and timeouts. Then practise with [Worked examples](/everyday-use/worked-examples.md).

A notification does not require action. Observing, asking for clarification, or skipping a stale message are valid responses.