---
url: /dashboard/trade-explainer.md
description: >-
  A plain-English AI story of any closed trade, a graded scorecard, an
  event-by-event Trade Journey, and a chart with your levels drawn on — so you
  can see exactly what TTMT did and why.
---

# AI Trade Explainer

When you open a finished trade, TTMT does more than show you the numbers — it can tell you the whole story. The trade detail screen carries three transparency surfaces that answer "what actually happened here, and why?" in plain language: the **AI Trade Explainer**, which writes a short narrative and a scorecard; the **Trade Journey**, an event-by-event timeline from signal to close; and the **trade chart**, a candlestick view with your entry, stop, and targets drawn straight onto the price. It is not just a log of what filled — it is the engine explaining its own decisions back to you.

::: tip
Open any **closed** trade from the [Trade Log](/dashboard/trade-log), then click **Explain Trade** to read its story. The Journey timeline and chart are already there when the trade opens — no button needed.
:::

## Where to find these — opening a trade

Click any row in the [Trade Log](/dashboard/trade-log), [Position Log](/dashboard/position-log), or [Live View](/dashboard/live-view) to open the trade detail screen. Three of its panels make up the transparency surface:

| Surface | What it shows | Needs a click? |
|---|---|---|
| **AI Trade Explainer** | A plain-English story plus a graded scorecard of the trade | Yes — press **Explain Trade** |
| **Trade Journey** | Every lifecycle event in order, from signal to close | No — always shown |
| **Trade chart** | Candles around the trade with your entry zone, stop, and targets overlaid | No — shown when chart data exists |

## The AI Trade Explainer — your trade in plain English

The Explainer turns everything that happened on a trade into a short, readable story — not a dump of status codes. You trigger it with the **Explain Trade** button, which carries a counter of how many explanations you have left today (for example, **Explain Trade (4 left)**). It only works on **finished** trades — ones that have closed or failed. If a trade is still live, you will see "Only completed or failed trades can be explained"; wait for it to close, then ask again.

The story is written by AI that knows how TTMT's own engine works — your sanitizer, entry zones and layers, take-profit distribution, breakeven and trailing, and your safety systems — so it explains the *why* behind each decision, not just the *what*. It also reads **your** settings for that trade, so the story is specific to how you had things configured. Each explanation is a tight 300–600 words in plain trading language, with no jargon codes.

Every explanation is built from the same set of labelled sections:

| Section | What it tells you |
|---|---|
| **Trade Story** | A short narrative of the trade start to finish, ending with the bottom line — `Final Result: +$48.20` or `Final Result: -$12.60`. |
| **Key Decisions** | The moments that shaped the outcome — which layers filled, where positions moved to other targets, when the stop moved to breakeven. |
| **Non-Standard Moments** | Anything unusual worth your attention, such as a stop that filled a little past its level (slippage). Only appears when there is something to flag. |
| **Your Settings** | The settings that were in force for this trade — lot size, entry strategy, SL/TP defaults — so you can see what drove the behaviour. |
| **Issues** | Real problems, if any — a rejected order, a missing stop, a validation block. Only appears when something actually went wrong. |
| **Final Scorecard** | A short verdict grading how the trade went and pointing at anything you might tune. |

**Example.** You open a closed XAUUSD BUY that ended slightly red. The **Trade Story** explains that the market gave back ground after entry, your deeper layers filled, and a follow-up close from the channel ended it at `Final Result: -$9.40`. **Key Decisions** notes that once the third layer filled, TTMT pulled your earlier layers' targets in to secure profit faster. **Your Settings** shows you were running 0.10 lots with a 4-layer entry. The **Final Scorecard** tells you the trade was managed correctly and the loss was a normal cost of a reversal — nothing to fix.

## How many explanations you get — the daily counter

Generating a story costs real money, so each explanation is **saved** the first time you create it. Re-opening the same trade later shows the saved story instantly and for free — it does not cost you anything from your daily count. Only the *first* generation of each trade counts.

```mermaid
flowchart TD
    A["Click Explain Trade"] --> B{"Already explained<br/>this trade?"}
    B -->|Yes| C["Show the saved story<br/>(instant, free)"]
    B -->|No| D["Write a new story<br/>(uses 1 from today's count)"]
    D --> E["Save it to this trade"]
    E --> C

    style A fill:#023e8a,stroke:#0096c7,color:#e6f6ff
    style B fill:#5a4708,stroke:#e7c000,color:#fff6d6
    style C fill:#0d4f3c,stroke:#36d399,color:#d6fff0
    style D fill:#03045e,stroke:#48cae4,stroke-width:2px,color:#caf0f8
    style E fill:#023e8a,stroke:#0096c7,color:#e6f6ff
```

How it works:

