What problem does it solve?
Adds a disciplined, step-by-step process for introducing transformations, mappings, and converters while preventing subtle correctness regressions and undocumented behavior. It prevents incomplete implementations by enforcing a concrete example, an inverse mapping when required, and a strong correctness argument before proceeding.
Core Features & Use Cases
- Structured checklist for gathering source, target, algorithm, inverse mapping, correctness argument, example, and reference implementation.
- Closed-loop testing guidance that mandates source → target → solve → extract → verify to ensure round-trip correctness.
- Implementation and documentation requirements including registration in the project, example programs, and updates to docs; ideal for data migrations, type converters, compiler IR passes, and similar codebase transformations.
Quick Start
Use add-rule to implement a transformation from a verified source format to a target format with a concrete worked example and a closed-loop test.