{
  "title": "Communications equipment data for AI port-map revisions",
  "source_page": "https://fiund.com/industries/communication-device-port-map-revision-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "The label changed even though the connector position did not",
    "context": "An original paper module has numbered ports and two mock document revisions. No wiring or network behavior is represented.",
    "records": [
      [
        "1",
        "Rev A map",
        "Position 2 named X; position 3 named Y."
      ],
      [
        "2",
        "Rev B map",
        "Position 2 renamed Z; position 3 remains Y."
      ],
      [
        "3",
        "Photo",
        "Module revision B visible; label X printed at position 2."
      ]
    ],
    "question": "What discrepancy belongs in the record?",
    "answer": "Position 2 carries the old X label although the visible B revision calls for Z under record 2. Record 1 explains where X came from. Position 3 has no documented change. Treat the evidence as a label mismatch, with no inference about device behavior.",
    "failureModes": [
      "Using an old label as proof the entire module is rev A",
      "Inferring the physical port function from label text"
    ],
    "fields": [
      [
        "module_revision",
        "Selects the relevant reference"
      ],
      [
        "port_position",
        "Matches stable geometry across revisions"
      ],
      [
        "printed_label",
        "Stores the actual image evidence"
      ]
    ],
    "holdout": "Use a sticker covering the underlying label and require distinguishing old print from current applied marking.",
    "boundary": "No real communications hardware, wiring, protocol settings or network access information."
  }
}