How should a mismatch release be described in catalogue metadata?

Resellers usually need a listing to be searchable and machine-readable. A mismatch release can be described with a small metadata block that travels with each file.

- **workflow:** the workflow slug, plus a domain field such as banking, insurance, utilities or logistics. - **record_pairs:** the record types that are compared, such as ledger_entry with bank_line, or invoice with goods_receipt. - **cause_taxonomy:** the list of root-cause labels used, with a version string so customers can tell when labels change. - **policy_refs:** identifiers of the tolerance and approval rules that apply to each case. - **format:** JSONL for case-level records, Parquet for larger tabular tables, with a schema file for each. - **provenance:** a statement that the content is generated, with notes on how grounding and disclosure risk can be inspected. - **licence_flags:** whether sub-licensing, training use, evaluation-only use and redistribution are allowed, as agreed for the release.

Keep case identifiers stable across versions, such as CASE-0412 or REC-3306, so your customers can compare releases and report issues against a specific case. Agree the metadata block with MirrorFirm during scoping, since the fields a release carries depend on what was requested.