Most trading ideas don't start as a blank page in Maple — they start as a note, a forum post, or a strategy already coded up in TradingView's Pine Script. Strategy Import (currently in private alpha) is the on-ramp for those ideas: paste a strategy in plain English or Pine Script, and Maple reads it, explains what it found, and gets it ready for the same backtesting and validation every strategy in Maple goes through.
Why importing strategies matters
Rebuilding an idea by hand, field by field, is a real barrier between having a strategy and actually testing it — and a barrier is exactly what causes people to trust an idea on faith instead of evidence. Import removes the retyping step so more ideas make it to a real backtest instead of staying a hunch.
Why Maple reviews a strategy before testing it
Reading a strategy out of a paragraph of English or a script written for a different platform is an act of interpretation, not a lookup — and interpretation can be wrong. Before anything is backtested, Maple shows exactly what it understood, in plain language, so the mistake gets caught by a human before it quietly becomes a misleading result. This is the same "evidence over excitement" instinct behind the rest of Maple's methodology, applied one step earlier — to the strategy itself, not just its results.
Why Pine Script doesn't specify an asset
A Pine Script strategy is written to run on whatever chart it's attached to in TradingView — the script itself doesn't hard-code a market. That's normal, not a defect in the script. It does mean Maple can't know which asset to test an imported strategy against until a person chooses one, which is why asset selection is always a required, visible step after import, never an assumption Maple makes quietly on your behalf.
Why missing information has to be resolved before validation
Running a backtest or a full validation on a strategy with a real gap in it — no asset, an entry rule with no exit — wouldn't fail loudly. It would just produce a number that looks like a result but rests on an assumption nobody actually made. Maple would rather stop and ask than hand back a confident-looking answer to a question that was never fully specified.
Why unsupported features are disclosed instead of guessed
Plain-English descriptions and Pine Script can both reference logic Maple doesn't yet model — a custom indicator, a volatility-based stop, a volume filter. When that happens, Maple doesn't silently drop the rule or approximate it with something close enough to look complete. It's called out directly, as a warning attached to the specific part of the strategy it affects, so the gap between what you described and what was actually tested stays visible.
Why exports are best-effort
Exporting an imported strategy back out to plain English or Pine Script is the same kind of translation as importing one, run in reverse, and it carries the same caveats: any assumption Maple made, or anything it couldn't fully translate, is written directly into the exported text rather than hidden. Treat an export as a well-organized draft worth reading — not a finished, verified artifact — before sharing it or pasting it into TradingView.
How this fits Maple's mission
Maple's mission is separating a real, repeatable edge from a strategy that only looks good — and that discipline has to start before a single trade is simulated. Strategy Import applies the same honesty Maple brings to a backtest's results to the strategy's structure itself: show what's understood, flag what's missing, disclose what's unsupported, and never quietly paper over a gap.
Example strategies you can paste
A few short examples to try, either as plain English or Pine Script.
Plain English: EMA crossover
Go long when the 20 EMA crosses above the 50 EMA. Go short when the 20 EMA
crosses below the 50 EMA. Exit on opposite signal. Use a 3% stop loss.Plain English: RSI mean reversion
Buy when RSI(14) drops below 30. Sell when RSI(14) rises above 70.
Use a 5% stop loss.Pine Script: EMA crossover
strategy("EMA Cross", overlay=true)
fastEma = ta.ema(close, 9)
slowEma = ta.ema(close, 21)
if ta.crossover(fastEma, slowEma)
strategy.entry("Long", strategy.long)
if ta.crossunder(fastEma, slowEma)
strategy.close("Long")Pine Script: RSI strategy
strategy("RSI Reversion", overlay=false)
rsiValue = ta.rsi(close, 14)
if ta.crossunder(rsiValue, 30)
strategy.entry("Long", strategy.long)
if ta.crossover(rsiValue, 70)
strategy.close("Long")Plain English: a partially supported example
This one is worth trying on purpose — it shows how Maple discloses a rule it can't fully support instead of guessing at it:
Go long when the 20 EMA crosses above the 50 EMA, but only when volume is
above its 20-period average. Exit using a 2x ATR trailing stop.Maple understands the EMA crossover entry, but will flag the volume filter and the ATR-based trailing stop as unsupported today — visible in the review, not silently dropped.