Integration Overview
DataGen is designed to be a synthetic data producer, not a universal importer.
Recommended integration model
The cleanest pattern is:
- author and generate a DataGen world
- export normalized artifacts
- translate those artifacts in a bridge or companion adapter
- feed the translated data into the downstream consumer
Why this works well
- it preserves DataGen’s role as a data generator
- it keeps downstream translation logic close to the downstream system
- it reduces pressure to turn DataGen plugins into consumer-specific adapters