1. **The counter is your daily budget** — the number on the button is how many *new* stories you can generate today. By default you get five per day.
2. **Revisits are free** — opening a trade you have already explained shows the saved story and does not touch your count.
3. **Regenerate when something changed** — if you want a fresh take (for example, after a trade's final outcome was confirmed), you can regenerate the story. A regeneration writes a new story and spends one from your daily count, just like the first time.

::: info
Your saved story keeps the wording it had when you generated it. If TTMT later improves the explanations, your existing stories stay as-is until you regenerate them — so an old story is still the story you read before, not a surprise rewrite.
:::

## When the Explainer flags slippage

One of the most useful things the Explainer does is tell you when a close was **slippage**, not a fault. Your stop-loss and breakeven levels are *trigger* prices, not guaranteed fills — when price hits the trigger, your broker fills at the next available price. On a fast move or a wide-spread broker, that fill can land a little past the level. That is normal broker execution, not a TTMT error, and the Explainer says so plainly in **Non-Standard Moments** rather than letting the trade read like the stop "didn't work".

::: info Example — same stop, two brokers
A single signal was broadcast to two of your accounts. Both moved the stop to breakeven and the platform confirmed it at `4292.09`. On the live account, the broker filled that stop at `4291.76` — about 3 pips past it, a tiny loss. On the demo account, the *identical* stop filled cleanly at `4292.09` for a small profit. Same stop, same instant, two brokers: demo gives idealised fills, the live account slipped. The Explainer flags this as slippage so you don't mistake it for a broken breakeven.
:::

::: tip
If slippage on a slippage-prone broker keeps nudging your breakeven closes slightly red, widen your breakeven buffer so the stop sits a few extra pips in profit before it can be triggered. See [Breakeven Management](/core-concepts/breakeven-management).
:::

## The Trade Journey — every event in order

The **Trade Journey** is a vertical timeline of everything that happened to the trade, in the order it happened. Where the Explainer tells the story, the Journey shows the raw sequence — and you can click any step to jump to the order, position, or signal behind it.

```mermaid
flowchart LR
    A["Signal received"] --> B["Orders placed"]
    B --> C["Layers fill"]
    C --> D["Management<br/>breakeven · trailing · targets shift"]
    D --> E["TP / SL hit"]
    E --> F["Closed"]

    style A fill:#023e8a,stroke:#0096c7,color:#e6f6ff
    style B fill:#03045e,stroke:#48cae4,stroke-width:2px,color:#caf0f8
    style C fill:#03045e,stroke:#48cae4,stroke-width:2px,color:#caf0f8
    style D fill:#5a4708,stroke:#e7c000,color:#fff6d6
    style E fill:#0d4f3c,stroke:#36d399,color:#d6fff0
    style F fill:#0d4f3c,stroke:#36d399,color:#d6fff0
```

Step by step, a typical journey reads:

1. **Signal received** — the channel message TTMT read to build the trade.
2. **Orders placed** — the grid of entry orders across your layers; how many depends on your size and your broker's lot rules, up to 36 in total.
3. **Layers fill** — which orders actually triggered as price moved.
4. **Management** — every protective move while the trade was open: breakeven, trailing stop, and positions re-split across targets as deeper layers filled.
5. **TP / SL hit** — the targets and stops that closed positions.
6. **Closed** — the final event that ended the trade.

## The trade chart — your levels drawn on the candles

The third surface is a candlestick **chart** of the price around your trade, with your **entry zone**, **stop-loss**, **take-profit levels**, and any **modifications** drawn directly onto it. It covers a tight window around the trade's key moments, so you can see at a glance whether price ran straight to target, wicked into your stop, or chopped around your entry. Candle times display in **your local timezone**.

The chart behaves differently depending on whether the trade is still open or already closed.

**On an open trade**, the chart is live. It draws from **one-minute candles**, and where TTMT has live feed data it keeps a **forming bar** updating in real time so you watch price move against your levels as it happens. When an open trade doesn't yet have live candles, TTMT **polls roughly every 45 seconds** to fill the picture in, so the chart catches up shortly after each entry even on a quieter feed.

**On a closed trade**, the chart is the **retained snapshot** captured for the trade — it loads instantly every time you re-open the trade, even months later, long after the broker has rotated those candles out of its own history.

::: info
A few charts carry a **data-quality warning**. Trades that closed before this feature existed, or where only coarser legacy hourly (H1) data was available, may show a structure-only or "suspect legacy data" note — the levels are drawn, but the candles are approximate. A handful show a "no chart context available" placeholder where price data couldn't be fetched. In every case the trade and its Journey are unaffected; only the candle picture is limited.
:::

## Related pages

* [Trade Log](/dashboard/trade-log) — the trade list these three surfaces drill into, and what each end reason means.
* [Position Log](/dashboard/position-log) — the individual positions inside a trade, each with its own lifecycle.
* [Breakeven Management](/core-concepts/breakeven-management) — why a stop can fill a little past its level (slippage) and how the buffer absorbs it.
* [TP Redistribution](/core-concepts/tp-redistribution) — the TP re-split the Journey shows as your deeper layers fill.
* [Annotations](/dashboard/annotations) — add your own notes, ratings, and reflections to a completed trade.
* [Performance](/dashboard/performance) — the account-wide analytics that sit above any single trade.
