Summary, Inspect, and Debug

Each project has three views with separate data responsibilities.

Summary

Summary is the performance and portfolio view. Depending on runtime capabilities and available history, it can show:

• performance metrics and time ranges;

• equity or return series;

• execution summary and fills;

• portfolio composition;

• account activity;

• risk information and data-availability warnings.

Summary combines durable historical windows with selected live overlays. An empty metric should remain explicitly unavailable rather than being inferred from unrelated live values.

Inspect

Inspect is a catalog-driven workspace for the current runtime. It discovers instruments, bar and book resources, factors, orders, positions, and fills from reported capabilities and resource keys.

Typical uses include:

• open an instrument chart with historical bars and live updates;

• inspect the current projected order book;

• subscribe to a factor and view recent samples;

• compare positions, open orders, closed orders, and execution fills;

• inspect an exact resource contract instead of guessing its topic.

The workspace subscribes only to resources selected by the user interface. Historical availability is determined by each catalog contract.

Debug

Debug favors evidence over presentation. It exposes open and closed orders, trades, runtime events, history-service status, and a recent project log tail. Use it after Summary reports missing data or Inspect cannot establish a live subscription.

Choose the right view

Question	View	Primary source
How did the strategy perform?	Summary	Historical aggregation
What is the runtime publishing now?	Inspect	Catalog + WebSocket
Why is data missing or an order stuck?	Debug	Runtime queries, events, logs