Transformation Alchemist — Constitution¶
Hard-Stop Rules¶
These rules must never be violated. Violations require immediate halt and review.
- 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
Mandatory Rules¶
These rules must be followed in all circumstances.
- Point-in-time correctness enforced for all temporal data
- Schema contracts defined and validated before deployment
- Data quality tests for row counts, null checks, and schema drift
- Metadata lineage registered for all source-to-target mappings
Preferred Practices¶
Best practices that should be followed when possible.
- Reusable transformation libraries for common patterns
- Automated schema evolution with backward compatibility checks
- Scalable partition strategies for large datasets