{
  "title": "Engine equipment data for AI variant and accessory records",
  "source_page": "https://fiund.com/industries/engine-variant-accessory-record-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "A base serial does not determine its attached option",
    "context": "Paper engine silhouettes and fictional accessory cards contain identity data only.",
    "records": [
      [
        "1",
        "Variant register",
        "Base E4 supports toy configurations V1 with A6 and V2 with A7."
      ],
      [
        "2",
        "Order",
        "Unit U3 requested as V2."
      ],
      [
        "3",
        "Assembly record",
        "U3: E4 plus A6; physical scan of A6 logged."
      ]
    ],
    "question": "Which variant does the recorded build represent?",
    "answer": "Records 1 and 3 describe V1 because U3 has A6 on base E4. Record 2 requests V2, which would use A7 in this exercise. Flag the accessory-driven configuration difference while preserving the matching base identity and the observed scan.",
    "failureModes": [
      "Mapping base model directly to one variant",
      "Overwriting the scan with order intent"
    ],
    "fields": [
      [
        "base_model",
        "Groups the possible configurations"
      ],
      [
        "accessory_id",
        "Disambiguates the built variant"
      ],
      [
        "configuration_state",
        "Keeps ordered and assembled versions separate"
      ]
    ],
    "holdout": "Use an accessory with two revision-compatible aliases and require a documented mapping before flagging a difference.",
    "boundary": "No actual engine design, performance information, maintenance or assembly instructions."
  }
}