{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-propagate-an-inherited-trace-context-across-an-mcp-tool-call-boundary-when-the-upstream-a2a-peer-and",
  "title": "Under what conditions must an instance refuse to propagate an inherited trace context across an MCP tool-call boundary when the upstream A2A peer and the LLM inference layer disagree on span-kind semantics",
  "date_of_record": "2026 November 16",
  "scope": "Applies to multi-agent systems where a single logical request crosses at least three observability domains — an A2A (agent-to-agent) task envelope, one or more MCP (Model Context Protocol) tool invocations, and an LLM inference call — and where trace context (trace_id, span_id, parent_span_id, span kind, and baggage) is propagated by convention rather than by a schema-enforced contract. Does not apply to single-hop tool calls, to systems using a single unified tracing SDK with a shared semantic-convention version pinned across all hops, or to contexts where the trace is re-rooted at every boundary by policy.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-an-inherited-trace-context-across-an-mcp-tool-call-boundary-when-the-upstream-a2a-peer-and.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-an-inherited-trace-context-across-an-mcp-tool-call-boundary-when-the-upstream-a2a-peer-and.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-propagate-an-inherited-trace-context-across-an-mcp-tool-call-boundary-when-the-upstream-a2a-peer-and.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2169,
    "python_slice_tokens": 440,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"trace context is lost.\" Loss is observable and cheap: a broken parent link, an orphaned span, a trace that terminates early. The failure addressed here is **trace context that is faithfully propagated but semantically mislabeled**, producing a trace that is structurally valid, causally wrong, and indistinguishable from a correct trace at ...",
    "what_was_observed": "In a three-hop pipeline (orchestrator agent → A2A task → worker agent → MCP tool → LLM inference), the following invariant was found to hold in every failing trace: the worker agent's MCP tool-call span carried the A2A task span as its parent, and the LLM inference span carried the MCP tool-call span as its parent. Structurally correct. But the A2A task span was a *consumer* span on the receiving side and a *producer...",
    "condition_of_validity": "The invariant \"propagate inherited trace context across the MCP boundary\" is valid only when all of the following hold: 1. The upstream A2A peer and the local MCP instrumentation agree on the span kind of the inherited parent, *or* the local instrumentation does not depend on the parent's kind for any decision (attribution, sampling, error classification). 2...",
    "decision_boundary": "The boundary is crossed when a receiver cannot establish, from the inherited context alone, the span kind the upstream peer assigned to the parent. In practice this is almost always the case across A2A→MCP transitions, because A2A's convention and MCP's convention were specified independently and neither carries kind on the wire. The decision rule: - If the ...",
    "operational_effect": "Systems that adopt the refuse-and-link rule observe three effects. First, traces become slightly wider (links instead of parents at convention boundaries) and slightly more expensive to store. Second, attribution dashboards stop drifting with fan-out depth — the factor-of-fan-out cost error disappears because `agent.id` is no longer read from a colliding bag..."
  },
  "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": "ad64f38059e4279a84c5278cdc9f61c6d0b056e4a7762ea05b542c460af9f7b7",
    "verified_classes": [
      "SpanKind",
      "TraceContextKindConflict",
      "InheritedContext",
      "LocalSpanPolicy"
    ],
    "verified_functions": [
      "resolve_parent",
      "emit_mcp_tool_span"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TraceContextKindConflict"
    ],
    "sample_fail_closed_invariants": [
      "re-root plan missing trace_id; cannot preserve trace continuity"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
