> 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/everyday-use/worked-examples.md). # Worked examples Practise reading a directional setup, a late fast-move message, and an unresolved outcome. {% hint style="info" %} All messages, prices, times, identifiers, and rules on this page are fictional. They illustrate how to read an alert; they are not live signals, real results, or Degen's confirmed production thresholds. {% endhint %} ### Example 1: an upward scenario ``` TEACHING EXAMPLE — NOT A LIVE ALERT Stream: 1m LONG+SHORT Direction: LONG Instrument: EXAMPLE/USDT, illustrative spot venue Observed: 12:00 UTC Reference: 100.00 Scenario target: 104.00 Invalidation: 98.00 Evaluation deadline: 13:00 UTC Reason: Example upward momentum with supporting volume Rule for this example only: Target must be reached before invalidation and before deadline. ``` The message describes an upward scenario from a reference of 100. It does not open a position. Under this example's rule, reaching 104 first within the window would satisfy the success condition; reaching 98 first would not. The one-minute label is not the same as the example's one-hour evaluation window. The message explicitly states its deadline. Suppose you read the message when the market is already at 102. The distance to 104 is now 2, while the distance to 98 is 4. From the original reference, those distances were 4 and 2. The geometry changed; the old reference is not a price you are guaranteed to receive. ### Example 2: a downward scenario ``` TEACHING EXAMPLE — NOT A LIVE ALERT Direction: SHORT Reference: 200.00 Scenario target: 194.00 Invalidation: 203.00 ``` SHORT describes a downward scenario. In this example, the target is below the reference and invalidation is above it. The labels do not create a short position or tell you to use derivatives. Before interpreting the outcome, you still need the timestamp, evaluation window, venue, and resolution rule. Three prices alone are not a complete alert record. ### Example 3: a move was already underway ``` TEACHING EXAMPLE — NOT A LIVE ALERT Stream: Fast Move Movement observed: 09:58–10:00 UTC Message sent: 10:00:20 UTC Message read: 10:01:00 UTC Price before observed move: 50.00 Price when message was sent: 52.00 ``` This message reports movement that happened before it was sent. It may be useful context, but it does not demonstrate an advance prediction from 50 to 52. The one-minute delay between the event endpoint and reading the message also matters. Do not treat an old reference as a fresh opportunity simply because the notification is new to you. ### Example 4: expiry is not self-explanatory An example observation has a target of 104, invalidation at 98, and a deadline of 13:00 UTC. At the deadline, neither level has been reached. The outcome is an expiry under the example's lifecycle. Whether the performance calculation counts it as unsuccessful, neutral, or excluded depends on the published scoring rule. You cannot choose the treatment after seeing the result. Similarly, if one candle touches both levels and no finer data establishes their order, the candle alone does not prove which outcome came first. **Takeaway:** match direction, price, timing, and the predefined rule. None of them can be replaced by a headline success percentage.