Resume Deployment

The candle closes a deployment's runs evaluate (UX-8).

Closes sit at offset_minutes past 00:00 UTC and every period_minutes after it: the deployment's cron inverted under its persisted dispatch generation (utils.schedule.evaluation_grid), so a pre-arm cron that fires at 11:59 reads as the 12:00 close it evaluates.

Which venue a deployment or account runs on, and its money class.

Paper Trading v2, S01 §3.10 / IC-01-9. capital_class is trading.accounts.capital_class (real or practice); code is the venue's trading.venues.code (HL, PAPER). On a deployment whose account_id names no account row (no foreign key refuses one, V6.0__deployments.sql:16) the block reads {code: null, capital_class: "real"}: such a row predates paper and keeps its pre-paper meaning. Clients key on this block, never on a probe.

IC-04-2's health_detail (S04 §3.10.2): the first predicate that matched, the count of most recent consecutive missing bars, the newest COMPLETE bar, and the bar label the current state began at.

IC-03-2: the record's latest non-day-0 snapshot, else its first day-0 row.

IC-03-5: the graduation criteria state, computed on read.

record and carry_over are null only for a deployment with no deployed commit (the record has no commit to name).

Coverage state of the money facts behind a performance read (spec 04 §5.1, M4).

Freshness is part of the answer: the number beside this block is only as fresh as the capture coverage that produced its inputs, and this block says exactly how fresh —

• COVERED — coverage reaches the requested interval's end; fresh_as_of is the weakest fact class's reach.
• SYNCING — the interval is managed and post-epoch but coverage has not reached its end yet; synced_through is how far it has (null when no coverage row speaks for the interval at all — absence never reads as fresh).
• LEGACY — the interval predates the account's first coverage row (the epoch cutover): pre-capture history, served ungated but labeled. Until the capture lane goes live, every account reads this.
• UNMANAGED — the interval overlaps no managed window; strategy performance is not defined there.

Phase 1 labels only — no numeric field elsewhere in the response changes because of this block.