{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-reconcile-trace-span-timestamps-with-eval-and-safety-signal-timestamps-when-they-are-produced-by-different-clocks",
  "title": "How should an instance reconcile trace-span timestamps with eval and safety-signal timestamps when they are produced by different clocks?",
  "date_of_record": "2026 November 18",
  "scope": "Applies to GenAI observability pipelines that join trace spans, offline/online eval results, and safety-classifier verdicts at agent-step granularity, where each signal class is emitted by a separately scheduled component (tracer SDK in-process, eval worker out-of-process, safety gateway on a network hop). Does not apply to single-process synchronous instrumentation where all three signals share one monotonic clock.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-trace-span-timestamps-with-eval-and-safety-signal-timestamps-when-they-are-produced-by-different-clocks.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-trace-span-timestamps-with-eval-and-safety-signal-timestamps-when-they-are-produced-by-different-clocks.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-reconcile-trace-span-timestamps-with-eval-and-safety-signal-timestamps-when-they-are-produced-by-different-clocks.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1425,
    "python_slice_tokens": 245,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **event time** (when the agent step actually executed) and **ingest time** (when the observability backend received the record). Trace spans carry event time from the agent runtime's clock. Eval results and safety verdicts typically carry *their own* event time, but that timestamp is stamped by the eval worker or safety ga...",
    "what_was_observed": "In a multi-agent pipeline (planner → tool-caller → summarizer) with steps averaging 400–900 ms, eval verdicts were joined to spans by `abs(eval.ts - span.end_ts) < 1s`. Three failure signatures appeared in production: 1. **Cross-step bleed under backpressure.** When the eval queue backed up (p99 enqueue-to-eval latency rose from 120 ms to 3.4 s), eval timestamps drifted past the 1 s window and were re-attributed to t...",
    "condition_of_validity": "Timestamp-proximity joining is only valid when **all** of the following hold simultaneously: - `max_clock_skew + max_ingest_queue_delay < min_step_duration` (strict, with margin — use the p1 step duration, not the mean). - Every signal payload carries the propagated `trace_id` AND `span_id` of the originating step (not merely the trace root). - The eval/safe...",
    "decision_boundary": "When correlating signals at agent-step granularity, choose **token-based correlation as primary, timestamp as a consistency check**: - Join on `(trace_id, span_id)` propagated end-to-end through eval and safety payloads. - Treat a timestamp as a *validator*: if `signal.ingest_ts < span.end_ts`, the signal was observed before the step completed — a causal imp...",
    "operational_effect": "After switching to token-based correlation with timestamp-as-validator: - False-positive safety flags from cross-step bleed fell from 0.7% to 0.02% of steps (residual attributable to genuinely ambiguous multi-tool steps, not attribution error). - Eval coverage *appeared* to drop from 99.2% to 97.8% — this was the correct number, revealing ~1.4% of signals th..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "7b34e8b2d14d60e2fb1867a7cf9efe3e5cc2a83af19dd585972735ba0a73db88",
    "verified_classes": [
      "UnattributableSignal",
      "ClockSkewViolation"
    ],
    "verified_functions": [
      "attribute_signal"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ClockSkewViolation",
      "UnattributableSignal"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
