CAT-104 synthetic catalog cleanup example All records, product details and supplier information in this folder are fictional. They illustrate a reviewable cleanup proposal, not a client result or live import. Every CSV marks its rows as synthetic. No credentials or provider calls are needed. Read the files in this order: 1. input.csv: the unchanged source export, with two rows for CAT-104. 2. supplier-reference.csv: the fictional source for width and material. 3. proposed-output.csv: two proposed rows, both held and still separate. 4. review.csv: the two unresolved decisions. 5. change-log.csv: the five proposed field changes and their evidence. What changes: - ROW-002 width: 2 cm becomes 20 mm. ROW-001 already says 20 mm. - Both missing material values become Aluminium, stated by SUP-104. - The unsupported compatibility claim becomes blank in the proposal only. Its original wording remains in input.csv and change-log.csv. What stays unresolved: - A shared SKU and manufacturer part indicate a possible match. They do not prove that item identity, version and linked history are safe to merge. - The supplier source gives no compatibility evidence. A blank means unknown. - REV-001 and REV-002 remain open. No merge or publication is approved. Expected result: 2 input rows, 1 supplier row, 2 proposed output rows, 2 open reviews and 5 proposed field changes. There is no completed import. source_ref uses filename:row-id. A vertical bar separates multiple references. review_refs points to review.csv; supplier_ref points to supplier-reference.csv. These files are for inspection and learning. They are not a provider-specific import format. A real catalog needs verified source authority, identity and history checks, field mapping, an approved review and a destination test.