{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-trace-reconstruction-across-a2a-hops-when-otel-genai-spans-are-correlated-by-trace-id-alone",
  "title": "Which invariants prevent trace reconstruction across A2A hops when OTel GenAI spans are correlated by trace_id alone",
  "date_of_record": "2026 November 12",
  "scope": "Applies to multi-agent systems where an orchestrator invokes downstream agents via the Agent-to-Agent (A2A) protocol and each agent emits OpenTelemetry GenAI semantic-convention spans. It does not apply to single-process tool-calling loops, nor to systems where a single collector-side processor rewrites all spans into one resource before export.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-trace-reconstruction-across-a2a-hops-when-otel-genai-spans-are-correlated-by-trace-id-alone.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-trace-reconstruction-across-a2a-hops-when-otel-genai-spans-are-correlated-by-trace-id-alone.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-trace-reconstruction-across-a2a-hops-when-otel-genai-spans-are-correlated-by-trace-id-alone.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1593,
    "python_slice_tokens": 322,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **trace identity** and **causal reachability**. A `trace_id` is a 128-bit label propagated as an opaque string; it asserts only that two spans belong to the same logical transaction, not that one span's execution causally produced the other's. Across an A2A hop, the orchestrator's `gen_ai.chat` span and the downstream ...",
    "what_was_observed": "In a three-hop pipeline (orchestrator → retrieval agent → synthesis agent), the orchestrator emitted a `gen_ai.chat` span with `gen_ai.operation.name=chat`, `gen_ai.request.model`, and a `send` message event. The A2A client serialized the outbound request with a `traceparent` header whose `parent-id` was the orchestrator span's `span_id`. The retrieval agent, however, ran under a framework whose A2A server handler cr...",
    "condition_of_validity": "Correlation by `trace_id` is valid only when **all** of the following hold: 1. Every hop's A2A client injects `traceparent` (W3C Trace Context) and every A2A server extracts it into the active context *before* creating its first span. 2. The `tracecontext` propagator is present in `OTEL_PROPAGATORS` on every process — not merely `baggage`, not merely `b3`. 3...",
    "decision_boundary": "When reconstructing a multi-agent trace, the operator must decide between two strategies: - **Strict tree reconstruction** (join on `trace_id`, then validate parent edges): correct, but fails closed. Any hop that violated conditions 1–4 yields a forest, and the reconstruction must report the break rather than silently stitching. - **Context-keyed reconstruct...",
    "operational_effect": "The operational consequence is that \"trace completeness\" is not a property of the collector or the backend but of the *propagator configuration across every hop's runtime*. A single agent deployed with a default `OTEL_PROPAGATORS` (which historically defaulted to `baggage` in some SDK distributions) silently converts every downstream trace into a new root. B..."
  },
  "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": "85373dc8573d22d9fe5bf0439e16a86802f90d7817ba223030c65bf45d06ba08",
    "verified_classes": [
      "TraceReconstructionError",
      "Span"
    ],
    "verified_functions": [
      "assert_causal_edge",
      "reconstruct",
      "check_propagator_env"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "TraceReconstructionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "os",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}