ores.synthetic.core

ores.synthetic.core implements the server side of the synthetic data component. Each of the nine bound entities has a generated repository, mapper, entity, service, NATS handler with sub-registrar, history provider registrar, and history field mapper. messaging/registrar.cpp composes all handlers and history providers into the service host. The facet also keeps the component's original catalog and organisation generation services, which produce synthetic test data for the DQ pipeline.

• NATS request messages for entity CRUD, history, feed configuration, and feed control, decoded with the ores.synthetic.api protocol headers.
• Database context supplied by the host (ores.synthetic.service), carrying the tenant and party scope the RLS policies enforce.

• Entity rows written to the ores_synthetic_ tables, with version history.
• NATS responses for every registered subject.
• Synthetic organisation hierarchies and catalogs returned to callers.

• include/ores.synthetic.core/messaging/registrar.hpp — registers all NATS handlers and history providers with the service host.
• include/ores.synthetic.core/service/ — one service class per entity.
• include/ores.synthetic.core/repository/ — one repository class per entity.
• src/generators/ and src/data/ — the catalog and organisation generators.

• ores.synthetic.api — domain types, protocol schemas, and feeds.
• ores.eventing — change event publication.
• ores.database — execution context and party scope.
• nats.c — NATS messaging client.

• ores.synthetic.api — protocol types and domain entities.
• ores.synthetic.service — NATS service entrypoint.
• ores.synthetic Messaging Reference — full NATS subject and message catalogue.