{
  "title": "Automobile manufacturing data for AI order and build options",
  "source_page": "https://fiund.com/industries/automobile-order-build-option-chain-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The sales order and build manifest disagree on one option",
    "context": "An original mock order describes a paper vehicle model with invented market and package codes.",
    "records": [
      [
        "1",
        "Order",
        "Roof R2, seat package S4, market M1."
      ],
      [
        "2",
        "Issued build ticket",
        "R2/S4/M1."
      ],
      [
        "3",
        "Completed manifest",
        "R1/S4/M1 after an undocumented option difference."
      ]
    ],
    "question": "Which options are confirmed and which needs follow-up?",
    "answer": "The seating and market fields agree across records 1–3. The roof in the completed manifest is R1 while the order and ticket specify R2. Record the roof discrepancy at build completion; there is no documented amendment that would make R1 the authorized order.",
    "failureModes": [
      "Treating the issued ticket as the as-built state",
      "Masking one option mismatch under the matching package"
    ],
    "fields": [
      [
        "option_role",
        "Separates roof, seat and market fields"
      ],
      [
        "expected_build_value",
        "Tracks order and issue context"
      ],
      [
        "completed_value",
        "Preserves actual recorded outcome"
      ]
    ],
    "holdout": "Include an order amendment after the issue ticket but before completion; compare to the effective customer request.",
    "boundary": "No customer or VIN data, vehicle safety, build processes or configuration advice."
  }
}