ores.refdata.core

ores.refdata.core manages the reference-data domain in ORE Studio: over 150 domain types covering currencies, countries, counterparties, books, business units, business centres, and trading structure entities. It provides temporal ORM repositories, domain services, NATS message handlers in the 0x3000–0x3FFF range, CSV export for selected types, and synthetic-data generators. Reference data is consumed by all other domain components (trading, assets, IAM) and drives UI drop-downs and validation.

• NATS request messages from Qt clients and peer services (query/create/update for currencies, counterparties, books, etc.) in the 0x3000–0x3FFF range.
• PostgreSQL connections to ores_refdata_* tables with temporal versioning.
• DQ population events for bulk reference-data loads.

• Reference-data records persisted to the ores_refdata schema with full temporal history (valid_from / valid_to).
• NATS response messages returned to callers.
• CSV exports of selected entity types (e.g., currencies).

• include/ores.refdata.core/ores.refdata.core.hpp — aggregate include.
• include/ores.refdata.core/messaging/registrar.hpp — registers all NATS handlers with the service host.
• include/ores.refdata.core/service/ — per-entity service headers.

• ores.refdata.api — shared domain types and NATS protocol schemas.
• ores.dq — ORM base classes and data-quality infrastructure.
• ores.iam.core — identity and authorisation context.
• rfl — JSON serialisation via reflection.
• fort — formatted table output.
• soci — SQL ORM for PostgreSQL persistence.
• nats.c — NATS messaging client.

• ores.refdata — component group overview.
• ores.refdata.api — protocol types and domain entities.
• ores.refdata.service — NATS service entrypoint.
• ores.refdata Messaging Reference — full NATS subject and message catalogue.
• Multi-Party Architecture — how parties, books, and business units relate.
• Trading Structure — party, book, portfolio, business-unit, business-centre hierarchy design.