A trace for every transformation.
Making the journey from a source record to a context bundle visible and inspectable.
The final bundle is only half the story
A structured bundle tells you what reached the downstream application. It does not, by itself, explain which source produced a fact, whether another version existed, or why a record was omitted. Those questions call for a record of the process.
Provenance as a companion output
Calyra’s provenance layer represents transformations as a graph. It accompanies the compiled context so developers can investigate the path from source records to emitted output. Keeping the two together makes debugging a question about a concrete transformation.
Build for the questions you will ask later
A useful trace should help a team understand selection, normalization, removal, and validation. It should be evaluated alongside the output itself. Traceability is not a substitute for sound clinical validation, but it gives reviewers something concrete to inspect.