Every record arrives with a clock, a source and a health state.
The data contract makes disagreement visible. Fallback data is labelled as fallback, and evidence travels with the decision.
Inputs for Nova, Atlas and Aegis
ClassContentRequirement
Exchange spotPrice, volume and approved trading pairsTimestamping and feed-gap monitoring
DerivativesFutures, options, funding, open interest and positioningA common clock with spot
Order bookDepth and movement at fixed basis-point bandsFreshness; stale depth blocks Aegis
On-chainFlows, exchange reserves and large transfersNormalised to the market timeline
EventsNews, macro and venue statusNever substitutes for market data
PortfolioPositions, limits, mandate and concentrationSource of truth for Atlas and Aegis
Sources for Ava, Elara and Iris
ClassContentRule
DocumentsPDFs, policies, runbooks and researchAllowlist, owner and immutable snapshot
RepositoriesProject documentation with controlled accessVersion and snapshot date required
Tickets / CRMOne operating system per Elara connectionRead-only until a human approves the action
Evaluation casesThe team’s own Iris test setVersioned with the system
Data contract
No silent smoothing.
- TimestampEvery record carries time, source, schema version and feed-health state.
- DisagreementConflicting feeds remain visible to the operator.
- FallbackA fallback feed is labelled as fallback, never presented as the primary source.
- EvidenceEvidence and risk state travel with the decision through the full path.
Typical integration
The vendor set is fixed during Scope.
Exchange APIs and market-data vendors feed Nova. Portfolio accounting and the OMS or execution gateway meet Aegis. Document stores and repositories feed Ava; Elara connects to one ticketing or CRM system; Iris joins the CI and release path. The integration surface does not expand silently during Run.