Skip to content
StatePath
Platform Atlas

One map of the whole platform.

Everything here moves along one line: a signal is found, filtered, shaped into an order, and managed as a live position. From there it branches — prove it in backtests, compile it into a MetaTrader robot or indicator, or sell it on the marketplace. Pick any stop on the map to jump to its section.

Start here

From empty canvas to running robot

Six steps, each one building on the last. The first four are guided lessons with a live practice canvas; the last two happen in the real editors.

Four ways to learn

Choose the door that fits the moment

Lessons

Guided, hands-on tracks with a practice canvas built in. The right door on day one.

Open Learn
Recipes

Copyable starting points for common setups — open one, paste it into an editor, adapt it.

Browse recipes
Reference

Precise, scannable catalogs: every tool, every wire type, every chart pattern.

Tool AtlasData TypesPatterns
Concepts

The ideas underneath: the pipeline, the honesty rules, the version model. Explained on this page.

Jump to concepts

The build line

Four stages, four documents

A strategy is not one file — it is four documents, each authored on its own canvas and validated on its own terms. The composer snaps them together.

  1. Search Signal
    Finds the moment

    Decides buy or sell on every bar. Its exit takes two booleans — raising both emits two independent signals.

  2. Filters
    Guard the gate

    A chain of filter documents interrogates each signal. Every filter answers with one boolean: pass, or stop it here.

  3. Create Order
    Shapes the trade

    Turns a surviving signal into price levels: one or more take-profits, one or more stop-losses, and an optional confidence that scales position size.

  4. Deal Stage
    Manages the position

    After execution: qualification models decide whether a management suggestion is allowed, sizing models decide how big. Prop-firm presets included.

Composition and publishing

The composer references one Search Signal, an ordered filter chain, one Create Order and a Deal Stage configuration. Publishing freezes the whole assembly into a numbered, immutable version — runs and compiles always execute a version, never your live draft.

What a filter can say

Go next
The signal advances to the next state.
Hold
Not yet — try again on the next bar.
Cancel
Discard the signal entirely.

The five filter categories

Inside a state, categories evaluate in a fixed order. Strict families cancel; non-strict families hold.

  1. Data miningObserves and records. Never affects the signal.
  2. StrictAll must pass, or the signal is cancelled.
  3. Strict weightedThe weighted score must reach the threshold, or the signal is cancelled.
  4. Non-strictAt least one must pass, or the signal holds for the next bar.
  5. Non-strict weightedThe weighted score must reach the threshold, or the signal holds.

The instrument

Everything is a node on a canvas

Each stage document is a graph: tool nodes joined by typed wires, flowing into the stage exit. The type system does the safety work for you.

Tools are the atoms

A tool is one unit of computation — an indicator, a comparison, a piece of arithmetic, a drawing. Drop it on the canvas, configure it in the inspector, wire its output onward. Many tools carry modes: one node, several behaviours.

Interpretors turn numbers into meaning

An oscillator gives you a curve; an interpretor reads it and answers a semantic question — overbought? trending? diverging? They are the bridge between raw indicator output and a decision, and the concept newcomers miss most often.

Wires carry types

A connection only forms when the types agree. When they almost agree, the canvas offers an adapter to bridge the gap — so a mistake is caught at drag time, not at run time.

Buffer
A value for every bar — the shape indicators speak.
Scalar
One number for the current evaluation, like a price level.
Boolean
True or false — what exits and conditions consume.
Enum
One choice from a named set.
Multi-enum
Several choices from a named set.
Event list
Discrete happenings with bar positions, like detected patterns.
Bundle
A structured record — tap a single field when you need just one part.

The honesty rule

At decision time a graph cannot read the current bar's close — the engine raises an error if it tries. Repainting tools are re-evaluated bar by bar, seeing only what was known at that moment. What you backtest is what a live terminal would have seen.

Market data

The bars underneath

Every run replays real historical bars. Browse what is available, and study any symbol on the chart workspace with catalog tools overlaid.

The prove line

Backtest, optimize, validate

A published version replays against history. Progress streams live; results are equity curves, trade records and per-node chart series.

