One identity per security, across every venue
Tickers are recycled, companies are renamed, and the same economic exposure trades under different symbols in different countries. Quantivo resolves all of it to stable identities with effective-dated history.
What it does
Stable identities
Issuers, instruments, listings, and venues are modelled separately, so a symbol change never breaks the link to prior history.
Effective-dated aliases
Tickers, ISINs, CUSIPs, SEDOLs, FIGIs, and vendor codes are stored as time-bounded aliases rather than overloaded strings.
Explicit relationships
Depositary receipts, foreign ordinaries, share classes, dual listings, and successor entities are linked as typed relationships.
Point-in-time membership
Index and universe membership is effective-dated, so historical queries return the constituents as they were on the requested date.
How it works
Resolve the identity
Incoming symbols match against effective-dated aliases for the relevant date and venue.
Link the relationships
Related listings and share classes attach through typed links rather than string similarity.
Version the change
Renames, delistings, and corporate actions create new effective-dated records that preserve prior lineage.
Serve point-in-time
Queries specify an as-of date and receive the identity and membership that applied on it.
Where this actually stands
Quantivo is being built in the open. This is what is running today and what is being worked on next — no roadmap items dressed up as shipped features.
Shipped today
- Venues, instruments, listings, aliases, and typed instrument links
- Bitemporal universe membership with source and revision history
- Shared instrument contracts published to every app in the monorepo
In progress next
- Entity resolution across Quantivo symbols and statement proxies (QVP-194)
- Provider symbol mapping and reconciliation under the vendor decision (QVP-127, QVP-163)