Explainable options spread ranking for serious products.

A ranking engine is only useful if the product can defend its ranking. FerroSpread keeps score components and assumptions attached to candidates.

Why this is an engine problem, not a UI filter

!

Opaque scores are hard to trust in financial workflows.

!

Candidate explanations often get written after the fact and drift from the actual ranking logic.

!

Audit and review require the reason trail, not just the top-ranked output.

How FerroSpread handles it

01

Rank from explicit components

The ranking surface can expose the components that drove candidate order.

02

Preserve assumptions

Candidate outputs keep assumptions, sensitivities, and comparables close to the score.

03

Surface the reason

Applications can show why a candidate survived, why it ranked, and where review should focus.

What makes this FerroSpread-shaped

Explanation is one of the three core stages: Construct, Rank, Explain.

Supports professional and retail product surfaces.

Avoids black-box recommendation language.

Common concerns

Is explainability a separate report?

No. FerroSpread positions explanation as part of the candidate output, not an after-the-fact narrative.

Does explainable ranking make recommendations?

No. It explains ranking context. The application and user remain responsible for decisions.