Live Terminal & operational surfaces
Two operational surfaces sit alongside My Strategies. One works; one does not yet.
Live Terminal
/live-terminal
A real-time event stream for your deployed strategies, the surface for watching what is happening right now rather than reviewing what happened.
What it shows
| Order events | Submitted, acknowledged, filled, partially filled, rejected, cancelled |
| Strategy events | State changes, evaluations, risk decisions |
| Raw log view | A lower-level event view for detailed inspection |
| Event history | Retained client-side so you can scroll back through a session |
Two views
The terminal view is the readable stream, events formatted with their meaning.
The raw log view is the underlying event data, for when the formatted line is not enough. It has its own storage so your view preference persists.
What it is good for
| Use it when | Because |
|---|---|
| A strategy just deployed and you want to see it evaluate | You see the first evaluation, not just the first fill |
| An order was rejected and you want the reason immediately | The rejection reason appears in the stream |
| You are debugging a strategy that is not trading | You can see whether it evaluated and decided no action |
| You want to confirm a risk gate engaged | The risk decision appears as an event |
That last one is genuinely useful during a paper run: watching a gate trip in the stream is how you confirm your limits are real. See Alerts & breaches
Limitations
- It is a live stream, not a report. For historical analysis use the strategy detail Trades and Orders tabs.
- Retention is session-scoped. Close the tab and the scrollback goes.
- It shows events, not aggregates. No P&L totals, no exposure summary.
Algo Execution Console
/algo-execution-console
The route renders a complete interface: a search header, a stat grid (triggered, sent, rejected, out of sync, pending) and an orders table with columns for strategy id, order id, instrument, side, quantity, order type, status, execution delay and rejection reason.
It is backed by an empty mock data array. The table has no rows because there is no data source wired to it, and one of the stat figures is a hardcoded constant rather than a computed value.
Use Live Terminal and My Strategies instead. Both are wired to real data.
Why document it at all
Because the route is reachable, it has a guided tour anchor, and it looks like a working operational console. A user who lands on an empty table will reasonably conclude something is broken with their strategy rather than with the page.
Being explicit costs one paragraph and saves a support ticket.
What it is intended to become
The column set tells you the intent, and it is a genuinely useful one that no current surface fully covers:
| Intended column | What it would answer |
|---|---|
| Strategy id and order id | Which strategy, which order |
| Instrument with contract detail | Including derivative legs, e.g. a strike and right |
| Side, quantity as filled/total | Partial fill visibility in one place |
| Order type | Market, limit, stop |
| Status | Filled, partially filled, rejected, cancelled, retry in progress, out of sync |
| Execution delay | Latency between signal and fill |
| Rejection reason | Why, inline in the table |
Two of those are not available anywhere today. Execution delay is the measurement that would let you quantify backtest-versus-live divergence directly, and out of sync is the reconciliation state between the platform's view and the broker's. Both are worth having.
Until it is wired, the nearest equivalents are the Live Terminal event stream for reasons and latency impressions, and the strategy detail Orders tab for order history.
Choosing a surface
| Question | Surface |
|---|---|
| How is my portfolio doing? | My Strategies |
| What is this one strategy doing? | My Strategies, then strategy detail |
| What is happening right now? | Live Terminal |
| Why was that order rejected? | Live Terminal, or the strategy's Orders tab |
| What does my broker think my exposure is? | Broker risk exposure |
| Tell me when something happens | Notifications |