REFERENCE
The words that keep the workflow precise.
A shared vocabulary for research, charting, strategy identity, automation state, portfolio boundaries and evidence.
TERMS
Meridian vocabulary
Use these meanings when moving between the public reading surfaces and the instrument workspace.
| Term | Meaning | Why it matters |
|---|---|---|
| Data seam | The source and continuity boundary that provides a series or event. | A value without its seam is difficult to trust or reproduce. |
| Model | A defined lens that computes or describes a market condition. | The model question limits what its output can mean. |
| Indicator | A chart instrument with inputs and plots. | Its placement and scale determine how the signal is read. |
| Pane | A chart region with its own scale. | Separate scales prevent unrelated values from sharing a false axis. |
| Overlay | A chart mark drawn in the price field. | It should share the meaning of the price context. |
| Strategy document | The graph plus settings that defines executable logic. | The document identity is what later revisions link to. |
| Compile pass | The strategy graph satisfies structural compilation checks. | It is necessary for execution, not evidence of performance. |
| Backtest | A historical evaluation of frozen logic and assumptions. | Its assumptions must be compared with paper/live behavior. |
| Revision | An immutable executable snapshot of a strategy definition. | Runtime records should point to the revision they actually ran. |
| Automation | A runtime definition that observes alerts or executes a revision. | It carries mode, status, evidence and lifecycle. |
| Paper | An execution mode without live exchange funds. | It is safer for observing behavior, but not identical to live fills. |
| Live | An execution mode that can place real exchange orders. | It requires a verified connection, risk controls, fresh reconciliation and the LIVE_TRADING_ENABLED safety boundary. |
| Provenance | The context explaining where a result came from. | It connects performance or events to data, revision and timing. |
| Durable Alert | An alert result stored beyond a transient toast. | It lets you reconstruct an event after a tab closes. |
| Sync conflict | A disagreement between local and account-backed workspace state. | Resolving it overwrites one side, so the choice must be explicit. |
PUT IT TO WORK