# Trace the request by identity, not by nearby timestamps

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Trace the request by identity, not by nearby timestamps

ID: MHC-D-RESEARCH-0974 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/trace-the-request-by-identity-not-by-nearby-timestamps

Two messages appearing at 10:03 do not necessarily belong to the same story.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### 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.

### Explanation

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.

### 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.

### 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.

### Limits

- A shared identifier can be misused or reused incorrectly. A trace shows what was instrumented, not a guaranteed complete history.

### Evidence and sources

- supports: OpenTelemetry uses propagated trace context and span links to associate work across synchronous and asynchronous boundaries. — RS-11A3596487BDCEAE. Recorded links describe instrumented relationships, not necessarily the complete system history. (Context Propagation; Span Links)
- RS-11A3596487BDCEAE: Traces — https://opentelemetry.io/docs/concepts/signals/traces/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/find-the-first-boundary-where-the-record-becomes-wrong
