Adding an asset class
Table of Contents
1. Summary
A new asset class plugs into two places in the simulator: its configuration rows
become a typed build input, and its generator implements i_generator behind a new
kind string. It also needs catalogue rows for its vendor instruments and
mappings. Everything else stays as it is: the runner, the adapter contract, the
ingest loop and the party tick.
2. Detail
2.1. The edits
- A codegen entity model for the config, regenerated.
- A struct in
generator_build_inputand a builder registered inmake_default_generator_factory(). - One
register_kindcall inmake_default_generator_kind_registry(). It carries the kind's config read permission, loader, build-input resolver, and simulate decode and reply pair. - A permission row and a role grant in the IAM populate SQL.
- Catalogue rows: vendor instruments and mappings for each provider that quotes the class, in the system bundle. See A system bundle installs the catalogue and the simulator installs its own universe.
Steps 1 to 4 are the simulator's. Step 5 is the service's, and a live adapter needs the same rows.
2.2. What needs no edit
The runner, the subject builders, the adapter contract, the party tick and the ingest loop. The only exception is the CRM hook in The ingest loop and the one pipeline.
3. See also
- Market Data Architecture — the structure note that orders this cluster.
- The generator factory and the kind seam — completes: the seam these edits sit around.
- A system bundle installs the catalogue and the simulator installs its own universe — completes: where the catalogue rows go.