Omni Terminal

Price & Market Structure

Chart-first market context built for live trading decisions.

Omni Terminal treats price as more than a line chart. The terminal combines live ticker state, candles, regime context, orderbook visibility, and downstream overlays so traders can interpret moves with surrounding structure.

At a glance

WS-first design
Live-first Market state comes from WebSocket streams, with REST or server loads used only where snapshots are needed.
Market context
Ticker + candles Price views combine live ticker updates, candle snapshots, and regime-driven chart context.
Execution framing
Integrated Price is interpreted alongside liquidations, funding, L4, and news rather than in isolation.

Why It Matters

What traders and researchers should take away

  • Live price without surrounding context is weak; traders need ticker, structure, and nearby risk signals together.
  • A price move means something different when regime, liquidation pressure, and orderbook structure line up.
  • This page explains why Omni is a terminal workflow rather than just another chart.

How it works

What the product uses behind the scenes

  • Omni Terminal documents the stream inventory for ticker, candles, LVWAP, and regime state.
  • The terminal UI wires Price, L4, liquidations, funding, and news as adjacent surfaces inside one workflow.
  • The node to data-api to terminal chain explains why price views stay aligned with downstream analytics.

Notes

Things to know

  • Price views are real-time analytical context, not an execution guarantee.
  • Different streams have different snapshot behavior; some views hydrate from server data before live updates take over.
  • Price interpretation should be paired with liquidity, liquidation, and news context for higher-confidence decisions.

Chart workspace

The price surface is the terminal entry point for live market structure.

  • The selected symbol drives chart state, ticket context, center-panel analytics, and adjacent market panes.
  • Live ticker and candle updates keep the visible chart aligned with the terminal websocket model.
  • Regime and LVWAP-oriented overlays add structure beyond a plain price line without forcing the user into a separate research page.

Connected surfaces

The chart is useful because it is wired into the rest of the terminal instead of acting like a detached widget.

  • L4 and orderbook surfaces help explain whether visible liquidity supports or contradicts the chart move.
  • Liquidation, funding, IV, and news tabs keep the market structure read close to execution context.
  • Trader-profile and wallet-cluster routes let a user pivot from market movement into public wallet investigation.

Execution context

A chart-first workflow still needs ticket and account checks before any order action.

  • The order ticket should be reviewed against selected symbol, side, size, reduce-only state, leverage, and account scope.
  • Funding and collateral actions remain separate wallet-authorized flows even when reached from the same terminal workspace.
  • Mobile and tablet layouts preserve the same flow, but prioritize chart, ticket, summary, and private tabs differently by viewport.

Implementation notes

The chart should be described as stream-backed terminal context, not as a magical signal generator.

  • Use WS_STREAMS.md for stream behavior and snapshot rules.
  • Use TerminalPageView.svelte for how the terminal composes price, analytics tabs, private state, and execution controls.
  • Use architecture docs to explain why browser routes talk to the Omni API rather than directly to node infrastructure.

References

Implementation references

  • WebSocket streams

    omni-terminal/docs/WS_STREAMS.md

    Documents ticker, candles, LVWAP, and regime stream behavior and snapshot rules.

  • Terminal page stream design

    omni-terminal/src/lib/components/terminal/TerminalPageView.svelte

    Shows how Price, L4, News, Wallet Clusters, Funding, Margin Stress, and IV are presented inside one terminal surface.

  • Terminal API architecture

    omni-terminal/docs/ARCHITECTURE_TERMINAL_API.md

    Explains the browser-facing terminal route model used by the chart and market views.

Next