Setup Criteria
Define the market conditions, symbols, volume context, float/volatility filters, and setup patterns that qualify for review.
Define the setup criteria, risk limits, sizing rules, stop logic, and trade-management preferences XeanVI is allowed to follow before any broker-connected workflow can move forward.
Reviewed by Troy Swartwood, Founder & Software Engineer · Last updated June 28, 2026
The Trading Playbook is the rule blueprint XeanVI follows to scan configured market conditions, apply validation checks, and determine when supported broker-connected routing can be considered.
Define the market conditions, symbols, volume context, float/volatility filters, and setup patterns that qualify for review.
Use AI-assisted context checks to help evaluate whether headlines, filings, or sector momentum support the setup before it can move forward.
Set max risk, stop-loss behavior, and boundaries that automation must respect.
XeanVI can calculate size from the risk settings and stop distance you define.
Define target, stop, and bracket-order preferences so the workflow has clear instructions.
Broker-connected routing can only be considered when playbook rules, validation, risk settings, broker permissions, and account configuration align.
XeanVI does not treat a scan as permission to trade. A setup has to pass through rule, validation, risk, paper-testing, and broker-permission gates before supported routing can be considered.
Your setup criteria define whether a market condition is even eligible for review.
AI-assisted catalyst and context checks help determine whether the setup can move forward.
Position size, stop distance, and max risk settings are calculated from the controls you define.
Paper testing lets you review behavior before using live capital.
Supported routing can only be considered when broker permissions and account configuration are active.
Six example rules showing how criteria, risk settings, routing eligibility, and audit visibility can be layered.
Relative volume above configured threshold.
News/filing/sector context passes AI-assisted validation.
Max risk per trade based on user setting.
Stop-loss distance defines position size.
Only route when broker connection and permissions are active.
Track behavior in dashboard monitoring and audit logs.
Examples are for product explanation only and are not trading recommendations.
Start narrow. Pick one setup you already understand and can describe in a sentence — the conditions that make it eligible, where the stop goes, and what the target looks like. Encode that single setup first instead of trying to capture everything you have ever traded.
From there, add the risk settings that should never be crossed: maximum risk per trade, maximum open positions, and the stop logic that determines size. Then run it in paper mode and watch how often it triggers and how sizing behaves before you change anything. A playbook is meant to be revised — the goal of the first version is simply to make your rules explicit enough that the workflow, and you, can follow them the same way every session.
XeanVI is designed around the opposite idea: automation should be constrained before it acts. The Playbook gives the system strict boundaries, keeping scans, validation, sizing, paper testing, routing eligibility, and audit visibility tied to your rules. It is built to reduce impulsive decisions and keep risk settings explicit before any broker-connected workflow is considered.
Start by defining your playbook, test the behavior in paper mode, then connect a supported broker only when you understand the rules, permissions, and risks.
Continue with feature-level workflow details, broker connection safeguards, and audit visibility notes. You can also visit the XeanVI blog for implementation education.
XeanVI does not provide financial advice or guaranteed results. Trading involves risk, including possible loss of capital. Broker-connected workflows depend on user-defined rules, broker permissions, and account configuration.