TTMT Docs

Appearance

Reading Oracle ​

Once Oracle is enabled, it leaves a mark on every trade it grades. Rather than a single screen, Oracle surfaces its verdict wherever you already look at trades — so you can see, at a glance, what it thought of a setup and whether it acted. This page walks the places Oracle appears and how to read what it says.

Limited preview

Oracle is in limited preview and is enabled per account on request. Availability, behavior, and naming may change before general release. Contact support if you'd like to take part.

Reading a verdict ​

Every trade Oracle grades gets a verdict — its judgment of the setup at the moment the trade would run. A verdict has two parts:

  • A grade — how good Oracle judged the setup, from strong to poor.
  • A reason — the plain-language "why" behind the grade, so you're never left guessing (for example, that the stop was unusually tight for this channel, or that price had already run far past the entry).

In advisory mode a verdict is informational — the trade ran regardless, and the grade tells you what Oracle would have done. In guardian mode a poor verdict means Oracle held the trade: no position opened, and the row is marked as held with Oracle's reason.

Where Oracle appears ​

On the dashboard ​

Your dashboard surfaces Oracle at a summary level — how many recent trades it graded, how many it flagged or held, and a running sense of whether its calls have been helping. It's the quick pulse; drill into a specific trade for the detail.

In the Trade Log ​

The Trade Log shows an Oracle indicator on each row it graded, so you can scan a whole day's trades and spot the ones Oracle rated poorly. Trades that Oracle held in guardian mode appear with their own outcome so you can tell them apart from trades that ran and lost — a held trade never risked capital.

In the trade modal ​

Open any trade and the trade detail modal carries Oracle's full verdict for that trade: the grade, the reason, and — where relevant — what the trade did afterwards so you can judge the call for yourself. This is the best place to understand a single verdict in context alongside the signal, orders, and journey of that trade.

In replay ​

When you replay a trade to see how it unfolded, Oracle's verdict rides along, anchored to the moment the trade would have run. Replay is where a verdict becomes concrete: you can watch how price moved after Oracle called the setup strong or poor, and build your own trust in its judgment.

On the performance surface ​

Oracle keeps score of itself. The Oracle performance view aggregates its verdicts over a period so you can answer the question that matters: is Oracle's judgment actually helping? It shows how the trades it rated well did versus the ones it rated poorly, and — in guardian mode — how the trades it held would have turned out. Use this before you tighten strictness or move from advisory to guardian.

On profiles ​

Because Oracle can be tuned per config profile, its behavior and results show up where you manage those profiles — so you can see how it's performing for a specific channel and adjust that profile's Oracle mode, strictness, or zone behavior without touching your account default.

Reading Oracle's "savings" ​

Oracle reports a savings figure — its estimate of what its verdicts spared you. It's built from the trades Oracle rated poorly (or, in guardian mode, held) and how those trades actually turned out: when a setup Oracle warned about went on to lose, that avoided or flagged loss counts toward savings.

Savings is a running estimate, not a guarantee

Savings is a look-back tally, not a promise of future results. It measures how Oracle's poor-rated trades behaved, so it moves as more trades close. Oracle will sometimes flag a trade that would have won — that's the cost of a selective filter — so read savings alongside the performance surface to see the full picture, not in isolation.