The compile lanes

From document to MetaTrader file

Two lanes leave the platform. Both end in a real file you download and drop into a terminal.

Build faster

Shortcuts that stay yours

Three accelerators feed the same pipeline — nothing here bypasses versions, validation or ownership.

The market loop

Sell your work, buy a head start

Strategies, modules, indicators, tools and saved settings can be listed. Every listing passes review before it goes live.

Under the hood

For readers who want the machinery

The corrected deep dive — how the engine actually works today.

The runtime, in one paragraph

Editors produce JSON documents. The composer assembles them; publishing freezes an immutable version stamped with the exact tool versions it was built against. Runs load the version, replay bars through the four stages, and stream progress events. Compiles lower the same graph to MQL source and hand it to the compile service, which returns the finished terminal file.

Entry money management

Four steps between an order and the broker: a gate that can refuse entry, a sizing model, a confidence mapping that scales size by the order's confidence value, and a final risk guard that clamps the result.

Temporal gating

Static time-window rules that block, reduce or force-close; DST-aware market sessions; a news ceasefire around scheduled events; and a live-learning heatmap by day and hour.

Engines and fidelity

Bar-by-bar is fast and coarse; tick-simulated interpolates intra-bar movement; real ticks replays recorded ticks. The vectorized engine runs the signal pipeline sequentially and hands execution to a fast vector backend — deal-stage management requires the reference engine.

Look-ahead and repainting

Inside the decision scope, reading the current bar raises an error — the guard is structural, not advisory. Tools that repaint are re-evaluated under a moving cursor so each bar sees only its own past; assembly flags any repainting tool in the build report.

Journey data

An optional per-signal data bus. The search signal declares the schema; filters and the order stage read and write. A write becomes readable from the next state onward — never within the same state — so information always flows forward.

Drafts and versions

Every document family keeps one mutable draft per author and a chain of immutable published versions. Version numbers only move forward; diffs are first-class; runs and compiles pin to versions, so nothing you run can change under you.

Glossary

The vocabulary, in one place

Short definitions, consistent with what every editor and label calls things.

Platform terms

  • Tool

    The smallest unit of computation — one canvas node type from the catalog.

  • Mode

    A named variant of one tool, chosen in its configuration — one node, several behaviours.

  • Wire

    A typed connection between two ports. Types must agree, or an adapter bridges them.

  • Interpretor

    A tool that reads raw indicator output and answers a semantic question with a verdict.

  • Document

    One authored artifact — a search signal, filter, create order, deal stage or indicator — stored as a graph or typed configuration.

  • Draft

    Your single mutable working copy of a document. Publishing turns it into a version.

  • Version

    An immutable published snapshot of a document. Runs and compiles always execute versions.

  • Search signal

    The stage document that decides buy or sell on every bar.

  • Filter

    A stage document that gates signals with one boolean answer; its category decides cancel versus hold.

  • Create order

    The stage document that shapes a signal into take-profit, stop-loss and confidence.

  • Deal stage

    The post-execution stage: qualification and sizing models managing the open position.

  • Strategy

    The composed assembly of the four stages, published as a version.

  • Run

    One backtest or optimization executing a published version against history.

  • Robustness score

    A 0–100 composite from six validation analyzers, computed after every optimization.

  • Robot

    A compiled Expert Advisor file produced from a strategy version.

  • Indicator document

    The document family that compiles to a custom MetaTrader indicator; its graph ends in sinks.

  • Sink

    A terminal indicator-lane node: a plot, an alert, or a chart object.

  • Cell

    A reusable sub-graph, shared by link and referenced inside filters.

  • Journey data

    The per-signal data bus stages use to pass values forward.

  • Credits

    The prepaid balance that meters compute. Runs hold a worst-case amount, then settle to actual.

  • Entitlement

    What a marketplace purchase grants: run access to a sealed product, or a private clone of an open one.

  • Repainting

    When a tool's past values change as new bars arrive. The engine re-evaluates such tools bar by bar so backtests stay honest.

