mainsequence-assets-and-translation

You map assets to upstream market data by defining AssetTranslationTable rules that connect each asset to its corresponding time series, ensuring deterministic routing with exactly one matching translation rule per asset.

Distinguishing public versus custom assets requires applying asset identity decisions that assign stable unique identifiers and asset categories, ensuring clean dependency manifests and reliable upstream data routing.

You need an asset category to represent a universe when defining AssetTranslationTable rules that route multiple underlying assets through a collective upstream time series rather than mapping each security individually.

Deterministic routing is enforced by validating that exactly one matching translation rule applies per asset, preventing ambiguous upstream data mapping and maintaining stable asset identities across your project.

Duplicate or unmatched upstream time series occur when asset identity decisions lack stable unique identifiers or when AssetTranslationTable rules allow multiple matching rules for a single asset.

Managing asset translation without predefined asset categories risks non-deterministic routing, as categories are required to define whether an asset maps to a specific time series or represents a broader universe.