Paper — every trading figure here (positions, orders, P&L, equity, returns) is simulated on an Alpaca paper account. No real capital is at risk, and no order is ever placed with your money. Running costs shown under ops, such as LLM spend, are real.

Your dashboard

Public

Monitoring

The pulse check. One page that answers two questions: is the system running, and is it working with fresh, trustworthy data?

What this page shows

Monitoring is your reassurance panel. A trading system is only as good as the data feeding it, so this page keeps an eye on both the activity of the system and the freshness of the information it relies on. You don't need to understand the plumbing — you just need to know it's alive and being fed good data.

Is it running?

  • ·Decisions logged— a running count of the choices the system has recorded. This number should keep climbing while the market is open. If it stops growing during a trading session, that's the first sign the system has gone quiet.
  • ·Activity today — how much the system has been thinking and working since the start of the day. Steady activity means the engine is ticking over normally.
  • ·Account value — the live balance, mirrored here so you can confirm the trading side is connected and reporting.

Is the data fresh?

  • ·Feeds healthy— the share of the system's information sources that are reporting in normally. At 100%, everything the system needs is flowing. If it dips, one of the feeds has gone stale and the system will hold back rather than act on old information.
  • ·Decision-quality score — an independent grade of how well-reasoned recent decisions have been. A healthy score means the system is explaining itself clearly and backing its choices with evidence; a sustained drop is worth a closer look.

Fresh data is a safety rule, not a nicety

If the information is stale or a feed goes missing, the system deliberately stops rather than trade blind. So when Monitoring shows the feeds healthy, you're not just seeing "all green" — you're seeing that it's safe for the system to act at all.

If entry reconciliation is required

This red alert means the broker accepted an entry but the system could not safely finish recording it. New entries stay blocked, including after a restart, until an operator repairs the broker-versus-records difference and completes the verified recovery procedure. Never dismiss the alert by editing system state.

How to use it

A quick visit answers "is everything OK?" in seconds: the decision count is climbing, the feeds are healthy, the quality score is steady. If something looks off — a flat count during market hours, feeds below 100% — that's your cue to pause and investigate before trusting the day's output.