This model sits underneath every command Scout supports. Once it clicks, the rest of the product makes sense.
You give Scout a market, condition, level, zone, setup, or preference — in plain language or a command.
Scout structures the request around the relevant market information — turning it into a trade-plan monitor, not a vague note.
The condition remains monitored instead of disappearing after one interaction. You don't need to ask again.
The monitored market condition changes — price breaks the range, a zone gets tested, structure shifts.
Scout surfaces the relevant event and explains the context behind it — not just that price moved.
The loop doesn't end at the alert. You can ask what happened, why, or resume something you paused — days or weeks later, stored in a durable database that survives restarts and new sessions.
| You ask | Scout does |
|---|---|
| "What was I watching?" | Retrieves your active watches |
| "What conditions did I ask you to monitor?" | Retrieves the relevant conditions |
| "Why did you alert me?" | Retrieves the recorded event and market context |
| "Resume this setup" | Continues the monitoring workflow — no re-describing it |
This is Scout's decision loop — but it isn't a one-way funnel. The market can move between these states in either direction, and Scout tells you which state you're in and why.
The market or setup doesn't meet the conditions that make it worth acting on right now. No action required.
Something's potentially relevant, but confirmation is missing. Scout explains exactly what's missing — e.g. "structure is interesting, but confirmation is missing."
You've identified something specific — "watch BTC for a break above 105,000" — and Scout monitors it persistently.
The current market state satisfies the relevant setup logic and is actionable. This does not mean guaranteed profit.
The exact transitions follow what Scout actually observes in the market — not a fixed script. A few examples:
| Transition | What it means |
|---|---|
| IGNORE → WAIT | A previously irrelevant market becomes interesting |
| WAIT → TRADE | The missing confirmation occurs |
| WAIT → WATCH | You ask Scout to monitor the missing condition |
| WATCH → TRADE | The monitored condition triggers and becomes actionable |
| WATCH → WAIT | The condition changes or readiness is lost |
| TRADE → WAIT | The setup is no longer entry-ready |
| TRADE → IGNORE | The underlying thesis becomes invalid |
| WATCH → IGNORE | The monitored thesis becomes invalid or irrelevant |
See every way to describe a condition to Scout.
Explore the full How-To Guides →