Snapshots as System State
In control-theoretic terms, market snapshots act as observable system state for the trading and risk engine.
Explanation
In control systems, effective feedback requires a measurable state of the system and its disturbances.
In a pricing and risk framework, booked trades and market snapshots together define the state from which decisions are made.
Versioned snapshots make this state observable and reproducible, enabling control actions such as hedging and limit setting to be analysed.
Framing snapshots as state highlights why missing or unversioned market data makes the overall system effectively uncontrollable.
statecontrol theorysnapshotssystem view
Interactive visualisation
Snapshots as system state
In control terms, snapshots are the observable state. Missing or unversioned state makes the system hard to control.
State quality
Complete
80%
Noise
20%
Hedge
55%
Controllability proxy
Higher when state is complete and observation noise is low.
Interpretation
- Trades + snapshot define the state the desk acts on.
- Versioned snapshots make decisions analysable and replayable.
- Poor state quality increases tracking error (plot) even with aggressive hedging.
Closed-loop error (toy)
range -0.45–0.70
Increasing completeness improves feedback. Increasing noise makes the same hedge action less effective.
Control-loop view
Snapshot is the observable state. Run ID is the experiment handle.
Market snapshot (state)
80% complete
Risk engine
compute PV/Greeks
Decision (hedge)
55% aggression
Observed outcome
20% noise