Nexus Algo Cockpit Guide: Every Panel and Status Indicator

The cockpit in one safe reading order

1. Check identity and broker mode: Read the desktop header first. CONN_LIVE means a broker connection is present; MOCK_SANDBOX means the live connection condition is not met. Confirm the intended account before relying on any balance or position.
2. Check market synchronization: Read Live Sync or Sync Stopped in the header and the more detailed footer state. A live account still needs a healthy, current market feed.
3. Check safety and account capacity: Review the kill switch, wallet or broker balance, credit or trial state, configured order size, and account risk settings before enabling a deployment.
4. Read research as evidence, not permission: Use the market-research panel to inspect quote age, spread, momentum, RSI, VWAP, volume, breakout, volatility, and any trap labels. A strong-looking candidate must still pass server-side gates.
5. Read the operations console during activity: After Ignite, follow the phase pipeline, Processing or Blocked state, deploy-block analysis, and order context instead of relying on the aircraft animation alone.
6. Reconcile with orders and the broker: Use Live Executed Position Orders for open or pending rows and the Executed Trades Order Ledger for settled rows, then verify material state with the broker.

Desktop header and the five account summary cards

The header is the first operational boundary. It exposes broker connection mode, market synchronization, credit or trial access, the kill-switch control, settings, and the signed-in account. The kill switch is a control for blocking new orders; it should not be interpreted as proof that existing broker positions have been closed.

Directly below the shell, five cards summarize the account and the operational ledger. These values are useful for orientation, but each has a different scope.

• Amount Invested: entry-price notional currently deployed in active contracts.
• Active Live Profit: unrealized profit or loss across running positions, using the current marks available to the app.
• Realized Profit: operational closed-trade profit or loss, with today calculated on the India Standard Time day and an all-time total maintained for the ledger.
• Autopilot Win Rate: winning operational closes divided by the closed operational trades supplied to the dashboard; it is a historical ratio, not a forecast.
• Broker Wallet or Demo Wallet: the displayed available balance. A refresh control appears when the broker is connected, and margin used can appear separately.
• Credit or trial badges: platform deployment access, not broker cash, margin, or guaranteed trading capacity.

What the five lifecycle states mean

When the cockpit is idle, the lifecycle strip shows five labeled stages. The highlighted state follows the local flight state used to explain the workflow. Once a server loop or deployment is active, the large operations view replaces the normal three-column cockpit.

• Research: the standby and research states, covering candidate discovery and signal inspection.
• Strategies: the gearing-up state, when selected parameters and sizing are being prepared.
• Orders: the take-off state, when the client-side deploy handshake is underway.
• Execution: the cruising state, used while a loop or position workflow is active.
• Profit: the landing state, used while the cockpit returns toward standby after a close or abort sequence.

Market Research panel: price context and signal telemetry

The left research panel lets the user search and select a tradeable symbol, view a short price trace, and compare the current candidate with the rest of the watchlist. The sigma badge classifies recent average price movement as LOW, NORMAL, or HIGH for this display.

The live edge area combines several current fields. Relative Strength Index (RSI), momentum, tick change, score, Exponential Moving Average (EMA) stack, Average True Range (ATR), volume, Volume-Weighted Average Price (VWAP) distance, spread, quote age, data source, relative strength, and breakout score are research inputs. Optional trap and support or resistance labels add context, while the F&O strike radar can surface a contract candidate for eligible underlyings.

• Quote age in seconds helps distinguish a fresh update from an older one; REST indicates the displayed data came through the REST fallback path rather than a current stream label.
• Spread is the available bid-ask spread percentage. N/A means the field was not available, not that the spread was zero.
• Score ranks or describes research evidence. It does not waive quote freshness, risk, margin, exposure, duplicate-intent, broker, or execution checks.
• BULLISH, BEARISH, and NEUTRAL sentiment in this card are derived from the displayed price change; they are not a promise about the next move.
• The watchlist and F&O strike radar are selection aids. The user still needs to inspect tradability, liquidity, expiry, lot size, and broker state.

