{
  "title": "Telephone apparatus data for AI module and version records",
  "source_page": "https://fiund.com/industries/telephone-product-module-version-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Two module revisions share an exterior model",
    "context": "Fictional handset cards and a mock internal manifest track a changed option without any network data.",
    "records": [
      [
        "1",
        "Model map",
        "Handset H4 rev A uses module M1; rev B uses M2."
      ],
      [
        "2",
        "Completed-unit record",
        "Serial S5, H4 rev B, module M1."
      ],
      [
        "3",
        "Photo",
        "Exterior badge reads H4 with revision obscured."
      ]
    ],
    "question": "What can be flagged and what remains unverified visually?",
    "answer": "The completed-unit record lists M1 where H4 rev B calls for M2, so records 1 and 2 support a module-revision discrepancy. Record 3 identifies only the exterior family. Do not claim the image independently confirmed the revision or the internal module.",
    "failureModes": [
      "Inferring revision from the shared family badge",
      "Overriding a recorded internal module with exterior appearance"
    ],
    "fields": [
      [
        "handset_revision",
        "Selects the expected module"
      ],
      [
        "installed_module_id",
        "Records the as-built identity"
      ],
      [
        "view_scope",
        "Limits conclusions from exterior imagery"
      ]
    ],
    "holdout": "Provide an explicit approved substitution for certain serials; verify S5 against the covered interval.",
    "boundary": "No actual phones, subscriber records, communications configurations or service advice."
  }
}