Docs/How it works
How it works

System overview

Provider adapters feed a canonical registry, normalized market engine, route and risk scoring, simulation layer, and read-only product surfaces.

01

System overview

Provider adapters feed a canonical registry, normalized market engine, route and risk scoring, simulation layer, and read-only product surfaces.

The implementation uses deterministic shared functions so the market page, simulation API, strategy builder, and vault preview apply the same allocation and funding rules.

02

Operational controls

Require explicit canonical instrument mapping. Reject missing spot or perp prices. Propagate null and stale states instead of substituting values.

03

Limits and risk

Cross-venue legs cannot be atomic today. The simulator models target construction, not guaranteed execution.

Risk boundary

Missing, stale, or contract-dependent values remain unavailable. Hinge does not insert demo values to complete a calculation.