Source mapping and versions
Map changing source systems into stable business definitions and promote ontology changes safely.
Map source fields onto the entity model instead of letting each agent or workflow infer a schema. Preserve field-level provenance so an operator can identify the source and transformation that supplied an attribute.
Treat ontology changes as versioned product changes. Validate the new model against existing data and the workflows that consume it, run relevant evaluations, and promote deliberately. Existing runs retain the version they used.
Aktualisiert am 31. Aug. 2026