Learning Memory and Execution Quality panels

Learning Memory summarizes closed outcomes used by the in-product learning records. Awaiting closes means there is no usable close history for the panel, Warming means history is accumulating, and Active means the summary has enough current memory to display learned buckets. Bucket trade count, win rate, and score bias describe recorded observations; they do not validate a strategy by themselves.

Execution Quality opens a dedicated view of the signed-in user’s fill-price slippage aggregates and recent deploy-decision records. It helps answer whether broker-confirmed fills differed from the prices expected by Nexus and why selected quality or quant gates passed or blocked a candidate.

Center flight deck, sizing controls, and strategy switches

The center panel combines an animated workflow display with the settings that will be sent when the user chooses Ignite & Execute. The allocation label changes with capital, asset preferences, and mode. The amount cannot exceed the available balance shown to the cockpit, and the panel previews any applicable deployment-credit cost.

The Auto Pilot checklist mirrors selected configuration. Risk Safeguard, Position Sizing, Multi-Asset, and Smart routing checks are a compact settings summary. The “ALL SECURE 100%” line is not an independent end-to-end certification of market data, broker margin, order acceptance, or future safety.

• Options Only restricts the requested workflow to contracts and reveals an underlying selector.
• MTF Equity requests the Margin Trading Facility path for eligible equity; it is disabled when Options Only is active.
• Delivery requests the CNC or delivery equity path and is mutually exclusive with MTF in the control logic.
• Sentiment AI enables the available sentiment overlay; when the shared model integration is unavailable, the label identifies a local overlay.
• Auto Signal lets Ignite use a sufficiently strong ranked symbol; otherwise the server workflow can scan without that client-selected symbol.
• Win Rate enables the stricter high-win-rate preference in the deployment configuration. The label is a guard setting, not a guaranteed 80% outcome.
• Test Mode is session-only and defaults off. When enabled, the requested deploy size is capped at one exchange lot for F&O or one share for equity; it does not bypass live-session hours or other gates.
• Scalper Mode selects faster scan behavior and tighter strategy settings, forces indicator convergence on, disables the sentiment overlay for speed, and turns Delivery off.

Ignite, readiness chips, and market-session messages

For a live non-sandbox workflow, Ignite is available only during the configured National Stock Exchange session. The button displays NSE Closed outside that window. Demo and sandbox modes are exempt from the live-session condition, but Test Mode itself is not an exemption.

For a connected live broker using options or scalper mode, the cockpit can show Desk pending, Warming desk, or Desk ready plus individual readiness checks. The current warm-up message names session one-minute bars, the option chain, and the premium pulse. Warm-up happens in the background; it is not a fill or deployment confirmation.

• Desk pending: readiness information is not yet complete.
• Warming desk: required market context is being prefetched.
• Desk ready: the current readiness checks passed for the selected desk context.
• Need credits: the requested platform deployment cost exceeds the current credit balance unless the account is exempt or on a free trial.
• NSE Closed: the live Ignite session condition is false.
• Error banner: the local or server start request returned a blocking message that should be read before trying again.

Operations Mode and the live console statuses

When deployment or the server autopilot loop is active, Operations Mode replaces the normal cockpit. The console shows the armed allocation, amount, cycle number when available, phase pipeline, recent research and operations events, current positions, and session profit or loss. It can expand to a full-screen Desk, Feed, and Orders view.

The console status chip distinguishes four conditions. Processing means the workflow is engaged, Standby means it is disengaged, Armed · blocked means a loop is active but current deploy conditions are preventing an order, and Blocked indicates an error condition. When available, the shield control opens categorized deploy-block reasons.

