{
  "title": "Commodity broker transaction corrections for AI evaluation",
  "source_page": "https://fiund.com/industries/commodity-broker-correction-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A replacement confirmation changes a field without adding a trade",
    "context": "Imaginary transaction aliases and arbitrary quantity units create an offline correction fixture. No security, contract price, position or strategy is represented.",
    "records": [
      [
        "BC1",
        "Confirmation V1",
        "Transaction T-A, order O-A, quantity 12 units, category X."
      ],
      [
        "BC2",
        "Replacement V2",
        "Explicitly supersedes BC1 for T-A/O-A; category corrected to Y. Quantity remains 12. Separate T-B/O-B also has quantity 12."
      ],
      [
        "BC3",
        "Unlinked correction note",
        "Says category Z and quantity 12 but omits transaction, order and supersession references."
      ]
    ],
    "question": "How many distinct identified transactions are present, which field changed for T-A, and can BC3 be applied to either transaction?",
    "answer": "BC1 and BC2 describe two identified transactions, T-A and T-B; the replacement is a new version of T-A, not a third transaction. T-A's category changes from X to Y while its quantity stays 12. BC3 lacks the identifiers needed to associate its Z correction with either transaction. Equal quantity cannot resolve that gap, so retain the note as an unmatched exception for review.",
    "failureModes": [
      "Counting a replacement confirmation as another trade in totals.",
      "Applying an unlinked correction to whichever transaction shares its quantity."
    ],
    "fields": [
      [
        "Transaction and order aliases",
        "Disambiguates equal-quantity records."
      ],
      [
        "Version and supersedes reference",
        "Defines the replacement chain."
      ],
      [
        "Changed field and unmatched-note status",
        "Separates an evidenced correction from an assumption."
      ]
    ],
    "holdout": "Give BC3 an explicit T-B reference but a conflicting order alias. Require a flagged identity conflict rather than a silent update.",
    "boundary": "Use original dummy records only. Exclude execution logs, clients, venue credentials and licensed platform formats; no trading action or recommendation belongs in the task."
  }
}