Architecture & Systems
Market Snapshots as Bundles
A market snapshot is an immutable bundle of curves, vols, and fixings that defines the pricing environment for a run.
Mental model
A snapshot freezes the collection of market inputs that defines one pricing environment.
A snapshot groups all curated market artefacts needed for valuation at a given cut-off: curves, vol surfaces, FX rates, and fixings.
Each snapshot has a unique ID, an as-of datetime, and provenance such as data sources and build configurations.
Explore the mechanism
Which curves, surfaces, fixings, and metadata together define one internally consistent market state?
- A snapshot is a bundle: curves, vols, FX, fixings. A run references the snapshot ID.
- Snapshots are immutable: corrections create a new ID, not an overwrite.
- Curation quality changes the stability of derived artefacts (wiggles here mimic bad inputs).
What to notice
Snapshots are immutable: corrections or rebuilds create new snapshots instead of overwriting past ones.
Valuation runs reference snapshot IDs so prices and risk numbers can always be tied back to a precise market view.
Where it appears
- reproducible valuation runs
- intraday risk comparisons
- controlled scenario construction
Where the intuition breaks
What this view leaves out
- A snapshot can be immutable yet economically inconsistent if its inputs use mismatched timestamps, conventions, or calibration dependencies.
Where this concept sits
Follow the strongest prerequisites, applications, extensions, and contrasts.
Connections for Market Snapshots as Bundles
Reliable snapshots should be assembled from curated, explicitly transformed market data rather than opaque raw feeds.
Foundation ofMarket and Model VersioningA valuation can only be reproduced if the exact market snapshot and model version are both identified.
Foundation ofSnapshot Versioning and CorrectionsOnce market inputs are captured as snapshots, versioning and correction rules determine how their history is preserved.
Extended bySnapshots as System StateThe system-state view generalises a market snapshot from a data bundle into an explicit representation of the system at a point in time.
Used byMark-to-MarketMark-to-market requires a coherent set of market inputs captured at a defined valuation time.
Used byReplay of Valuation RunsReplaying a valuation requires the same market snapshot or an explicitly versioned equivalent.
Reliable snapshots should be assembled from curated, explicitly transformed market data rather than opaque raw feeds.
Explore concept →