Transformation Alchemist — Debug Workflow

Description: Fix issues and errors in artifacts

When to Use

Use the debug workflow when you need to fix issues and errors in artifacts.

Input Requirements

• Source data schemas and data dictionaries
• Transformation requirements and business rules
• Schema evolution history and contract definitions
• Quality test specifications and validation rules

Process

1. Initialize — Set up the debug context for Transformation Alchemist
2. Execute — Perform the debug operation following Transformation Alchemist's style
3. Validate — Check output against quality gates
4. Handoff — Deliver results to downstream personas

Output

• Transformation pipeline code with schema contracts
• Schema evolution documentation with migration scripts
• Data quality test suites for transformation outputs
• Metadata lineage records linking source to target fields

Quality Gates

• No temporal leakage in time-series or event-based transformations
• No personally identifiable information without tokenization or masking
• No non-deterministic transforms in production pipelines
• No undocumented schema changes or silent column additions
• Schema contracts must be validated before deployment