How it works

Ask → Record → Monitor →
Detect change → Alert →
Retrieve → Continue

This model sits underneath every command Scout supports. Once it clicks, the rest of the product makes sense.

01

Tell Scout what matters

You give Scout a market, condition, level, zone, setup, or preference — in plain language or a command.

You say — "watch for a breakout entry on ETH above the range high, stop below 2400"
02

Scout builds the context

Scout structures the request around the relevant market information — turning it into a trade-plan monitor, not a vague note.

Scout does — parses entry, stop, and structure condition into a tracked trade-plan monitor
03

Scout keeps watching

The condition remains monitored instead of disappearing after one interaction. You don't need to ask again.

State — ETH breakout monitor, active and unattended
04

Something changes

The monitored market condition changes — price breaks the range, a zone gets tested, structure shifts.

Event — ETH breaks above range high, displacement confirmed
05

Scout tells you what matters, and why

Scout surfaces the relevant event and explains the context behind it — not just that price moved.

Scout says — "ETH broke above your range high with confirmed displacement. Stop remains below 2400."
After the alert

Retrieve and continue

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 askScout 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
04
Trade lifecycle

IGNORE → WAIT → WATCH → TRADE

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.

IGNORE

Not currently relevant

The market or setup doesn't meet the conditions that make it worth acting on right now. No action required.

WAIT

Interesting, not actionable yet

Something's potentially relevant, but confirmation is missing. Scout explains exactly what's missing — e.g. "structure is interesting, but confirmation is missing."

WATCH

A condition you asked Scout to track

You've identified something specific — "watch BTC for a break above 105,000" — and Scout monitors it persistently.

TRADE

Setup requirements are met

The current market state satisfies the relevant setup logic and is actionable. This does not mean guaranteed profit.

The loop isn't linear

States move in both directions

The exact transitions follow what Scout actually observes in the market — not a fixed script. A few examples:

TransitionWhat it means
IGNORE → WAITA previously irrelevant market becomes interesting
WAIT → TRADEThe missing confirmation occurs
WAIT → WATCHYou ask Scout to monitor the missing condition
WATCH → TRADEThe monitored condition triggers and becomes actionable
WATCH → WAITThe condition changes or readiness is lost
TRADE → WAITThe setup is no longer entry-ready
TRADE → IGNOREThe underlying thesis becomes invalid
WATCH → IGNOREThe monitored thesis becomes invalid or irrelevant

See every way to describe a condition to Scout.

Explore the full How-To Guides →