Six primitives. Composable by default.
The Ferro suite is the reusable infrastructure layer the MorphIQ Platform is built from: matching, signal analysis and feature extraction, pricing, spread construction, market data, and deterministic replay foundations. Some pieces are trading-specific; others are general-purpose math and infrastructure. Built into Anvil, consumed by the applications, and licensed or embedded where builders need the primitive.
The suite is not a monolith. A Ferro name means there is, or will be, a reusable artifact: a crate, service, wire contract, managed component, or licensed module. Internal utilities do not get promoted into the family just because they are useful.
Replay-exact limit-order-book matching with price-time priority, explicit tiebreakers, configurable tick semantics, and journal-friendly execution state.
Wavelet feature extraction and signal analysis for non-stationary time series: discrete and continuous transforms, multi-resolution decomposition, streaming features, and regime primitives.
Pricing, implied-volatility solving, Greeks, volatility-surface calibration, chain analytics, and portfolio risk measures.
Spread construction, ranking, and scenario explanation with leg-level accounting and pricing inputs from FerroRisk and the broader Ferro suite.
Market-data normalization for provider-agnostic event streams with explicit quality, tradability, and replay semantics.
Deterministic time, replay, and journal primitives that make time an explicit dependency in reproducible systems.
Line coverage is a ceiling, not a floor. FerroReplay, FerroRisk, and FerroWave move stable primitive laws into machine-checked proof boundaries, alongside mutation score, property tests, and reference-implementation parity checks. Performance has the same discipline: SIMD, batch APIs, runtime dispatch, and regression-gated benchmarks keep hot paths measurable.
The Ferro primitives are infrastructure. They are not wrapped in a marketing narrative, they are not sold as a bundle, and they are not trying to compete with trading desks on features. They exist because serious systems — trading applications first among them — need serious mathematical and systems primitives that can be audited line by line.
A trading signal marketplace. Signals are the output of consuming the primitives, not the product being sold.
A black-box risk service. Every output is derived from documented methodology, tested implementations, and auditable evaluation materials.
A single product bundle. Each Ferro component can have a small developer-marketing surface, but the suite itself is not sold as one SaaS.
An advertisement. If a component does not do a thing, it does not claim to. The docs are the specification.
Each Ferro component can have a technical brief, a deep docs section, and a small developer-marketing domain when evaluators need a front door. Those surfaces explain the primitive to builders; they do not turn Ferro into a consumer brand.
The deterministic runtime.