{
  "title": "Construction machinery data for AI telematics identity review",
  "source_page": "https://fiund.com/industries/construction-machine-telematics-identity-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "An equipment alias changed midweek",
    "context": "Fictional asset records and telemetry contain arbitrary motion counters, not customer sites or operational instructions.",
    "records": [
      [
        "1",
        "Assignment log",
        "Display alias Loader 1 belongs to asset M7 through Tuesday and M9 starting Wednesday."
      ],
      [
        "2",
        "Export",
        "Tuesday row 8 count increments; Wednesday row 5, both alias Loader 1."
      ],
      [
        "3",
        "Query",
        "Return M9 activity by day."
      ]
    ],
    "question": "Which row belongs to M9?",
    "answer": "Only the Wednesday row with five count increments belongs to M9 under record 1. Tuesday's eight belong to M7 even though record 2 repeats the same alias. Keep the timestamp and stable asset key so reassigning a label cannot rewrite history.",
    "failureModes": [
      "Summing rows by display alias",
      "Applying current alias ownership to older events"
    ],
    "fields": [
      [
        "stable_asset_id",
        "Survives reassignment"
      ],
      [
        "event_date",
        "Selects the effective alias mapping"
      ],
      [
        "counter_unit",
        "Prevents treating increments as hours"
      ]
    ],
    "holdout": "Use a meter reset halfway through Wednesday and distinguish a reset from negative activity.",
    "boundary": "No locations, operator identities, authentic fleet exports or equipment operating instructions."
  }
}