{
  "title": "Dealer-arranged finance contract data for AI testing",
  "source_page": "https://fiund.com/industries/dealer-finance-contract-match-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Finance acceptance attaches to a contract revision, not a preliminary worksheet",
    "context": "A practice sale packet has invented deal aliases and arbitrary figures. It contains no signatures, credit applications, vehicle IDs or actual lender terms.",
    "records": [
      [
        "DF1",
        "Worksheet W1",
        "Deal D-A, preliminary version: practice total 200 and trade-in field 20. Marked proposal only."
      ],
      [
        "DF2",
        "Contract C2 and acceptance A2",
        "Revised D-A/C2: practice total 190, trade-in 25. A2 explicitly accepts D-A/C2, not W1."
      ],
      [
        "DF3",
        "Second packet",
        "Deal D-B/C1 has an acceptance referring to older D-B0/C1. No D-B-to-D-B0 revision relationship supplied."
      ]
    ],
    "question": "Which D-A document has a matched acceptance, and does the second packet establish acceptance for D-B/C1?",
    "answer": "DF2 explicitly matches A2 to D-A/C2. DF1's proposal has different figures and is not the accepted document named in A2. DF3's acceptance points to D-B0, while the packet asks about D-B; the similar contract suffix does not establish a revision relationship. Flag the second packet's deal-identity gap rather than transferring acceptance. The task identifies documentary links without assessing finance suitability or a consumer decision.",
    "failureModes": [
      "Summarizing accepted figures from the earlier proposal instead of the named contract.",
      "Matching by a contract suffix while ignoring a conflicting deal reference."
    ],
    "fields": [
      [
        "Deal alias and document class",
        "Separates proposals from contracts."
      ],
      [
        "Contract revision and acceptance target",
        "Establishes the exact match."
      ],
      [
        "Practice figures and unresolved relationship",
        "Exposes mismatched versions without guessing."
      ]
    ],
    "holdout": "Add an explicit D-B0-to-D-B conversion record that excludes acceptance carryover. Require the identity link to be recognized while acceptance remains unconfirmed.",
    "boundary": "Use independently written fictional packets. Exclude credit decisions, lender buy rates, applications, signatures and actual dealership records."
  }
}