VELMONTAIRE product documentation
This is the official product reference for creating a strategy, connecting an account, validating it and moving safely from PAPER to LIVE.
Strategy logic, account rules and execution authority are separate. A strategy does not receive LIVE authority just because it was created successfully.
Recommended setup order
For a new user, follow these steps in this exact order. This avoids configuration being scattered across the workspace.
CORE for building/testing. PRO for Prop + LIVE. ELITE for higher limits.
Personal account, CFD Prop or Futures Prop.
Use credentials for the exact account you want VELMONTAIRE to operate.
Describe → clarify → review → approve an immutable version.
Validate the exact version before runtime use.
Run the production execution path without LIVE authority.
Only after connection, strategy version and safety prerequisites are verified.
Natural language → structured strategy
Write the trading system normally. VELMONTAIRE parses known concepts, fills structured controls and asks for clarification where a rule is ambiguous or missing.
Example: Order Block, FVG, CHOCH, liquidity sweep, RSI or EMA can map directly to existing capabilities.
VELMONTAIRE must ask what makes the condition true. It must not silently guess the meaning.
If you change a confirmed rule later, that should become a new strategy version instead of rewriting historical behavior.
Personal account vs Prop Firm
Select Personal when the account is your own broker account and there are no prop-specific drawdown, consistency or news rules.
Select the firm, program, phase/stage and account size before execution. These rules are account policy and remain separate from strategy logic.
For a prop account
How a user connects the bot to an account
The website does not need the MetaTrader desktop password stored in the browser. The user submits the trading account connection to the server-side broker boundary.
Use the MT5 credentials issued for that exact challenge or funded account. Do not connect a different MT5 account while another prop policy is selected.
Validate the exact strategy version
Backtests should use a specific immutable strategy version plus explicit symbol, timeframe, dates, starting balance, spread, commission and slippage assumptions.
PAPER before LIVE
Runs the guarded runtime path without granting LIVE execution authority. Use it to verify runtime behavior before real money.
Requires explicit authorization and verified prerequisites such as approved strategy version, broker connection and safety state.
The runtime should fail closed if required authorization, connection state or recovery state is uncertain.
What the production safety layer protects
Unknown or invalid state blocks new execution instead of guessing.
State can be restored from durable checkpoints and event history.
The same market input should not advance the same sequence twice.
How to understand CORE, PRO and ELITE
If the user needs a prop account or LIVE execution, PRO is the normal starting plan. ELITE is primarily for higher limits.
Common problems
I was logged out. Is my bot still authorized?
Website session authentication and LIVE execution authority are separate concerns. Re-authenticate to inspect current runtime state.
MT5 test fails
Check the exact login, server spelling and trading password. For a prop account, confirm you are using credentials for the selected challenge/funded account.
My prop firm rules are not shown
Choose the account environment first. If the firm/program is not supported, submit it through the Capability Lab / Support flow rather than guessing policy.
LIVE cannot start
Check strategy approval, verified broker connection, plan entitlement, explicit confirmation and Safety state. LIVE should remain blocked if any prerequisite is unresolved.