reference · 5 min read
Understand AMM terminology
Look up the distinctions that matter when configuring charts, research, automation and integrations.
Reviewed 2026-10-24 · Windows & macOS
On this page
Workspace and interface#
| Term | Meaning |
|---|---|
| Named workspace | An explicitly saved snapshot of workspace preferences and supported window/tab state |
| Open workspace | A currently open workspace with working state; it can differ from its saved snapshot |
| Workspace tab | A full app shell and its own canvas inside a native window |
| Canvas item | A feature instance such as a chart, Backtest or screener with its own scoped state |
| Panel | A dockable part of an item, such as Configure, Results or a ledger |
| Pop out | Show a panel in a native panel window while retaining its owner |
| Move | Transfer content to another target tab/window/workspace; different from a view-only pop-out |
| App screen | A shell-level screen such as Settings, Licensing or MCP server opened over the canvas |
| Symbol/timeframe link | Independently chosen color channels that propagate supported context changes |
| Template | A reusable chart, screener, workspace or command definition imported into normal user state |
Markets and execution#
| Term | Meaning |
|---|---|
| Venue/provider | The concrete execution or market-data integration; capabilities differ |
| Execution account | The exact account and environment to which orders belong |
| Demo/paper | A provider's non-live account environment with provider-reported capital and rules |
| Simulation | AMM's simulation venue; distinct from a real broker's demo account |
| Replay | Historical observations advanced by an explicit replay clock rather than current market time |
| Broker symbol | Exact instrument identity used by the execution provider |
| Live-data symbol | Exact instrument identity used for streaming observations |
| Historical symbol | Exact identity used for history and warmup |
| Netting | An account model that combines exposure into net positions under its contract |
| Hedging | An account model that can retain separate opposing/individual positions |
| Fill style | Historical execution semantics such as Standard or cTrader-style; separate from netting/hedging |
| Working order | An accepted order that remains open or partially unfilled |
| Local order | AMM-managed conditional intent whose lifecycle differs from a broker-native order |
| Protection | Explicit stop-loss/take-profit intent or orders; implementation depends on venue and session |
| Preflight | Admission review of exact account, route, capability and safety conditions before starting |
| Manual override | Controlled intervention in strategy-owned exposure so algorithm ownership is respected |
| Reconciliation | Compare actual provider positions/orders with retained app ownership and expected state |
| Continuous future | A research/selection series connected to dated contracts and roll policy; not itself a generic exchange contract |
Research and risk#
| Term | Meaning |
|---|---|
| Backtest | A historical chronological engine run under explicit data, account, cost and fill assumptions |
| Declared instrument | An instrument described by the algorithm for configuration/preview |
| Runtime instrument | An instrument actually resolved/used by the run, with retained provenance |
| Warmup | Earlier observations needed to initialize indicator/algorithm state before decisions |
| Optimization candidate | A parameter combination and its evaluated historical results |
| Brute Force | Exhaustive evaluation of the configured search combinations |
| Grid Search | Adaptive search/refinement over the configured parameter domain |
| Genetic Algorithm | Population-based search under configured fitness and generation rules |
| In-sample | Data used to select parameters |
| Out-of-sample | Later held-out data evaluated after selection |
| Walk-forward | Repeated historical in-sample selection followed by subsequent out-of-sample tests |
| Portfolio sleeve | An independently saved strategy result used in artifact portfolio research |
| Daily-close blending | Combining source sleeve returns at terminal UTC daily observations under the stated fixed-weight model |
| Factor exposure | Model-estimated sensitivity to chosen explanatory return factors |
| Risk contribution | An attribution from the chosen covariance/model assumptions, not a guaranteed realized loss |
| Liquidity estimate | Capacity/participation calculations based on available volume/price coverage and model inputs |
| Scenario | A modeled set of shocks or conditions applied to an analysis; different from an observed future outcome |
Operations and extensions#
| Term | Meaning |
|---|---|
| Broker Manager/relay | A shared upstream-connection process used by supported live-provider routes |
| Worker | A separately configured API execution node for whole research jobs |
| Platform Server | A separate server role used by supported shared/hosted services, not a promise of managed cloud trading |
| REST catalogue | Runtime-generated operations and schemas at the configured API origin |
| MCP | Local Model Context Protocol transport projecting AMM operations with their normal policies |
| UI command bus | Correlated remote commands handled by a connected trusted primary UI |
| Mounted control | An actual currently exposed UI control/action discovered from the running app |
| Plugin manifest | The versioned metadata/payload declaration that makes an external extension discoverable |
| Shadow copy | Content-addressed loading of a plugin payload without rewriting a running instance |
| Background alert | A server-owned monitor independent of a visible chart or screener |
| Screener rule | A rule evaluated while that screener runs; not automatically a persistent background monitor |
| Audit | App-owned request/execution evidence, separate from broker history |
Use the linked task guides for exact configuration steps. Similar words in two provider interfaces do not guarantee identical order or data semantics.