• Research, broker handshake, sizing, routing, monitoring, close, complete, and error phases describe where the recorded workflow event occurred.
• An amber deploy-block count is a reason to inspect the blocking cards, not a prompt to retry the order repeatedly.
• Abort & Liquidate requests loop shutdown and position handling through the server. Stop Loop appears when there are no active positions in the expanded console.
• An abort response can fail or remain subject to broker state. Verify every open position and exit in the broker account after using the control.

Performance State, Live Expectancy, and the right-side feed

The right panel calculates a return percentage from the active and closed trade data supplied to the cockpit. Ledger WR is the closed-trade win rate, PF Factor is gross winning profit divided by absolute gross losing profit, and Drawdown is the worst displayed trade return or total return when negative. CUM_ABS_PNL combines active marked profit or loss with closed profit or loss.

MKT VOL (σ) is the research display’s recent average absolute move, followed by the number of open positions or total rows in the cockpit ledger. The scrolling Auto Operations Feed contains short client-side workflow messages. Live Expectancy deliberately separates trusted or reconciled outcomes from uncertain records, so it can disagree with the broader realized-profit card.

Live positions, pending states, and the settled order ledger

Below the cockpit, Live Executed Position Orders shows active and pending rows with symbol, asset class, quantity, entry, current Last Traded Price (LTP) when available, profit or loss, strategy, protection levels, and an exit control. A Trigger Pending badge means the entry is waiting on its broker-side trigger state. Sell Trigger Pending or Broker Exit describes a pending broker-side exit condition.

The Executed Trades Order Ledger shows settled rows for the current IST day and offers symbol or strategy search. Manual marks broker-imported activity that Nexus reconciled for visibility rather than activity owned by the Nexus deployment path. Live Match ID is the stored broker order reference; warnings and rejected badges expose broker validation or reconciliation concerns.

• OPEN: the app currently treats the position as open and monitors its mark and exit state.
• PENDING or Trigger Pending: an order or trigger is not yet a completed open fill.
• CLOSED or settled: the local ledger has recorded the round trip as closed; review fill confidence and the broker record.
• Rejected or warning badge: read the broker message and investigate the cause before another attempt.
• Imported Manual: the broker-originated row is visible for reconciliation but is excluded from operational Nexus profit and win-rate calculations.
• Today’s settled count uses IST. Full historical truth remains at the broker, even when Nexus loads additional history for display.

Footer system-status map

The sticky desktop footer combines the market-running flag, feed health, broker connection, last-tick age, and quant status. Its exact labels are a compact troubleshooting map.

• LIVE SYNC: the market is running and the market feed is marked healthy.
• SYNC STOPPED: the market-running flag is off.
• FEED STALE: the market is running and the broker is connected, but the feed is not marked healthy.
• NO BROKER: the market is running, feed health is not live, and no broker connection is present.
• Tick N seconds ago: the age of the last recorded market tick while market running is true.
• Quant status: the current shared quant-pipeline status when that state is available.

Cockpit troubleshooting and safety limits

• CONN_LIVE but no fresh ticks: inspect the footer. A broker session and a healthy market-data feed are separate conditions.
• Desk stays Warming: keep the selected symbol and mode stable long enough for the named data checks, then inspect the feed and readiness details rather than repeatedly pressing Ignite.
• Armed · blocked: open deploy-block analysis and correct the stated data, account, strategy, or risk condition. Do not turn off safeguards simply to remove an amber badge.
• Profit cards disagree: compare active versus realized scope, today versus all-time scope, operational versus imported trades, and trusted versus suspect fill classification.
• A position looks missing or stale: refresh state and compare the broker order book and positions. The broker remains authoritative.
• Abort was pressed: confirm whether the loop stopped, whether exit orders were acknowledged, and whether any broker position remains open.
• The API is offline: use Retry Connection after services return. Do not infer that existing broker-side orders or protection stopped merely from the web status.
• Mobile layout differs: the mobile terminal reorganizes the same major trading state into a smaller navigation surface, so labels and placement are not identical to the desktop cockpit described here.

Frequently asked questions