{
  "title": "Specialized telemetry clock and lineage data for AI",
  "source_page": "https://fiund.com/industries/telemetry-provider-clock-lineage-data",
  "authorship": "Original fictional Fiund editorial exercise. No actual operating records or third-party source assets are included.",
  "example": {
    "title": "Late arrival and a corrected source clock are different timing problems",
    "context": "An artificial telemetry packet uses abstract values and seconds from a shared fictional origin. The task aligns records, not signals or asset behavior.",
    "records": [
      [
        "TM1",
        "Series A",
        "Source second 1, value 7, received at second 10."
      ],
      [
        "TM2",
        "Series B batch",
        "Source seconds 0 and 2 received at seconds 10 and 12; source second 1 arrives later at receipt second 13."
      ],
      [
        "TM3",
        "Series C clock note",
        "C source clock is exactly 2 seconds ahead of the shared origin. C record source second 3, value 9, received at second 14; corrected source time is recorded as 1."
      ]
    ],
    "question": "Which observations align at corrected source second 1, and does B's initially absent point remain missing after the late batch arrives?",
    "answer": "TM1's A point, TM2's late B point and TM3's corrected C point align at shared source second 1. Their receipt times differ and must not be used as the source-time key. B's point was absent from the earlier received batch but is present after receipt second 13. C's correction changes its clock interpretation, whereas B's delay changes arrival order. Neither establishes a physical fault.",
    "failureModes": [
      "Aligning by receipt time and treating simultaneous source observations as different events.",
      "Calling B's late point permanently missing or applying C's clock correction to every series."
    ],
    "fields": [
      [
        "Series and source timestamp",
        "Defines the observation's original time reference."
      ],
      [
        "Receipt timestamp",
        "Preserves delay and arrival order."
      ],
      [
        "Clock correction and scope",
        "Records the transformation applying to C only."
      ],
      [
        "Availability cutoff",
        "Shows when a supposedly missing point became available."
      ]
    ],
    "holdout": "Ask the same alignment question with a receipt cutoff of second 12. Require B's point to be unavailable at that cutoff while retaining A and corrected C only if their receipts qualify too.",
    "boundary": "Use invented series and values. Exclude asset identities, real signals, frequencies, locations, configurations and live traces."
  }
}