The recurring job
A catalog operator receives a supplier CSV every month. Rows and columns may move, volatile notes change, and identifiers contain leading zeros. The operator needs to isolate material record changes, normalize the accepted delivery and retain evidence of what ran.
Match records by the exact composite key sku + warehouse, independent of row order.
Exclude updated_at and import_note from material field changes.
Rename the status column, lowercase exact text, map pending to ready, and remove the delivery note.
Require four output records before writing the cleaned file.
Check the committed comparison and run reports against their source artifacts.
The checked result
These are observations from the committed CLI and fixtures, enforced by npm run check:marketing-demo. They describe this small example only.
Download the complete proof bundle
The source and output CSVs contain only the published fictional fixture values. The evidence reports deliberately contain aggregate counts and hashes rather than source cell values.
Reproduce before repeating the claim
npm run check:marketing-demoThe repository check rebuilds the CLI, compares the deliveries, verifies both reports against their artifacts, checks the expected outcome, confirms that leading-zero SKUs remain present, and rejects selected source cell values if they leak into either report.