Implied volatility solving in Rust, inside the risk path.

FerroRisk treats implied volatility as part of the analytics pipeline, not a disconnected helper function.

Why this needs one shared risk path

!

Standalone IV solvers can disagree with the pricing model or fail silently near difficult quotes.

!

Surface calibration needs robust contract-level IV behavior before fitting begins.

!

Live chains need solved IV, forward recovery, and diagnostics in one pass.

How FerroRisk handles it

01

Recover the market context

Forward recovery and quote conventions are handled before solved IV feeds downstream analytics.

02

Solve on the model path

IV solving stays attached to the pricing model and unit conventions used for Greeks.

03

Feed surfaces and chains

Solved IVs can become inputs for SVI, SSVI, SABR, smile panels, and chain-level exposure views.

What makes this FerroRisk-shaped

Fused contract analytics combines solved IV, forward, and Greeks.

Surface calibration pages build on contract-level IV behavior.

Reference tests and proof gates reduce room for silent convention drift.

Common concerns

Is the solver isolated from the rest of the engine?

No. FerroRisk positions IV solving as part of contract analytics and surface construction.

Does FerroRisk expose fit diagnostics?

Yes. Surface calibration includes fit-quality diagnostics and quality contracts.