{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/trace-the-request-by-identity-not-by-nearby-timestamps",
  "id": "MHC-D-RESEARCH-0974",
  "version": "0.1.0",
  "title": "Trace the request by identity, not by nearby timestamps",
  "summary": "Two messages appearing at 10:03 do not necessarily belong to the same story.",
  "kind": "checklist",
  "body": "Use propagated request or trace identifiers to connect work across services. Preserve parent or causal links when asynchronous processing starts a separate trace. Timestamps help order observations, but proximity alone cannot establish that one message caused another.",
  "limits": [
    "A shared identifier can be misused or reused incorrectly. A trace shows what was instrumented, not a guaranteed complete history."
  ],
  "topics": [
    "work-01-reliable-changes"
  ],
  "intents": [],
  "source_ids": [
    "RS-11A3596487BDCEAE"
  ],
  "evidence": [
    {
      "claim": "OpenTelemetry uses propagated trace context and span links to associate work across synchronous and asynchronous boundaries.",
      "source_id": "RS-11A3596487BDCEAE",
      "role": "supports",
      "note": "Recorded links describe instrumented relationships, not necessarily the complete system history.",
      "locator": "Context Propagation; Span Links"
    }
  ],
  "use_when": [
    "Logs from multiple services need to be connected to one operation."
  ],
  "avoid_when": [
    "A shared identifier can be misused or reused incorrectly. A trace shows what was instrumented, not a guaranteed complete history."
  ],
  "example": "A queue consumer starts minutes after the sender finishes. The recorded causal link, not clock proximity, connects their attempts.",
  "check": "Each claimed connection has an identifier or documented linking rule; gaps remain visible.",
  "checklist": [
    "Identify the initiating operation and its correlation identifier.",
    "Follow the identifier or explicit causal link through each boundary.",
    "Mark missing instrumentation and avoid copying sensitive payloads into a tracing field."
  ],
  "sources": [
    {
      "id": "RS-11A3596487BDCEAE",
      "title": "Traces",
      "url": "https://opentelemetry.io/docs/concepts/signals/traces/"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-0974",
      "to": "MHC-D-RESEARCH-0972",
      "type": "useful_with",
      "url": "/knowledge/find-the-first-boundary-where-the-record-becomes-wrong"
    }
  ],
  "collections": [
    {
      "id": "RC-8F91DD82E91EA56B",
      "title": "Find the failure without creating a second incident",
      "url": "/collections/find-the-failure-without-creating-a-second-incident"
    }
  ]
}