Report metrics

  • Initial deposit

    Starting equity used to open the backtest. Every profit-and-loss figure on the report is measured relative to this number.

  • Final balance

    Where the account ended up at the last bar of the run — starting equity plus the sum of every closed trade.

  • Total net profit

    Sum of every closed trade over the whole run. Positive means the strategy made money; negative means it lost money.

  • Gross profit

    How much the winning trades alone made, before any losers are netted out. Always non-negative.

  • Gross loss

    How much the losing trades alone gave back, shown as a positive magnitude so it lines up with gross profit side-by-side.

  • Profit factor

    Dollars earned per dollar lost. Values above 1 are profitable; a value of 2 means the strategy makes two dollars for every one it gives back.

  • Expected payoff

    Statistically expected dollar outcome of the next trade — literally the average result per trade so far. Think of it as the house edge of the strategy.

  • Recovery factor

    How much profit was produced for every dollar of the worst drawdown. High numbers mean the strategy digs itself out of holes quickly relative to the money it makes.

  • Calmar ratio

    Return versus the largest peak-to-trough hit — a risk-adjusted return measure that uses worst-case drawdown instead of volatility. In this implementation it shares the formula of recovery factor.

  • Sharpe ratio

    Classic risk-adjusted return — average return divided by its standard deviation, annualised. It assumes a zero risk-free rate. Higher values mean the strategy earns more per unit of volatility.

  • Sortino ratio

    Like Sharpe but only punishes downside moves — upside volatility is treated as a feature, not a bug. Fairer for strategies with asymmetric, skewed payoffs.

  • Ulcer index

    Downside-only risk score — the root-mean-square of the percentage drawdowns from every running peak. Large drawdowns hurt the score proportionally more than small ones, so it reflects the pain of holding the strategy through bad stretches (Peter Martin, 1987).

  • Balance drawdown absolute

    Absolute drawdown — how far below the starting equity the account ever dipped, measured in account currency. It only counts time spent underwater relative to day one.

  • Balance drawdown maximal

    Maximal drawdown — the biggest peak-to-trough drop on the closed-trade balance curve, in account currency. Captures the worst streak of losses regardless of where in the run it occurred.

  • Balance drawdown relative

    Worst percentage drawdown at any peak on the balance curve. Unlike the maximal dollar version, this picks out the steepest relative hit even if it happened early when the account was small.

  • Equity drawdown absolute

    How far below the starting equity the account ever went when floating open-position P&L is included. It can be worse than the balance-curve version because unrealised losses count.

  • Equity drawdown maximal

    The largest peak-to-trough drop measured on the equity curve (balance plus open-position P&L). Matters more than the balance version for strategies that hold positions through storms.

  • Equity drawdown relative

    Worst percentage drawdown measured against any running peak on the equity curve — the single worst bar-to-bar equity pullback in the whole run, in percentage terms.

  • Max drawdown

    The headline worst-case drawdown percentage — how much of the peak equity was given back at the worst point during the run. Prop-firm evaluators care about this number a lot.

  • Max drawdown duration

    Longest stretch, measured in bars, during which the equity curve stayed below its most recent peak without making a new high — i.e. the longest time spent underwater.

  • Total trades

    How many trades closed during the backtest window. Statistical significance of the other metrics rises with this number.

  • Winning trades

    Number of trades that closed with a profit strictly greater than zero.

  • Losing trades

    Number of trades that closed flat or at a loss. Break-even trades are counted on this side, not the winning side.

  • Win rate

    Share of trades that closed profitably. On its own it tells you almost nothing — a 90% win-rate can still lose money if the occasional loser is huge.

  • Long trades (won %)

    How many buy-side trades were taken, with the share of those that were profitable shown in parentheses.

  • Short trades (won %)

    How many sell-side trades were taken, with the share of those that were profitable shown in parentheses.

  • Largest profit

    Biggest single profitable trade of the whole run. Useful for spotting whether the net result is driven by one lucky outlier.

  • Largest loss

    Biggest single losing trade of the run, shown as a negative value. A realistic stop-loss should keep this within your risk budget.

  • Average profit

    Mean dollar size of a winning trade. Together with the losing counterpart it tells you the payoff ratio of the strategy.

  • Average loss

    Mean dollar size of a losing trade (negative magnitude). Compare with the average winner to see whether your winners are bigger than your losers.

  • Max consecutive wins

    Longest run of back-to-back profitable trades. Long winning streaks can signal trend-following behaviour — or, in a thin sample, just luck.

  • Max consecutive losses

    Longest run of back-to-back losing trades. Matters a lot for position sizing — if this run is 8, could the account survive 8 losers at your risk-per-trade setting?

  • Max consecutive profit

    Dollar sum of the best winning streak. Useful for calibrating realistic upside: this is what a run of good luck actually felt like.

  • Max consecutive loss

    Dollar sum of the worst losing streak (negative). A key stress figure for risk-of-ruin: can the account absorb this and keep going?

  • Avg consecutive wins

    How long, on average, winning streaks last. Higher numbers hint at momentum/trend behaviour in the edge.

  • Avg consecutive losses

    How long, on average, losing streaks last. Should shape how aggressively you scale position size after a loss.

  • Average holding

    Mean number of bars a position stayed open. Combined with the timeframe it tells you the typical holding horizon of the strategy.

  • Min holding

    Shortest position duration (in bars). Very small values often mean SL/TP levels are tight relative to bar size or the logic is scalping.

  • Max holding

    Longest position duration (in bars). Useful for catching trades that overstayed — might flag a missing exit rule or a timeout opportunity.

  • Z-score

    Run-test on the win/loss sequence (MetaTrader-5 definition). Positive z means wins tend to follow wins and losses follow losses — the sequence has momentum. Negative z means the sequence is more alternating than random. Values with magnitude greater than 1.96 are statistically significant at the 5% level.

  • LR correlation

    Pearson correlation between the balance curve and a straight line drawn against bar index. Values near 1.0 mean a remarkably steady, straight-line equity curve; values near 0 mean the curve is jagged and uneven.

  • LR standard error

    Standard deviation of the balance curve around its straight-line fit. Smaller means the account grew in a tighter, more predictable corridor around the trendline.

  • Average MAE

    Average Maximum Adverse Excursion — the typical worst unrealised loss a trade had to sit through before closing, converted to account currency (John Sweeney, "Maximum Adverse Excursion").

  • Average MFE

    Average Maximum Favourable Excursion — the typical best unrealised profit a trade reached before closing, in account currency. If MFE is much bigger than the actual win, trade management is leaving money on the table.

  • Correlation (profit, MAE)

    Pearson correlation between the final profit of a trade and how far the trade went against it first. A strongly negative value means trades that dipped deep tended to close as losers — stops are probably too tight.

  • Correlation (profit, MFE)

    Pearson correlation between the final profit of a trade and how far it ran in its favour. Strongly positive means the big winners did, in fact, run far — suggests take-profits could be wider or replaced with a trail.

  • Correlation (MAE, MFE)

    Pearson correlation between how far a trade went against it and how far it ran in its favour. High values mean volatile trades just move a lot in both directions — the strategy is exposed to noise as much as edge.

Validation metrics

  • PBO

    Probability of Backtest Overfitting. The fraction of in-sample/out-of-sample splits where the in-sample winner underperforms out of sample. Below 50% is the acceptable range.

  • DSR p-value

    Deflated Sharpe Ratio significance, corrected for multiple testing and higher moments. Above 0.95 means the strategy beats the null at the 5% level.

  • MC p-value

    Monte Carlo trade-shuffle test. How often a random permutation of the trades produces a Sharpe ratio as good as the real sequence.

  • SPA p-value

    Hansen’s Superior Predictive Ability test. Whether the strategy beats a benchmark once data-snooping bias is accounted for.

  • WFE mean

    Walk-Forward Efficiency. The ratio of out-of-sample to in-sample performance, averaged across windows. Values near 1.0 mean no degradation.

  • Param drift

    The mean coefficient of variation of the best parameters across walk-forward windows. High drift means the strategy has no stable optimum.