{
  "title": "Bearing manufacturing data for AI designation and suffix review",
  "source_page": "https://fiund.com/industries/bearing-designation-suffix-identity-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The suffix has meaning only in its glossary",
    "context": "A fictional component code uses invented suffixes that deliberately do not map to actual bearing specifications.",
    "records": [
      [
        "1",
        "Order",
        "Bearing alias B4 with suffix H."
      ],
      [
        "2",
        "Glossary",
        "In family B4, H means variant V1; in B5, H means V3."
      ],
      [
        "3",
        "Inspection index",
        "Entry R1 covers B4/V1; R2 covers B5/V3."
      ]
    ],
    "question": "Which inspection entry matches the order?",
    "answer": "R1 matches: record 1 requests B4/H, and record 2 resolves H to V1 only within B4. Record 3 then identifies R1. R2 also has a connection to suffix H, but only through another family and variant.",
    "failureModes": [
      "Treating suffix meanings as universal",
      "Joining on the suffix and ignoring the family"
    ],
    "fields": [
      [
        "designation_family",
        "Selects the applicable glossary"
      ],
      [
        "suffix_token",
        "Preserves the marked variant"
      ],
      [
        "canonical_variant",
        "Joins the resolved variant to the report"
      ]
    ],
    "holdout": "Provide a suffix whose glossary changed over time and require version-specific resolution.",
    "boundary": "No authentic bearing designations, fit calculations, loading assumptions or selection advice."
  }
}