Find indicators, trading systems and algorithm families
Navigate the installed content catalogue and distinguish decision support, executable strategies and research.
Reviewed 2026-10-24 · Windows & macOS
On this page
Treat the installed catalogue as current#
AMM discovers concrete content from the watched plugin workspace. The catalogue changes when packages are installed, rebuilt or removed. Use the algorithm/indicator selectors, Trading Systems page and GET /api/plugins, /api/algorithms and /api/plugins/artifacts for your installed inventory. A source repository can contain research that is not built or admitted for trading.
Plugin identity, indicator Type, algorithm class and trading-system ID are separate keys. An assembly can contain many algorithms and indicators. The same system family can offer a decision-support chart and an executable baseline with different assumptions. Read the selected entry's guide instead of inferring behavior from the family name.
Standard and custom indicators#
The AMM.StandardIndicators package supplies ordinary chart/screener types:
| Type | What it exposes |
|---|---|
sma, ema |
Moving-average lines |
rsi, atr |
Momentum/volatility values |
macd |
MACD, signal and histogram |
moving_average_crossover |
Fast/slow lines and spread |
bollinger_bands |
Middle, upper and lower bands |
stochastic |
K and D |
pivot_break |
Direction and broken level |
pivot_points |
Central pivot and support/resistance levels |
candlestick_patterns |
Confirmed pattern direction/count/strength and family scores |
donchianChannel, hullMovingAverage |
Compatible channel/Hull types with retained stable spelling |
These are plugins, not host fallback calculations. The Donchian/Hull legacy IDs deliberately retain camel case for saved configurations. Candlestick markers can contain several confirmed patterns on one candle; +N indicates additional detections, not extra orders.
TradingViewIndicators adds tradingview_ema_hull and key_bars. NovaVolume adds volume, liquidity/context and system outputs. System packages add their own setup/score or multi-timeframe overlays. Chart signals use completed-bar semantics where declared; a displayed badge does not submit an order.
Packaged Trading Systems guides#
The source-backed package set reviewed for this guide contains the following named systems. Your installed list can be smaller or newer; required-plugin warnings explain unavailable tools.
| Package | Guide entries |
|---|---|
| DiscretionarySystems | ATLAS; PULSE; HARBOR; VAULT; Three Ducks; Phillip Nel 4H MACD; DIBS; CHOROS 10-EMA Rejection (AMM rules); Buy Sell Line; Pivot Point Break; COMPASS Daily Trend Transition |
| ForexFactoryStrategies | Trading Made Simple; TMS M30 - Likica; Genesis Matrix; Sonic R Classic; DIBS Mechanical Baseline; Highest Open / Lowest Open; Trading Made Simpler RSOR; Magic 100 |
| D1ElasticityPullback | D1 Elasticity Pullback |
| DanceOfTheWickResearch | Dance of the Wick Mechanical Proxy |
| GuppyReinvented | Guppy Re-Invented XAUUSD M15 v2 |
| IchimokuH4D1 | Ichimoku H4 D1 |
| MtfStochastics | MTF Stochastics |
| TrendCrossBreakout | Trend Cross Breakout |
| H4Systems | AURUM Channel; MOSAIC Momentum; RADIANT RSI Momentum; ZENITH Band Momentum |
| NovaVolume | Nova Volume |
These describe 30 guide entries in the reviewed source, not a fixed application limit. Each descriptor links companion chart and screener tools and declares its historical-example capability. Optional workspaces assemble them into a complete board.
Choose a family by task#
For discretionary trend review, ATLAS combines trend/pullback context, Three Ducks uses completed H4/H1/M5 agreement, and CHOROS implements a clearly labeled rejection subset. For session analysis, PULSE freezes a local opening range and DIBS uses its declared time boundary. HARBOR examines failed-auction/reclaim context; VAULT examines compression/release; Pivot Point Break uses prior-session levels and explicit confirmation settings.
H4Systems separates gold channel breakout, index momentum, RSI/EMA momentum and band continuation. The standalone FX/MTF packages have their own source interpretation and cadence. Do not apply a system to another timeframe/asset because the selector permits it without checking the rule and warmup implications. COMPASS has a recorded rejected-promotion research boundary; a packaged guide is not an endorsement of its returns.
The two DIBS entries remain intentionally distinct. Their plugin types, rules, charts and screeners differ. Likewise, a forum-derived normalized baseline or black-box indicator reconstruction should not be presented as exact original-source equivalence.
Algorithm and research families#
The broader workspace includes an algorithm collection, equity/index constituent examples, tick-scalp and Magnificent Seven quote research, runtime-instrument lifecycle examples and adaptive/causal multi-market research packages. Exact algorithm names, parameters and retained-history recommendations come from the loaded /api/algorithms response. Search/filter that catalogue instead of relying on a permanent count.
Research projects can be staged, source-only, rejected, incomplete or pending native/broker acceptance. A manifest/build establishes availability, not profitability or production readiness. A point-in-time equity strategy needs dated membership; a quote-tick strategy needs the declared recorded quote source; a futures strategy needs exact contract/roll metadata. Preserve fixed sizing and complete evidence when comparing candidates.
Use and maintain content safely#
Open the selected system's guide, read rules/invalidations/risk/limitations, then launch its chart or screener. Inspect account, provider, symbol and timeframe after importing assets. Test in historical review or Simulation before considering Paper/LIVE. A guide's plan levels and human checklist are not automatic protection orders unless a separate executable algorithm explicitly implements them.
When updating a package, verify its new payload and required types, start a fresh run and retain the prior configuration/results. Keep public catalogue documentation generated or checked from descriptors and runtime discovery so a new package does not require changing a hard-coded application list. See Plugin templates, Algorithm authoring and Indicator authoring for extension workflows.