Operate from a record, not a hunch.

Automations carry a strategy or alert definition into a runtime that can be observed over time. The fleet surface answers whether something is running; the detail record answers what it did, what it saw and whether its evidence still keeps up with the bar clock.

The runtime keeps execution class and safety boundaries explicit. Alert, Paper Trade, Live Trade and mixed definitions should be read as different operational resources, not as different colors for the same thing.

Start with a Paper Portfolio or an alert so you can observe behavior, state transitions and accounting without confusing a simulation with a live venue.

When a Live automation is selected, the app warns that it can place real orders with real funds. A verified connection, validated provider account mode, fresh reconciliation and the LIVE_TRADING_ENABLED safety boundary remain mandatory; a UI link alone is not permission to trade.

Each block on an automation reads its own source. When a source answers and holds nothing, you see its ordinary empty wording — no fills, no orders, flat. When a source does not answer, the block says so instead, and a number it would have computed reads as a dash rather than as zero.

The activity ledger shows what the automation did and what the runtime did around it: signals and their actions, start and stop transitions, evaluation coverage, and any bar the runtime has not finished deciding. Quiet bars are summarised rather than listed — an automation on a one-minute chart evaluates hundreds of thousands of them a year.

• CoverageWhen evaluation started and ended, and any named gap in between. Without it, "no signals" and "not evaluated" would look the same.
• UnresolvedA bar whose attempt failed or was blocked and has not yet reached a decision. It stays visible until it does.
• SupersededA retry that resolved an earlier failed attempt. Both attempts are kept; only one decided the bar.