ORIGINAL COMPANY-CONTEXT PRACTICE
Version a synthetic ingredient and label graph
Original practice scenario: A fictional food manufacturer changes an ingredient supplier while packaged inventory from the earlier recipe remains available. How should label data be versioned?
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Tie each manufactured lot to the recipe and label versions actually used. A current product description cannot safely replace historical composition for units already produced.
Work through it
- Give ingredient specifications, supplier lots, recipes and packaging labels immutable versions with explicit effective intervals and approval status.
- Record manufacturing-lot relationships and validate that the selected label corresponds to the applicable recipe rather than merely the product name.
- Test overlapping revisions, reworked material, supplier corrections and remaining old inventory; provide traceable impact searches and reviewable exceptions.
Tradeoffs to discuss
- Versioned graphs increase operational complexity but support accurate historical lookup and targeted investigation.
Common pitfalls
- Do not overwrite historical lot composition when a catalog changes.
- This synthetic data exercise does not establish food-label compliance or product safety.