---
url: /oracle/modes-and-strictness.md
description: >-
  How to configure Oracle — pick a mode (off, advisory, or guardian; Settings
  says Off, Watch only, or Block doubtful signals), set how strict it is, choose
  how it treats price relative to the entry zone, and override any of it per
  preset.
---

# Oracle Modes & Strictness

Oracle has three dials you control: **mode** (how forcefully it acts on a verdict), **strictness** (how much of the riskiest signals it holds back), and **entry zone** (how it treats where price is relative to the entry zone). You set them once for the account and can override them per [preset](/presets/) for individual channels.

## Where to set them

* **Settings › Signal checks** (in the **Entries & exits** group, Full view). The Oracle controls sit under the heading **Oracle (second opinion on each signal)**: **What the Oracle does**, **How strict it is**, **Judge the entry from**, and **Tell me when it blocks a signal** (Oracle page: **Notify when blocked**).
* **The Oracle page** (`/dashboard/oracle`). It has the same account-level controls, as cards named **Mode**, **Strictness**, **Zone entry point** and **Notify when blocked**, and links back to the Settings row.
* **A preset**, in Settings › Presets, for the first three controls only (see [Overriding Oracle per preset](#overriding-oracle-per-preset)).

::: info Two names for the same modes
The Oracle page and most of the app call the modes **Off / Advisory / Guardian**. Settings calls them **Off / Watch only / Block doubtful signals**. They are the same three settings: **Watch only** is Advisory, and **Block doubtful signals** is Guardian. This section uses Advisory and Guardian. On a Settings step, look for the Settings wording.

On the Oracle page, choosing Guardian asks you to confirm first (**Enable Guardian mode?**, with **Cancel** and **Enable Guardian**).
:::

::: info 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.
:::

## Mode — what Oracle does with its verdict

The mode decides whether Oracle only speaks up or actually intervenes. Start at the top and move down only once you trust what you're seeing.

| Mode | What happens | Trades run? |
|:---|:---|:---|
| **Off** | Oracle does not evaluate your trades at all. No verdicts, no warnings. | All trades run as normal |
| **Advisory** (Settings: **Watch only**) | Oracle grades every trade and shows you its verdict across your logs and trade screens, but never blocks. This is the "watch first" mode. | All trades run; you just see the grade |
| **Guardian** (Settings: **Block doubtful signals**) | Oracle grades every trade and **holds back** the ones it judges poor. A held trade never opens a position; it's logged with Oracle's reason. | Only trades that clear Oracle's bar run |

::: tip Always start in Advisory
Advisory mode lets Oracle grade real trades without changing a single outcome. Run it for a while, compare its verdicts against what actually happened on the [performance surface](/oracle/reading-oracle#oracle-performance), and only switch to Guardian once you're comfortable letting it hold trades. You can drop back to Advisory or Off at any time.
:::

## Strictness — how much Oracle blocks

Within Advisory or Guardian mode, **strictness** sets the share of the riskiest signals Oracle holds back. It doesn't change *what* Oracle measures, only how many of the riskiest signals count as too risky.

| Strictness | Behavior | Best for |
|:---|:---|:---|
| **Lenient** | About the riskiest 5% of signals (the Oracle page shows **Lenient (~5%)**). Most trades pass. | Channels you already trust; you want a light safety net |
| **Balanced** | About 10% (**Balanced (~10%)**). The recommended setting. | Most traders start here |
| **Strict** | About 15% (**Strict (~15%)**). More blocks, including some winners. | Noisy channels, or when you want Oracle to be selective |

In Guardian mode, stricter settings mean **more trades held back**. In Advisory mode, strictness only changes how many trades get a warning label — nothing is blocked either way. Settings shows the plain names Lenient, Balanced and Strict, without the percentages.

```mermaid
flowchart LR
    A[Signal becomes a trade] --> B{Oracle mode}
    B -- Off --> R[Trade runs]
    B -- Advisory --> G[Grade the trade]
    B -- Guardian --> G
    G --> S{In the riskiest share?}
    S -- Advisory, any grade --> R
    S -- Guardian, yes --> R
    S -- Guardian, no --> H[Trade held, logged with reason]

    style A fill:#023e8a,stroke:#0096c7,color:#e6f6ff
    style R fill:#0d4f3c,stroke:#36d399,color:#d6fff0
    style H fill:#5e1620,stroke:#ed3c50,color:#ffe1e4
    style G fill:#0077b6,stroke:#48cae4,color:#caf0f8
    style B fill:#03045e,stroke:#48cae4,color:#caf0f8
    style S fill:#03045e,stroke:#48cae4,color:#caf0f8
```

*Illustrative — advisory always lets the trade run and only labels it; guardian holds a trade only when it falls in the riskiest share set by strictness.*

## Entry zone — how Oracle treats price vs the entry zone

Where price sits relative to the signal's entry zone changes how a trade is likely to fill and how much room it has. Oracle's zone setting tells it which edge of the signal's entry zone to compare the price with when it grades a trade.

| Setting | How Oracle treats it |
|:---|:---|
| **Near edge** | Rewards setups where price is close to the entry — the trade is likely to fill promptly and near plan. |
| **Middle** | A balanced middle ground between prompt fills and deeper, better-priced entries. |
| **Far edge** | Tolerates setups where price is further from the entry, giving retracement-style entries more credit. |

Settings calls this **Judge the entry from**, with **Near edge / Middle / Far edge**. The Oracle page calls it **Zone entry point**, with **Near edge / Midpoint / Far edge**. **Midpoint** is the same choice as Settings' **Middle**.

Match this to how the channel actually behaves. A channel whose signals are meant to be entered immediately fits **Near edge**; a channel that expects you to wait for a pullback fits **Far edge**.

## Overriding Oracle per preset

Oracle's mode, strictness, and entry zone are part of your effective settings, so they follow the same [two-layer model](/presets/) as the rest of your configuration:

1. **Your account-level Oracle settings** are the baseline.
2. **A preset's Oracle overrides** apply to the channels using that preset. Mode, strictness and entry zone can be overridden per preset. **Tell me when it blocks a signal** (Oracle page: **Notify when blocked**) cannot: it is an account-level switch only. A preset row you leave alone shows the account value ("Account: {value}") and follows it.

This lets you run Oracle differently per channel — for example, Guardian + Strict on a noisy channel you don't fully trust, Advisory + Lenient on a proven one — without touching your account default. See [Presets](/presets/) for how preset changes work in general.

::: warning Oracle grades new trades, not open ones
Changing your Oracle mode or strictness affects how **future** trades are graded. It does not re-judge or close trades that are already open — a trade that Oracle let run stays running.
:::

## Related pages

* [Oracle](/oracle/) — what Oracle is and how to request access
* [Reading Oracle](/oracle/reading-oracle) — where Oracle's verdicts appear and how to read them
* [Presets](/presets/) — per-channel setting changes, including Oracle
* [Applying Presets](/presets/applying-presets) — assigning a preset to a channel
